diff options
| author | Craig de Stigter | 2014-10-03 08:41:18 +1300 |
|---|---|---|
| committer | Craig de Stigter | 2014-10-03 08:41:18 +1300 |
| commit | dfab9af294972720f59890967cd9ae1a6c0796b6 (patch) | |
| tree | 587fb81fc26d401870f860afb400fa027441b403 /docs/topics/writable-nested-serializers.md | |
| parent | ffc6aa3abcb0f823b43b63db1666913565e6f934 (diff) | |
| download | django-rest-framework-dfab9af294972720f59890967cd9ae1a6c0796b6.tar.bz2 | |
Minor: fix spelling and grammar, mostly in 3.0 announcement
Diffstat (limited to 'docs/topics/writable-nested-serializers.md')
| -rw-r--r-- | docs/topics/writable-nested-serializers.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/writable-nested-serializers.md b/docs/topics/writable-nested-serializers.md index 66ea7815..abc6a82f 100644 --- a/docs/topics/writable-nested-serializers.md +++ b/docs/topics/writable-nested-serializers.md @@ -6,7 +6,7 @@ Although flat data structures serve to properly delineate between the individual entities in your service, there are cases where it may be more appropriate or convenient to use nested data structures. -Nested data structures are easy enough to work with if they're read-only - simply nest your serializer classes and you're good to go. However, there are a few more subtleties to using writable nested serializers, due to the dependancies between the various model instances, and the need to save or delete multiple instances in a single action. +Nested data structures are easy enough to work with if they're read-only - simply nest your serializer classes and you're good to go. However, there are a few more subtleties to using writable nested serializers, due to the dependencies between the various model instances, and the need to save or delete multiple instances in a single action. ## One-to-many data structures |