From 937213c2c37f71be1b112d9767f6ee8aecf0cfcf Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Fri, 30 Dec 2011 20:36:54 +0000 Subject: [PATCH] Edited csrf.txt changes from [17299] git-svn-id: http://code.djangoproject.com/svn/django/trunk@17309 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/contrib/csrf.txt | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/ref/contrib/csrf.txt b/docs/ref/contrib/csrf.txt index feeba2280c..006d63b7a3 100644 --- a/docs/ref/contrib/csrf.txt +++ b/docs/ref/contrib/csrf.txt @@ -150,10 +150,11 @@ Other template engines ---------------------- When using a different template engine than Django's built-in engine, you can -set the token in your forms manually after making sure it is available in the -context of the template. +set the token in your forms manually after making sure it's available in the +template context. -So in Cheetah for example, your form could contain the following: +For example, in the Cheetah template language, your form could contain the +following: .. code-block:: html @@ -161,7 +162,7 @@ So in Cheetah for example, your form could contain the following: -You may use javascript similar to the :ref:`AJAX code ` above to get +You can use JavaScript similar to the :ref:`AJAX code ` above to get the value of the CSRF token. The decorator method