From 4042c772c8043ac96a22db439a736fec9ea2aafa Mon Sep 17 00:00:00 2001 From: Paul Everitt Date: Fri, 13 Sep 2013 17:09:35 -0400 Subject: All the references re-wired. --- docs/quick_tutorial/views.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/quick_tutorial/views.rst') diff --git a/docs/quick_tutorial/views.rst b/docs/quick_tutorial/views.rst index ee51cdc0d..f36387027 100644 --- a/docs/quick_tutorial/views.rst +++ b/docs/quick_tutorial/views.rst @@ -99,9 +99,9 @@ and the name of the view, can all be different. More on routes later. Earlier we saw ``config.add_view`` as one way to configure a view. This section introduces ``@view_config``. Pyramid's configuration supports -:term:`pyramid:imperative configuration`, such as the +:term:`imperative configuration`, such as the ``config.add_view`` in the previous example. You can also use -:term:`pyramid:declarative configuration`, in which a Python +:term:`declarative configuration`, in which a Python :term:`python:decorator` is placed on the line above the view. Both approaches result in the same final configuration, thus usually, it is simply a matter of taste. @@ -114,7 +114,7 @@ Extra Credit #. Why might ``assertIn`` be a better choice in testing the text in responses than ``assertEqual``? -.. seealso:: :ref:`pyramid:views_chapter`, - :ref:`pyramid:view_config_chapter`, and - :ref:`pyramid:debugging_view_configuration` +.. seealso:: :ref:`views_chapter`, + :ref:`view_config_chapter`, and + :ref:`debugging_view_configuration` -- cgit v1.2.3