summaryrefslogtreecommitdiff
path: root/docs/quick_tutorial/view_classes.rst
diff options
context:
space:
mode:
authorPaul Everitt <paul@agendaless.com>2013-09-13 17:09:35 -0400
committerPaul Everitt <paul@agendaless.com>2013-09-13 17:09:35 -0400
commit4042c772c8043ac96a22db439a736fec9ea2aafa (patch)
tree88abca8bdea3781975822b716d7091b607fd1566 /docs/quick_tutorial/view_classes.rst
parentb1b92284f496800a4dfd2cea72cb9be07ba8661c (diff)
downloadpyramid-4042c772c8043ac96a22db439a736fec9ea2aafa.tar.gz
pyramid-4042c772c8043ac96a22db439a736fec9ea2aafa.tar.bz2
pyramid-4042c772c8043ac96a22db439a736fec9ea2aafa.zip
All the references re-wired.
Diffstat (limited to 'docs/quick_tutorial/view_classes.rst')
-rw-r--r--docs/quick_tutorial/view_classes.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/quick_tutorial/view_classes.rst b/docs/quick_tutorial/view_classes.rst
index 0c8976b7f..e06e7f6c0 100644
--- a/docs/quick_tutorial/view_classes.rst
+++ b/docs/quick_tutorial/view_classes.rst
@@ -12,7 +12,7 @@ So far our views have been simple, free-standing functions. Many times
your views are related: different ways to look at or work on the same
data or a REST API that handles multiple operations. Grouping these
together as a
-:ref:`view class <pyramid:class_as_view>` makes sense:
+:ref:`view class <class_as_view>` makes sense:
- Group views
@@ -93,4 +93,4 @@ class. But you can also see the pattern in the tests of instantiating
the view class with the dummy request first, then calling the view
method being tested.
-.. seealso:: :ref:`pyramid:class_as_view`
+.. seealso:: :ref:`class_as_view`