summaryrefslogtreecommitdiff
path: root/docs/tutorial03.txt
diff options
context:
space:
mode:
authorGeorg Bauer <gb@hugo.westfalen.de>2005-10-04 19:34:43 +0000
committerGeorg Bauer <gb@hugo.westfalen.de>2005-10-04 19:34:43 +0000
commit6e2b74d65e84938fdc05f2de40bcfe15efadc693 (patch)
tree43c91a20fff4506a76c2eaecb0318c793bcd0d1e /docs/tutorial03.txt
parent8c2b8aaee676131e6cbf6cb9e50393638db6c451 (diff)
i18n: merged r722:774 from trunk
git-svn-id: http://code.djangoproject.com/svn/django/branches/i18n@775 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/tutorial03.txt')
-rw-r--r--docs/tutorial03.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/tutorial03.txt b/docs/tutorial03.txt
index 2bbd8d7782..84fb64abfe 100644
--- a/docs/tutorial03.txt
+++ b/docs/tutorial03.txt
@@ -91,8 +91,8 @@ Finally, it calls that ``detail()`` function like so::
detail(request=<HttpRequest object>, poll_id=23)
The ``poll_id=23`` part comes from ``(?P<poll_id>\d+)``. Using
-``(?<name>pattern)`` "captures" the text matched by ``pattern`` and sends it as
-a keyword argument to the view function.
+``(?P<name>pattern)`` "captures" the text matched by ``pattern`` and sends it
+as a keyword argument to the view function.
Because the URL patterns are regular expressions, there really is no limit on
what you can do with them. And there's no need to add URL cruft such as