diff --git a/docs/ref/class-based-views/generic-editing.txt b/docs/ref/class-based-views/generic-editing.txt index 8c1fe0f758..969a033a31 100644 --- a/docs/ref/class-based-views/generic-editing.txt +++ b/docs/ref/class-based-views/generic-editing.txt @@ -74,7 +74,7 @@ editing content: .. code-block:: html+django -
{% csrf_token %} + {% csrf_token %} {{ form.as_p }}
@@ -130,7 +130,7 @@ editing content: .. code-block:: html+django -
{% csrf_token %} + {% csrf_token %} {{ form.as_p }}
@@ -187,7 +187,7 @@ editing content: .. code-block:: html+django -
{% csrf_token %} + {% csrf_token %} {{ form.as_p }}
@@ -238,7 +238,7 @@ editing content: .. code-block:: html+django -
{% csrf_token %} + {% csrf_token %}

Are you sure you want to delete "{{ object }}"?

diff --git a/docs/ref/csrf.txt b/docs/ref/csrf.txt index fdb373b002..2664a6270f 100644 --- a/docs/ref/csrf.txt +++ b/docs/ref/csrf.txt @@ -41,7 +41,7 @@ To take advantage of CSRF protection in your views, follow these steps: .. code-block:: html+django -
{% csrf_token %} + {% csrf_token %} This should not be done for POST forms that target external URLs, since that would cause the CSRF token to be leaked, leading to a vulnerability. @@ -179,7 +179,7 @@ to ``{% csrf_token %}`` in the Django template language. For example: .. code-block:: html+jinja - {{ csrf_input }} + {{ csrf_input }} The decorator method -------------------- diff --git a/docs/topics/forms/formsets.txt b/docs/topics/forms/formsets.txt index cb07e7ad59..eb84da40eb 100644 --- a/docs/topics/forms/formsets.txt +++ b/docs/topics/forms/formsets.txt @@ -630,7 +630,7 @@ The ``manage_articles.html`` template might look like this: .. code-block:: html+django - + {{ formset.management_form }} {% for form in formset %} @@ -644,7 +644,7 @@ deal with the management form: .. code-block:: html+django - +
{{ formset }}
@@ -662,7 +662,7 @@ If you manually render fields in the template, you can render .. code-block:: html+django - + {{ formset.management_form }} {% for form in formset %}