summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2010-11-21 10:03:20 -0700
committerCasey Duncan <casey.duncan@gmail.com>2010-11-21 10:03:20 -0700
commit78facc37c9fc5d1648c48e19f649ac4a1809c7bb (patch)
treea3e2e9f6c9fcf78d5e2adef1cc9358bcd4214bef /docs
parentabe2f0444ef1dcf6d860da86e6e3e890a5dd2f52 (diff)
downloadpyramid-78facc37c9fc5d1648c48e19f649ac4a1809c7bb.tar.gz
pyramid-78facc37c9fc5d1648c48e19f649ac4a1809c7bb.tar.bz2
pyramid-78facc37c9fc5d1648c48e19f649ac4a1809c7bb.zip
notate literal period in text for clarity
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/urldispatch.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/narr/urldispatch.rst b/docs/narr/urldispatch.rst
index 45c027e06..82e2950dc 100644
--- a/docs/narr/urldispatch.rst
+++ b/docs/narr/urldispatch.rst
@@ -263,10 +263,10 @@ To capture both segments, two replacement markers can be used:
foo/{name}.{ext}
-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 ``.`` between the other
-replacement marker ``:ext``.
+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``.
It is possible to use two replacement markers without any literal characters
between them, for instance ``/{foo}{bar}``. This would be a nonsensical pattern