summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2010-12-23 19:32:05 -0500
committerChris McDonough <chrism@plope.com>2010-12-23 19:32:05 -0500
commitd1138fdd4fe55358dcb583c5ddee3f45043d1fb5 (patch)
tree5f4ff069015e67e57f97b7ef98211e1168156c47 /docs
parent52a4aabd679a9e9e91a579d1546abd5dfbe2931d (diff)
downloadpyramid-d1138fdd4fe55358dcb583c5ddee3f45043d1fb5.tar.gz
pyramid-d1138fdd4fe55358dcb583c5ddee3f45043d1fb5.tar.bz2
pyramid-d1138fdd4fe55358dcb583c5ddee3f45043d1fb5.zip
fix awkward wording
Diffstat (limited to 'docs')
-rw-r--r--docs/tutorials/wiki/definingviews.rst7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/tutorials/wiki/definingviews.rst b/docs/tutorials/wiki/definingviews.rst
index c051d6db7..2c016b373 100644
--- a/docs/tutorials/wiki/definingviews.rst
+++ b/docs/tutorials/wiki/definingviews.rst
@@ -7,9 +7,10 @@ Conventionally, :term:`view callable` objects are defined within a
automagically special about the filename ``views.py``. Files implementing
views often have ``view`` in their filenames (or may live in a Python
subpackage of your application package named ``views``), but this is only by
-convention. However, a project may have many views throughout its codebase
-in arbitrarily-named files. In this application, we'll be continuing to use
-the ``views.py`` module, because there's no reason to break convention.
+convention. A project may have many views throughout its codebase in
+arbitrarily-named files. In this application, however, we'll be continuing
+to use the ``views.py`` module, because there's no reason to break
+convention.
A :term:`view callable` in a :app:`Pyramid` application is typically a simple
Python function that accepts a single parameter: :term:`request`. A view