summaryrefslogtreecommitdiff
path: root/docs/intro/tutorial04.txt
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2013-10-01 10:08:36 -0400
committerTim Graham <timograham@gmail.com>2013-10-01 10:08:36 -0400
commitb66a51ad545ac726ef98966cbc35ee7aefdff8cd (patch)
tree09a3df388b19ab9ceea31377c7fbc45a0f58e6a0 /docs/intro/tutorial04.txt
parentc1c44b25062c3a793ac0d8416f369383a4a58cb4 (diff)
Fixed #21195 -- Clarifed usage of template_name in tutorial part 4.
Diffstat (limited to 'docs/intro/tutorial04.txt')
-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 b0b0f571d8..8abf2d395a 100644
--- a/docs/intro/tutorial04.txt
+++ b/docs/intro/tutorial04.txt
@@ -271,7 +271,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/question_detail.html"``. The
+In our case, it would use the template ``"polls/question_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 --