summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-06-29 10:34:58 +0000
committerChris McDonough <chrism@agendaless.com>2009-06-29 10:34:58 +0000
commit6f06811f113ba0c8590d9102f7624ea749196982 (patch)
treeb8cd83319cdd59603726c9a0358cf8fc8eff05b3 /docs
parent724f11737383ef5953a8ef2327919fd4c4b9ea6b (diff)
downloadpyramid-6f06811f113ba0c8590d9102f7624ea749196982.tar.gz
pyramid-6f06811f113ba0c8590d9102f7624ea749196982.tar.bz2
pyramid-6f06811f113ba0c8590d9102f7624ea749196982.zip
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/introduction.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index 82f59c8ce..e7b07f059 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -77,10 +77,10 @@ Differences from Other Frameworks
Like :term:`Zope`, the :mod:`repoze.bfg` framework imposes slightly
more `control inversion <http://plope.com/control_inversion>`_ upon
application developers than other Python frameworks such as
-:term:`Pylons`. For example :mod:`repoze.bfg` assumes that you're
-wiling to resolve a URL to a :term:`context` object before passing it
-to a :term:`view`. Pylons and other Python "MVC" frameworks have no
-such intermediate step; they resolve a URL directly to a controller.
+:term:`Pylons`. For example :mod:`repoze.bfg` allows you to
+explicitly resolve a URL to a :term:`context` object before invoking a
+:term:`view`. Pylons and other Python "MVC" frameworks have no such
+intermediate step; they resolve a URL directly to a controller.
Another example: using the :mod:`repoze.bfg` security subsystem
assumes that you're willing to attach an :term:`ACL` to a
:term:`context` object; the ACL is checked by the framework itself