From 8c4cc3235239d4d9d39a6294443a9cce0a7a7a81 Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Thu, 12 Jul 2007 04:44:45 +0000 Subject: [PATCH] Edited changes to docs/tutorial04.txt from [5649] git-svn-id: http://code.djangoproject.com/svn/django/trunk@5651 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/tutorial04.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/tutorial04.txt b/docs/tutorial04.txt index a25b5a7ba5e..cfd9a45a4be 100644 --- a/docs/tutorial04.txt +++ b/docs/tutorial04.txt @@ -210,7 +210,7 @@ objects" and "display a detail page for a particular type of object." ``object_id`` for the generic views. * We've added a name, ``poll_results``, to the results view so that we have - a way to refer to its url later on (see `naming URL patterns`_ for more on + a way to refer to its URL later on (see `naming URL patterns`_ for more on named patterns). .. _naming URL patterns: http://www.djangoproject.com/documentation/url_dispatch/#naming-url-patterns @@ -261,8 +261,8 @@ the new templates and context variables. Change the template call from ``polls/detail.html`` to ``polls/poll_detail.html``, and pass ``object`` in the context instead of ``poll``. -The last thing to do is fix the url handling to account for the use of generic -views. In the vote view above we used the ``reverse()`` function to avoid +The last thing to do is fix the URL handling to account for the use of generic +views. In the vote view above, we used the ``reverse()`` function to avoid hard-coding our URLs. Now that we've switched to a generic view, we'll need to change the ``reverse()`` call to point back to our new generic view. We can't simply use the view function anymore -- generic views can be (and are) used