diff options
| author | Luke Plant <L.Plant.98@cantab.net> | 2009-10-27 13:13:40 +0000 |
|---|---|---|
| committer | Luke Plant <L.Plant.98@cantab.net> | 2009-10-27 13:13:40 +0000 |
| commit | b32a187296fa856076652bc42dbf89e36c5c6dcf (patch) | |
| tree | 6b9bb0edca8aad8435977c1935d89105fe064a8e /docs | |
| parent | f00ad4168e6c435a2f3691854d3a4a3f78192600 (diff) | |
Fixed some typos
git-svn-id: http://code.djangoproject.com/svn/django/trunk@11668 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ref/contrib/csrf.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ref/contrib/csrf.txt b/docs/ref/contrib/csrf.txt index b168442aa9..3ece422c66 100644 --- a/docs/ref/contrib/csrf.txt +++ b/docs/ref/contrib/csrf.txt @@ -89,7 +89,7 @@ Legacy method ------------- 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 @@ as ``CsrfResponseMiddleware``, and it can be used by following these steps: 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 |