Docs: Link from renderer narrative docs to example render_to_response call, and index the example.

More fully explain the 2 examples, one with render_to_response call
and one without.

1 files changed, 6 insertions, 4 deletions

diff --git a/docs/narr/renderers.rst b/docs/narr/renderers.rst
index 4046c67fa..b86f7298b 100644
--- a/docs/narr/renderers.rst
+++ b/docs/narr/renderers.rst
@@ -56,10 +56,12 @@ serialization techniques.  In practice, renderers obtain application data
 values from Python dictionaries so, in practice, view callables which use
 renderers return Python dictionaries.
 
-View configuration can vary the renderer associated with a view callable via
-the ``renderer`` attribute.  For example, this call to
-:meth:`~pyramid.config.Configurator.add_view` associates the ``json`` renderer
-with a view callable:
+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:
 
 .. code-block:: python