From 3d1795d87a74e2ab5f2bee5bb71a856a809be4f7 Mon Sep 17 00:00:00 2001
From: Jacob Kaplan-Moss <jacob@jacobian.org>
Date: Tue, 12 Aug 2008 23:22:26 +0000
Subject: [PATCH] Clarified a bit of the {% url %} documentation. Fixes #7714.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@8332 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/templates.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/templates.txt b/docs/templates.txt
index 587c5915f0..99dbcb84b4 100644
--- a/docs/templates.txt
+++ b/docs/templates.txt
@@ -1181,7 +1181,7 @@ For example, suppose you have a view, ``app_views.client``, whose URLconf
 takes a client ID (here, ``client()`` is a method inside the views file
 ``app_views.py``). The URLconf line might look like this::
 
-    ('^client/(\d+)/$', 'app_views.client')
+    ('^client/(\d+)/$', 'project_name.app_name.app_views.client')
 
 If this app's URLconf is included into the project's URLconf under a path
 such as this::
@@ -1190,7 +1190,7 @@ such as this::
 
 ...then, in a template, you can create a link to this view like this::
 
-    {% url app_views.client client.id %}
+    {% url project_name.app_name.app_views.client client.id %}
 
 The template tag will output the string ``/clients/client/123/``.