summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2010-11-21 10:04:35 -0700
committerCasey Duncan <casey.duncan@gmail.com>2010-11-21 10:04:35 -0700
commit597b72993eeb538c6d0e3ac91e4f5e98a3339767 (patch)
tree8c3aeadc45c78d719dcaa03335346f453eba9b61 /docs
parent78facc37c9fc5d1648c48e19f649ac4a1809c7bb (diff)
downloadpyramid-597b72993eeb538c6d0e3ac91e4f5e98a3339767.tar.gz
pyramid-597b72993eeb538c6d0e3ac91e4f5e98a3339767.tar.bz2
pyramid-597b72993eeb538c6d0e3ac91e4f5e98a3339767.zip
fix lingering old-style replacement marker syntax
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/urldispatch.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/narr/urldispatch.rst b/docs/narr/urldispatch.rst
index 82e2950dc..3ac3bcf27 100644
--- a/docs/narr/urldispatch.rst
+++ b/docs/narr/urldispatch.rst
@@ -266,7 +266,7 @@ To capture both segments, two replacement markers can be used:
The literal path ``/foo/biz.html`` will match the above route pattern,
and the match result will be ``{'name': 'biz', 'ext': 'html'}``. This
occurs because the replacement marker ``{name}`` has a literal part of
-``.`` (period) between the other replacement marker ``:ext``.
+``.`` (period) between the other replacement marker ``{ext}``.
It is possible to use two replacement markers without any literal characters
between them, for instance ``/{foo}{bar}``. This would be a nonsensical pattern