From 6f229d2d7a4621fd73e0a5d22b8b7d42dec9493e Mon Sep 17 00:00:00 2001
From: Martin Brochhaus <mbrochh@gmail.com>
Date: Thu, 2 Aug 2012 19:29:19 +0800
Subject: [PATCH] Update docs/topics/class-based-views/index.txt

Fixed a small typo:

"We can use create" should be "We can create"
---
 docs/topics/class-based-views/index.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/topics/class-based-views/index.txt b/docs/topics/class-based-views/index.txt
index 6c2848944c..1ac70e6938 100644
--- a/docs/topics/class-based-views/index.txt
+++ b/docs/topics/class-based-views/index.txt
@@ -87,7 +87,7 @@ Where class based views shine is when you want to do the same thing many times.
 Suppose you're writing an API, and every view should return JSON instead of
 rendered HTML.
 
-We can use create a mixin class to use in all of our views, handling the
+We can create a mixin class to use in all of our views, handling the
 conversion to JSON once.
 
 For example, a simple JSON mixin might look something like this::