1 files changed, 9 insertions, 9 deletions
diff --git a/docs/narr/templates.rst b/docs/narr/templates.rst
index b97cc7be6..ae212fe5e 100644
--- a/docs/narr/templates.rst
+++ b/docs/narr/templates.rst
@@ -203,7 +203,7 @@ may set attributes on the response that influence these values.
 
 Here's an example of changing the content-type and status of the
 response object returned by
-:func:`pyramid.renderers.render_to_response`:
+:func:`~pyramid.renderers.render_to_response`:
 
 .. code-block:: python
    :linenos:
@@ -219,7 +219,7 @@ response object returned by
        return response
 
 Here's an example of manufacturing a response object using the result
-of :func:`pyramid.renderers.render` (a string):
+of :func:`~pyramid.renderers.render` (a string):
 
 .. code-block:: python
    :linenos:
@@ -247,8 +247,8 @@ System Values Used During Rendering
 -----------------------------------
 
 When a template is rendered using
-:func:`pyramid.renderers.render_to_response` or
-:func:`pyramid.renderers.render`, the renderer representing the
+:func:`~pyramid.renderers.render_to_response` or
+:func:`~pyramid.renderers.render`, the renderer representing the
 template will be provided with a number of *system* values.  These
 values are provided in a dictionary to the renderer and include:
 
@@ -282,7 +282,7 @@ variables.
 Templates Used as Renderers via Configuration
 ---------------------------------------------
 
-An alternative to using :func:`pyramid.renderers.render_to_response`
+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 
@@ -299,7 +299,7 @@ The association of a template as a renderer for a :term:`view
 configuration` makes it possible to replace code within a :term:`view
 callable` that handles the rendering of a template.
 
-Here's an example of using a :class:`pyramid.view.view_config`
+Here's an example of using a :class:`~pyramid.view.view_config`
 decorator to specify a :term:`view configuration` that names a
 template renderer:
 
@@ -456,8 +456,8 @@ Here's what a simple :term:`Chameleon` ZPT template used under
 Note the use of :term:`Genshi` -style ``${replacements}`` above.  This
 is one of the ways that :term:`Chameleon` ZPT differs from standard
 ZPT.  The above template expects to find a ``project`` key in the set
-of keywords passed in to it via :func:`pyramid.renderers.render` or
-:func:`pyramid.renderers.render_to_response`. Typical ZPT
+of keywords passed in to it via :func:`~pyramid.renderers.render` or
+:func:`~pyramid.renderers.render_to_response`. Typical ZPT
 attribute-based syntax (e.g. ``tal:content`` and ``tal:replace``) also
 works in these templates.
 
@@ -480,7 +480,7 @@ passing the macro template, or even the macro itself, *into* the rendered
 template.  To do this you can use the :func:`pyramid.renderers.get_renderer`
 API to retrieve the macro template, and pass it into the template being
 rendered via the dictionary returned by the view.  For example, using a
-:term:`view configuration` via a :class:`pyramid.view.view_config` decorator
+:term:`view configuration` via a :class:`~pyramid.view.view_config` decorator
 that uses a :term:`renderer`:
 
 .. code-block:: python