aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTobias Preuss2015-03-23 11:20:08 +0100
committerTobias Preuss2015-03-23 11:20:08 +0100
commit49c04d721884945927ff6b0f6e850b2b2caeec3a (patch)
tree20a68c476551066283b1f22435f1a3fdb22644b8
parent166801063d6d8bf70d549866da7f718c90927965 (diff)
downloaddjango-rest-framework-49c04d721884945927ff6b0f6e850b2b2caeec3a.tar.bz2
Fix typo.
-rw-r--r--docs/api-guide/serializers.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/api-guide/serializers.md b/docs/api-guide/serializers.md
index aad2236f..d9ded52f 100644
--- a/docs/api-guide/serializers.md
+++ b/docs/api-guide/serializers.md
@@ -344,7 +344,7 @@ Here's an example for an `update()` method on our previous `UserSerializer` clas
return instance
-Because the behavior of nested creates and updates can be ambiguous, and may require complex dependancies between related models, REST framework 3 requires you to always write these methods explicitly. The default `ModelSerializer` `.create()` and `.update()` methods do not include support for writable nested representations.
+Because the behavior of nested creates and updates can be ambiguous, and may require complex dependencies between related models, REST framework 3 requires you to always write these methods explicitly. The default `ModelSerializer` `.create()` and `.update()` methods do not include support for writable nested representations.
It is possible that a third party package, providing automatic support some kinds of automatic writable nested representations may be released alongside the 3.1 release.