summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSteve Piercy <web@stevepiercy.com>2017-08-14 18:32:36 -0700
committerGitHub <noreply@github.com>2017-08-14 18:32:36 -0700
commit90693748b980c49e414e512b5f93e20b631701b7 (patch)
treef6f175c5aee618a9b48bc1697dab7376f44e3258 /docs
parent1c8d2cf28e5ca5fe4768345365dc0e3283634274 (diff)
parent85d87f3614d960593a1b2b2d791df1f9bca50bfa (diff)
downloadpyramid-90693748b980c49e414e512b5f93e20b631701b7.tar.gz
pyramid-90693748b980c49e414e512b5f93e20b631701b7.tar.bz2
pyramid-90693748b980c49e414e512b5f93e20b631701b7.zip
Merge pull request #3153 from larsblumberg/change-wording
Update wording on tutorial page
Diffstat (limited to 'docs')
-rw-r--r--docs/quick_tutorial/view_classes.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/quick_tutorial/view_classes.rst b/docs/quick_tutorial/view_classes.rst
index 05d97a9b1..49cdcddcc 100644
--- a/docs/quick_tutorial/view_classes.rst
+++ b/docs/quick_tutorial/view_classes.rst
@@ -12,7 +12,7 @@ Background
==========
So far our views have been simple, free-standing functions. Many times your
-views are related to one another. They may be different ways to look at or work
+views are related to one another. They may consist of different ways to look at or work
on the same data, or be a REST API that handles multiple operations. Grouping
these views together as a :ref:`view class <class_as_view>` makes sense: