summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarl O. Pinc <kop@meme.com>2013-10-07 16:10:18 -0500
committerKarl O. Pinc <kop@meme.com>2013-10-07 16:10:18 -0500
commit77497acef17d5e5996ac231bf8ac9b679b291316 (patch)
tree0900b763dbd081a5f18290a61719ebeab5040374
parent70b05dfaea547fea328a7054acd921f02be34a87 (diff)
downloadpyramid-77497acef17d5e5996ac231bf8ac9b679b291316.tar.gz
pyramid-77497acef17d5e5996ac231bf8ac9b679b291316.tar.bz2
pyramid-77497acef17d5e5996ac231bf8ac9b679b291316.zip
Docs: renders.rst: Break sentence into two to simplify.
-rw-r--r--docs/narr/renderers.rst11
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/narr/renderers.rst b/docs/narr/renderers.rst
index 49f834ecb..b542e42a2 100644
--- a/docs/narr/renderers.rst
+++ b/docs/narr/renderers.rst
@@ -57,11 +57,12 @@ values from Python dictionaries so, in practice, view callables which use
renderers return Python dictionaries.
View callables can :ref:`explicitly call
-<example_render_to_response_call>` renderers; but typically view
-configuration declares the renderer used to render a view callable's
-results. This is done with the ``renderer`` attribute. For example,
-this call to :meth:`~pyramid.config.Configurator.add_view` associates
-the ``json`` renderer with a view callable:
+<example_render_to_response_call>` renderers, but they typically
+don't. Instead view configuration declares the renderer used to
+render a view callable's results. This is done with the ``renderer``
+attribute. For example, this call to
+:meth:`~pyramid.config.Configurator.add_view` associates the ``json``
+renderer with a view callable:
.. code-block:: python