summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorJosh Schneier <josh.schneier@gmail.com>2018-08-06 19:20:17 -0400
committerTim Graham <timograham@gmail.com>2018-08-06 20:15:22 -0400
commit53e85705221dcc5302393aac40f4fa606e2097d3 (patch)
tree75a03efe32c94c5b46b76b5ffab01733f5150493 /docs/ref
parenta9f5652113f0721a7066e359ae28d14692ea3c47 (diff)
Fixed typo in docs/ref/templates/api.txt.
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/templates/api.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt
index f37c0a65c2..5bd55cff65 100644
--- a/docs/ref/templates/api.txt
+++ b/docs/ref/templates/api.txt
@@ -371,10 +371,10 @@ replaced with the name of the invalid variable.
While ``string_if_invalid`` can be a useful debugging tool, it is a bad
idea to turn it on as a 'development default'.
- Many templates, including some of the Django's templates, rely upon the
- silence of the template system when a nonexistent variable is encountered.
- If you assign a value other than ``''`` to ``string_if_invalid``, you will
- experience rendering problems with these templates and sites.
+ Many templates, including some of Django's, rely upon the silence of the
+ template system when a nonexistent variable is encountered. If you assign a
+ value other than ``''`` to ``string_if_invalid``, you will experience
+ rendering problems with these templates and sites.
Generally, ``string_if_invalid`` should only be enabled in order to debug
a specific template problem, then cleared once debugging is complete.