aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTom Christie2013-06-17 09:27:38 +0100
committerTom Christie2013-06-17 09:27:38 +0100
commita7a9e8728453cafe331081cbf77ef42f8b9e1841 (patch)
tree323e82274bdc0ded33798b620e3c5601d3f4a6f8
parentaa706f581c84209d83acf04ccd8854e205057e50 (diff)
parentc2f0a5ab77a7ba233d38671c1b190392185427ec (diff)
downloaddjango-rest-framework-a7a9e8728453cafe331081cbf77ef42f8b9e1841.tar.bz2
Merge branch 'master' of https://github.com/tomchristie/django-rest-framework
-rw-r--r--docs/tutorial/1-serialization.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/tutorial/1-serialization.md b/docs/tutorial/1-serialization.md
index bc31d234..2b214d6a 100644
--- a/docs/tutorial/1-serialization.md
+++ b/docs/tutorial/1-serialization.md
@@ -146,7 +146,7 @@ The first thing we need to get started on our Web API is provide a way of serial
The first part of serializer class defines the fields that get serialized/deserialized. The `restore_object` method defines how fully fledged instances get created when deserializing data.
-Notice that we can also use various attributes that would typically be used on form fields, such as `widget=widgets.Testarea`. These can be used to control how the serializer should render when displayed as an HTML form. This is particularly useful for controlling how the browsable API should be displayed, as we'll see later in the tutorial.
+Notice that we can also use various attributes that would typically be used on form fields, such as `widget=widgets.Textarea`. These can be used to control how the serializer should render when displayed as an HTML form. This is particularly useful for controlling how the browsable API should be displayed, as we'll see later in the tutorial.
We can actually also save ourselves some time by using the `ModelSerializer` class, as we'll see later, but for now we'll keep our serializer definition explicit.