summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSteve Piercy <web@stevepiercy.com>2016-03-02 03:47:56 -0800
committerSteve Piercy <web@stevepiercy.com>2016-03-02 03:47:56 -0800
commit51f056043f9286734e93cb61f44bb0163c5b1fa3 (patch)
tree4274ec6f8ec16de08c2e417d2b962c3e675c95af /docs
parent530bad618c33d65ad071b0280ce56eb265195805 (diff)
downloadpyramid-51f056043f9286734e93cb61f44bb0163c5b1fa3.tar.gz
pyramid-51f056043f9286734e93cb61f44bb0163c5b1fa3.tar.bz2
pyramid-51f056043f9286734e93cb61f44bb0163c5b1fa3.zip
give sentence a colostomy, break into two
Diffstat (limited to 'docs')
-rw-r--r--docs/quick_tutorial/view_classes.rst9
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/quick_tutorial/view_classes.rst b/docs/quick_tutorial/view_classes.rst
index 50a7ee0af..6198eed63 100644
--- a/docs/quick_tutorial/view_classes.rst
+++ b/docs/quick_tutorial/view_classes.rst
@@ -10,11 +10,10 @@ then move some declarations to the class level.
Background
==========
-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 <class_as_view>` makes sense:
+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
+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:
- Group views