summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/designdefense.rst4
-rw-r--r--docs/narr/views.rst2
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 59b0e5a2d..84b6be907 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -219,7 +219,7 @@ is this:
Using such wrappers, we strive to always hide the ZCA API from application
developers. Application developers should just never know about the ZCA API:
they should call a Python function with some object germane to the domain as
-an argument, and it should returns a result. A corollary that follows is
+an argument, and it should return a result. A corollary that follows is
that any reader of an application that has been written using :app:`Pyramid`
needn't understand the ZCA API either.
@@ -720,7 +720,7 @@ microframeworks and Django boast.
The :mod:`zope.component`, package on which :app:`Pyramid` depends has
transitive dependencies on several other packages (:mod:`zope.event`, and
:mod:`zope.interface`). :app:`Pyramid` also has its own direct dependencies,
-such as :term:`PasteDeploy`, :term:`Chameleon`, :term:`Mako` :term:`WebOb`,
+such as :term:`PasteDeploy`, :term:`Chameleon`, :term:`Mako`, :term:`WebOb`,
:mod:`zope.deprecation` and some of these in turn have their own transitive
dependencies.
diff --git a/docs/narr/views.rst b/docs/narr/views.rst
index fa34cca61..dbc702de8 100644
--- a/docs/narr/views.rst
+++ b/docs/narr/views.rst
@@ -30,7 +30,7 @@ View Callables
View callables are, at the risk of sounding obvious, callable Python
objects. Specifically, view callables can be functions, classes, or instances
-that implement an ``__call__`` method (making the instance callable).
+that implement a ``__call__`` method (making the instance callable).
View callables must, at a minimum, accept a single argument named
``request``. This argument represents a :app:`Pyramid` :term:`Request`