From 9299422a9e04ecd07f81bea4fdf6975fb7d68b84 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sun, 5 Jul 2009 22:35:28 +0000 Subject: Spelling. --- docs/tutorials/bfgwiki/authorization.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/tutorials/bfgwiki/authorization.rst') diff --git a/docs/tutorials/bfgwiki/authorization.rst b/docs/tutorials/bfgwiki/authorization.rst index 7913240b8..a736b7faa 100644 --- a/docs/tutorials/bfgwiki/authorization.rst +++ b/docs/tutorials/bfgwiki/authorization.rst @@ -15,7 +15,7 @@ Configuring a ``repoze.bfg`` Authentication Policy -------------------------------------------------- For any :mod:`repoze.bfg` application to perform authorization, we -need to add a ``secrity.py`` module and we'll need to change our +need to add a ``security.py`` module and we'll need to change our :term:`application registry` to add an :term:`authentication policy` and a :term:`authorization policy`. @@ -41,7 +41,7 @@ Adding ``security.py`` Add a ``security.py`` module within your package (in the same directory as "run.py", "views.py", etc) with the following content: The groupfinder defined here is an authorization policy "callback"; it -is a be a callable that accepts a userid ana a request. If the userid +is a be a callable that accepts a userid and a request. If the userid exists in the system, the callback will return a sequence of group identifiers (or an empty sequence if the user isn't a member of any groups). If the userid *does not* exist in the system, the callback @@ -74,7 +74,7 @@ and logout views. Add a file named ``login.py`` to your application Changing Existing Views ~~~~~~~~~~~~~~~~~~~~~~~ -Then we need to change each opf our ``view_page``, ``edit_page`` and +Then we need to change each of our ``view_page``, ``edit_page`` and ``add_page`` views in ``views.py`` to pass a "logged in" parameter into its template. We'll add something like this to each view body: -- cgit v1.2.3