summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2013-10-01 10:08:36 -0400
committerTim Graham <timograham@gmail.com>2014-01-20 20:08:59 -0500
commit45535c8a4cba200cd610010ec1e2d515de6c2475 (patch)
treebafda1b4c92b25ecc20e6b587abe39f4efa40a32
parent0946aac61d0da2aceafe6179cdb64ccad583d924 (diff)
[1.5.x] Fixed #21834 -- Clarifed usage of template_name in tutorial part 4.
Backport of a292ad1105 from stable/1.6.x
-rw-r--r--docs/intro/tutorial04.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/intro/tutorial04.txt b/docs/intro/tutorial04.txt
index 05672c2852..ee0f0ad040 100644
--- a/docs/intro/tutorial04.txt
+++ b/docs/intro/tutorial04.txt
@@ -267,7 +267,7 @@ two views abstract the concepts of "display a list of objects" and
By default, the :class:`~django.views.generic.detail.DetailView` generic
view uses a template called ``<app name>/<model name>_detail.html``.
-In our case, it'll use the template ``"polls/poll_detail.html"``. The
+In our case, it would use the template ``"polls/poll_detail.html"``. The
``template_name`` attribute is used to tell Django to use a specific
template name instead of the autogenerated default template name. We
also specify the ``template_name`` for the ``results`` list view --