Minor change
distinguish between Pyramid itself and view code raising the exception as in previous exception listing. (cherry picked from commit eb166fb)

distinguish between Pyramid itself and view code raising the exception as in previous exception listing. (cherry picked from commit eb166fb)
Minor change
"functions, classes or any callable that accept" was messing with the flow while reading. Proposed change flows a little better for me. (cherry picked from commit 87d8aba)
Pylons
Unified Split

Showing with 2 additions and 3 deletions.

+2 −3 docs/narr/views.rst
diff --git a/docs/narr/views.rst b/docs/narr/views.rst
@@ -246,7 +246,7 @@ within view code, the result of the :term:`Not Found View` will be returned to
 the user agent which performed the request.

 If :exc:`~pyramid.httpexceptions.HTTPForbidden` is raised by Pyramid itself
-within view code, the result of the :term:`Forbidden View` will be returned to
+or within view code, the result of the :term:`Forbidden View` will be returned to
 the user agent which performed the request.

 .. index::
@@ -523,8 +523,7 @@ Alternate View Callable Argument/Calling Conventions
 ----------------------------------------------------

 Usually view callables are defined to accept only a single argument:
-``request``.  However, view callables may alternately be defined as classes,
-functions, or any callable that accept *two* positional arguments: a
+``request``.  However, a view callable may alternately be defined as any class, function, or callable that accepts *two* positional arguments: a
 :term:`context` resource as the first argument and a :term:`request` as the
 second argument.