From 53e85705221dcc5302393aac40f4fa606e2097d3 Mon Sep 17 00:00:00 2001 From: Josh Schneier Date: Mon, 6 Aug 2018 19:20:17 -0400 Subject: [PATCH] Fixed typo in docs/ref/templates/api.txt. --- docs/ref/templates/api.txt | 8 ++++---- 1 file 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.