From 6f06811f113ba0c8590d9102f7624ea749196982 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Mon, 29 Jun 2009 10:34:58 +0000 Subject: --- docs/narr/introduction.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs') 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 `_ 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 -- cgit v1.2.3