summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2010-11-21 10:07:42 -0700
committerCasey Duncan <casey.duncan@gmail.com>2010-11-21 10:07:42 -0700
commitb887aaa95a88fab020fb75d4d5fb46c35119365b (patch)
tree670628a3f4f4890ba885efb13e6bc71e800db986 /docs
parent597b72993eeb538c6d0e3ac91e4f5e98a3339767 (diff)
downloadpyramid-b887aaa95a88fab020fb75d4d5fb46c35119365b.tar.gz
pyramid-b887aaa95a88fab020fb75d4d5fb46c35119365b.tar.bz2
pyramid-b887aaa95a88fab020fb75d4d5fb46c35119365b.zip
clarify sentence about nonsensical replacement markers
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 3ac3bcf27..a072f87a8 100644
--- a/docs/narr/urldispatch.rst
+++ b/docs/narr/urldispatch.rst
@@ -268,10 +268,10 @@ 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
-without specifying a custom regular expression to restrict what a marker
-captures.
+It is possible to use two replacement markers without any literal
+characters between them, for instance ``/{foo}{bar}``. However, this
+would be a nonsensical pattern without specifying a custom regular
+expression to restrict what each marker captures.
Segments must contain at least one character in order to match a
segment replacement marker. For example, for the URL ``/abc/``: