summaryrefslogtreecommitdiff
path: root/docs/quick_tutorial
diff options
context:
space:
mode:
Diffstat (limited to 'docs/quick_tutorial')
-rw-r--r--docs/quick_tutorial/jinja2.rst2
-rw-r--r--docs/quick_tutorial/view_classes.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/quick_tutorial/jinja2.rst b/docs/quick_tutorial/jinja2.rst
index 2fc68827b..4faa81fc4 100644
--- a/docs/quick_tutorial/jinja2.rst
+++ b/docs/quick_tutorial/jinja2.rst
@@ -85,7 +85,7 @@ Extra credit
#. We used ``config.include`` which is an imperative configuration to get the
:term:`Configurator` to load ``pyramid_jinja2``'s configuration. What is
- another way could include it into the config?
+ another way we could include it into the config?
.. seealso:: `Jinja2 homepage <http://jinja.pocoo.org/>`_, and
:ref:`pyramid_jinja2 Overview <jinja2:overview>`
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: