diff options
| author | Tim Graham <timograham@gmail.com> | 2013-10-01 10:08:36 -0400 |
|---|---|---|
| committer | Baptiste Mispelon <bmispelon@gmail.com> | 2014-03-05 22:35:37 +0100 |
| commit | b8713ee69a7a171a01cf94c56d3b83bc09e41506 (patch) | |
| tree | 5921582ce42a042388611d29238762e4b90bc72d | |
| parent | 74181c0a2c5eb52c63666f830403c9331fc1ad69 (diff) | |
[1.4.x] Fixed #21195 -- Clarifed usage of template_name in tutorial part 4.
Backport of b66a51ad545ac726ef98966cbc35ee7aefdff8cd from master.
| -rw-r--r-- | docs/intro/tutorial04.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/intro/tutorial04.txt b/docs/intro/tutorial04.txt index 6a55917fd5..d3af620b88 100644 --- a/docs/intro/tutorial04.txt +++ b/docs/intro/tutorial04.txt @@ -276,7 +276,7 @@ two views abstract the concepts of "display a list of objects" and By default, the :class:`~django.views.generic.list.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`` argument 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 -- |