summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJulien Cigar <julien.cigar@gmail.com>2015-10-26 23:55:45 +0100
committerJulien Cigar <julien.cigar@gmail.com>2015-10-26 23:55:45 +0100
commit8bafd90d6143230391723e1a079f7914af2381ed (patch)
tree3bd27372b90a636518e8388f025ab76ec32a5d69 /docs
parentc32c8a4375543b563b2e7eb4bffe917b89a881ea (diff)
downloadpyramid-8bafd90d6143230391723e1a079f7914af2381ed.tar.gz
pyramid-8bafd90d6143230391723e1a079f7914af2381ed.tar.bz2
pyramid-8bafd90d6143230391723e1a079f7914af2381ed.zip
.txt -> json
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/renderers.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/renderers.rst b/docs/narr/renderers.rst
index cc5baf05e..50e85813a 100644
--- a/docs/narr/renderers.rst
+++ b/docs/narr/renderers.rst
@@ -609,8 +609,8 @@ 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 redefine the
-template extension. For example, if you would like to override the ``.txt``
-extension to specify a new renderer, you could do the following:
+template extension. For example, if you would like to override the ``json``
+renderer to specify a new renderer, you could do the following:
.. code-block:: python