Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Fixed #12350 -- Fixed typo in tutorial04. Thanks, mortense

git-svn-id: http://code.djangoproject.com/svn/django/trunk@12173 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 985dcdb4b228fe4e5a535ca0ae7bb07e18c637b1 1 parent 1f400c6
@adrianholovaty adrianholovaty authored
Showing with 6 additions and 6 deletions.
  1. +6 −6 docs/intro/tutorial04.txt
View
12 docs/intro/tutorial04.txt
@@ -47,15 +47,15 @@ A quick rundown:
* ``forloop.counter`` indicates how many times the :ttag:`for` tag has gone
through its loop
- * Since we are creating a POST form (which can have the effect of modifying
- data), we unfortunately need to worry about Cross Site Request Forgeries.
+ * Since we're creating a POST form (which can have the effect of modifying
+ data), we need to worry about Cross Site Request Forgeries.
Thankfully, you don't have to worry too hard, because Django comes with
- very easy-to-use system for protecting against it. In short, all POST
- forms that are targetted at internal URLs need the ``{% csrf_token %}``
- template tag adding.
+ a very easy-to-use system for protecting against it. In short, all POST
+ forms that are targeted at internal URLs should use the ``{% csrf_token %}``
+ template tag.
The ``{% csrf_token %}`` tag requires information from the request object, which
-is not normally accessible from within the template context. To fix this, a
+is not normally accessible from within the template context. To fix this, a
small adjustment needs to be made to the ``detail`` view, so that it looks like
the following::
Please sign in to comment.
Something went wrong with that request. Please try again.