diff options
| author | Michael Merickel <michael@merickel.org> | 2013-09-04 23:36:01 -0500 |
|---|---|---|
| committer | Michael Merickel <michael@merickel.org> | 2013-09-04 23:36:01 -0500 |
| commit | b56a6ee9c0c58992df67cdeb021f69d51bcfd26d (patch) | |
| tree | 35dfd10a962563a768ce0e32fe58c76adf3516bb | |
| parent | 6ca99b5b42ca13a25a22474c927733d2d16d7cbe (diff) | |
| download | pyramid-b56a6ee9c0c58992df67cdeb021f69d51bcfd26d.tar.gz pyramid-b56a6ee9c0c58992df67cdeb021f69d51bcfd26d.tar.bz2 pyramid-b56a6ee9c0c58992df67cdeb021f69d51bcfd26d.zip | |
change focus from we to you
| -rw-r--r-- | docs/narr/renderers.rst | 6 |
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:: |
