summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTshepang Lekhonkhobe <tshepang@gmail.com>2013-02-17 22:47:53 +0200
committerTshepang Lekhonkhobe <tshepang@gmail.com>2013-03-05 09:21:56 +0200
commit6a2827684a13bb588b031f4ac9a6257344bb4e18 (patch)
tree1c33254330116f91dd009370bd72ff38e481efba /docs
parentea87985307731d1ad8597a8e37b7fb9c7950f11f (diff)
downloadpyramid-6a2827684a13bb588b031f4ac9a6257344bb4e18.tar.gz
pyramid-6a2827684a13bb588b031f4ac9a6257344bb4e18.tar.bz2
pyramid-6a2827684a13bb588b031f4ac9a6257344bb4e18.zip
fix grammar; shorten overlong sentence
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/urldispatch.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/urldispatch.rst b/docs/narr/urldispatch.rst
index 749a2d49a..7e460c885 100644
--- a/docs/narr/urldispatch.rst
+++ b/docs/narr/urldispatch.rst
@@ -70,8 +70,8 @@ via its ``route_name`` predicate, that view callable will always be found and
invoked when the associated route pattern matches during a request.
More commonly, you will not use any ``add_view`` statements in your project's
-"setup" code, instead only using ``add_route`` statements using a
-:term:`scan` for to associate view callables with routes. For example, if
+"setup" code. You will instead use ``add_route`` statements, and use a
+:term:`scan` to associate view callables with routes. For example, if
this is a portion of your project's ``__init__.py``:
.. code-block:: python