Author: lukeplant
Date: 2009-10-27 08:13:40 -0500 (Tue, 27 Oct 2009)
New Revision: 11668
Modified:
django/trunk/docs/ref/contrib/csrf.txt
Log:
Fixed some typos
Modified: django/trunk/docs/ref/contrib/csrf.txt
===================================================================
--- django/trunk/docs/ref/contrib/csrf.txt 2009-10-27 12:11:56 UTC (rev
11667)
+++ django/trunk/docs/ref/contrib/csrf.txt 2009-10-27 13:13:40 UTC (rev
11668)
@@ -89,7 +89,7 @@
-------------
In Django 1.1, the template tag did not exist. Instead, a post-processing
-middleware that re-wrote POST forms to include the CRSF token was used. If you
+middleware that re-wrote POST forms to include the CSRF token was used. If you
are upgrading a site from version 1.1 or earlier, please read this section and
the `Upgrading notes`_ below. The post-processing middleware is still
available
as ``CsrfResponseMiddleware``, and it can be used by following these steps:
@@ -108,7 +108,7 @@
Use of the ``CsrfResponseMiddleware`` is not recommended because of the
performance hit it imposes, and because of a potential security problem (see
below). It can be used as an interim measure until applications have been
-updated to use the ``{% crsf_token %}`` tag. It is deprecated and will be
+updated to use the ``{% csrf_token %}`` tag. It is deprecated and will be
removed in Django 1.4.
Django 1.1 and earlier provided a single ``CsrfMiddleware`` class. This is
also
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
