summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2010-12-12 10:45:34 -0700
committerCasey Duncan <casey.duncan@gmail.com>2010-12-12 10:45:34 -0700
commitb72f93accef845ccc6f2fe6f19548b5f4893c606 (patch)
treea3ca5a12b8016db1c5fb5936d497eecc851c322f
parent470ad6910148332fa16a96a45806a77201065558 (diff)
downloadpyramid-b72f93accef845ccc6f2fe6f19548b5f4893c606.tar.gz
pyramid-b72f93accef845ccc6f2fe6f19548b5f4893c606.tar.bz2
pyramid-b72f93accef845ccc6f2fe6f19548b5f4893c606.zip
minor clarity improvement
-rw-r--r--docs/narr/templates.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/narr/templates.rst b/docs/narr/templates.rst
index a85c9b535..753b8ddf6 100644
--- a/docs/narr/templates.rst
+++ b/docs/narr/templates.rst
@@ -30,10 +30,10 @@ The most straightforward way to use a template within
:term:`view callable`. You may use whatever API is supplied by a
given templating engine to do so.
-:app:`Pyramid` provides various APIs that allow you to render
-templates directly from within a view callable. For example, if there
-is a :term:`Chameleon` ZPT template named ``foo.pt`` in a directory in
-your application named ``templates``, you can render the template from
+:app:`Pyramid` provides various APIs that allow you to render templates
+directly from within a view callable. For example, if there is a
+:term:`Chameleon` ZPT template named ``foo.pt`` in a directory named
+``templates`` in your application, you can render the template from
within the body of a view callable like so:
.. code-block:: python