summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/renderers.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/narr/renderers.rst b/docs/narr/renderers.rst
index 212832474..bc96f3d7b 100644
--- a/docs/narr/renderers.rst
+++ b/docs/narr/renderers.rst
@@ -630,15 +630,15 @@ Pyramid supports overriding almost every aspect of its setup through its
:ref:`Conflict Resolution <automatic_conflict_resolution>` mechanism. This
means that in most cases overriding a renderer is as simple as using the
:meth:`pyramid.config.Configurator.add_renderer` method to re-define the
-template extension. For example, if we'd like to override the ``json``
-extension to specify a new renderer we could do the following:
+template extension. For example, if you would like to override the ``.txt``
+extension to specify a new renderer you could do the following:
.. code-block:: python
json_renderer = pyramid.renderers.JSON()
config.add_renderer('json', json_renderer)
-After you do this, any views registered with the ``json`` renderer will use
+After doing this, any views registered with the ``json`` renderer will use
the new renderer.
.. index::