aboutsummaryrefslogtreecommitdiffstats
path: root/docs/tutorial
diff options
context:
space:
mode:
authorJosé Padilla2014-10-31 13:03:39 -0400
committerDougal Matthews2014-11-25 12:44:11 +0000
commit200e0b17daecd07de6d1f9926a430d29b3ee948f (patch)
tree8a8ac43c96df3a46b6c59f9a15a19553c7fb0e47 /docs/tutorial
parent06683b86b2b15153df52fe481b5c4eeb489a80cf (diff)
downloaddjango-rest-framework-200e0b17daecd07de6d1f9926a430d29b3ee948f.tar.bz2
Clean up extra white space
Diffstat (limited to 'docs/tutorial')
-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 db5b9ea7..f9027b68 100644
--- a/docs/tutorial/1-serialization.md
+++ b/docs/tutorial/1-serialization.md
@@ -134,7 +134,7 @@ A serializer class is very similar to a Django `Form` class, and includes simila
The field flags can also control how the serializer should be displayed in certain circumstances, such as when rendering to HTML. The `style={'type': 'textarea'}` flag above is equivelent to using `widget=widgets.Textarea` on a Django `Form` class. 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.
+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.
## Working with Serializers