summaryrefslogtreecommitdiff
path: root/docs/ref/templates/api.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/ref/templates/api.txt')
-rw-r--r--docs/ref/templates/api.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt
index f1fb70c9b8..cc6d807ce1 100644
--- a/docs/ref/templates/api.txt
+++ b/docs/ref/templates/api.txt
@@ -368,7 +368,7 @@ straight lookups. Here are some things to keep in mind:
To prevent this, set an ``alters_data`` attribute on the callable
variable. The template system won't call a variable if it has
``alters_data=True`` set, and will instead replace the variable with
- ``string_if_invalid``, unconditionally. The
+ ``string_if_invalid``, unconditionally. The
dynamically-generated :meth:`~django.db.models.Model.delete` and
:meth:`~django.db.models.Model.save` methods on Django model objects get
``alters_data=True`` automatically. Example::
@@ -381,8 +381,8 @@ straight lookups. Here are some things to keep in mind:
* Occasionally you may want to turn off this feature for other reasons,
and tell the template system to leave a variable uncalled no matter
- what. To do so, set a ``do_not_call_in_templates`` attribute on the
- callable with the value ``True``. The template system then will act as
+ what. To do so, set a ``do_not_call_in_templates`` attribute on the
+ callable with the value ``True``. The template system then will act as
if your variable is not callable (allowing you to access attributes of
the callable, for example).
@@ -666,7 +666,7 @@ processors::
]
In addition to these, :class:`RequestContext` always enables
-``'django.template.context_processors.csrf'``. This is a security related
+``'django.template.context_processors.csrf'``. This is a security related
context processor required by the admin and other contrib apps, and, in case
of accidental misconfiguration, it is deliberately hardcoded in and cannot be
turned off in the ``context_processors`` option.
@@ -1100,7 +1100,7 @@ Loader methods
source.
For example, the filesystem loader may receive ``'index.html'`` as a
- ``template_name`` argument. This method would yield origins for the
+ ``template_name`` argument. This method would yield origins for the
full path of ``index.html`` as it appears in each template directory
the loader looks at.