summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2010-12-12 11:30:36 -0700
committerCasey Duncan <casey.duncan@gmail.com>2010-12-12 11:30:36 -0700
commit58081111d47fd4beb380fdedc21513d4da052c1b (patch)
tree52de5f389c39e44f754de0d9439f04bb2f059f75
parentd168a0235a11924e49553664b6936aa11c1efc59 (diff)
downloadpyramid-58081111d47fd4beb380fdedc21513d4da052c1b.tar.gz
pyramid-58081111d47fd4beb380fdedc21513d4da052c1b.tar.bz2
pyramid-58081111d47fd4beb380fdedc21513d4da052c1b.zip
rework/clarify opening paragraph
-rw-r--r--docs/narr/templates.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/narr/templates.rst b/docs/narr/templates.rst
index 5177a0a35..4d064d608 100644
--- a/docs/narr/templates.rst
+++ b/docs/narr/templates.rst
@@ -282,11 +282,11 @@ variables.
Templates Used as Renderers via Configuration
---------------------------------------------
-Instead of using the :func:`pyramid.renderers.render_to_response`
-API within the body of a view function directly to render a specific
-template to a response, you may associate a template written in a
-supported templating language with a view indirectly by specifying it
-as a :term:`renderer` in *view configuration*.
+An alternative to using :func:`pyramid.renderers.render_to_response`
+to render templates manually in your view callable code, is
+to specify the template as a :term:`renderer` in your
+*view configuration*. This can be done with any of the
+templating languages supported by :app:`pyramid`.
To use a renderer via view configuration, specify a template
:term:`resource specification` as the ``renderer`` argument or