aboutsummaryrefslogtreecommitdiffstats
path: root/docs/tutorial/3-class-based-views.md
diff options
context:
space:
mode:
authorVeronica Lynn2013-08-07 14:00:06 -0400
committerVeronica Lynn2013-08-07 14:00:06 -0400
commit4d8d2340be4de905af3488dc721c7b94b1371ef0 (patch)
tree38b60bc6099d0af27a4a7fcc5dbaf91ca3d76b26 /docs/tutorial/3-class-based-views.md
parentb52beb0734e167349b2cf397047a2ec7fe304b35 (diff)
downloaddjango-rest-framework-4d8d2340be4de905af3488dc721c7b94b1371ef0.tar.bz2
Fixed typos in a bunch of docs
Diffstat (limited to 'docs/tutorial/3-class-based-views.md')
-rw-r--r--docs/tutorial/3-class-based-views.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/tutorial/3-class-based-views.md b/docs/tutorial/3-class-based-views.md
index c1b3d8f2..9fc424fe 100644
--- a/docs/tutorial/3-class-based-views.md
+++ b/docs/tutorial/3-class-based-views.md
@@ -81,7 +81,7 @@ Okay, we're done. If you run the development server everything should be workin
One of the big wins of using class based views is that it allows us to easily compose reusable bits of behaviour.
-The create/retrieve/update/delete operations that we've been using so far are going to be pretty simliar for any model-backed API views we create. Those bits of common behaviour are implemented in REST framework's mixin classes.
+The create/retrieve/update/delete operations that we've been using so far are going to be pretty similar for any model-backed API views we create. Those bits of common behaviour are implemented in REST framework's mixin classes.
Let's take a look at how we can compose our views by using the mixin classes.