From 9e04d18cd3f349b2961b2241973adcda6f7984b9 Mon Sep 17 00:00:00 2001
From: Ben Alex <ben.alex@springsource.com>
Date: Tue, 23 May 2006 12:07:19 +0000
Subject: [PATCH] SEC-184: Incorrect reference in RunAsManager reference
 documentation.

---
 doc/docbook/acegi.xml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/doc/docbook/acegi.xml b/doc/docbook/acegi.xml
index 26ddbe61ee..3f4a90f75a 100644
--- a/doc/docbook/acegi.xml
+++ b/doc/docbook/acegi.xml
@@ -2488,20 +2488,20 @@ public boolean supports(Class clazz);</programlisting></para>
         <para>The <literal>AbstractSecurityInterceptor</literal> is able to
         temporarily replace the <literal>Authentication</literal> object in
         the <literal>SecurityContext</literal> and
-        <literal>SecurityContextHolder</literal> during the
-        <literal>SecurityInterceptorCallback</literal>. This only occurs if
-        the original <literal>Authentication</literal> object was successfully
-        processed by the <literal>AuthenticationManager</literal> and
+        <literal>SecurityContextHolder</literal> during the secure object
+        callback phase. This only occurs if the original
+        <literal>Authentication</literal> object was successfully processed by
+        the <literal>AuthenticationManager</literal> and
         <literal>AccessDecisionManager</literal>. The
         <literal>RunAsManager</literal> will indicate the replacement
         <literal>Authentication</literal> object, if any, that should be used
         during the <literal>SecurityInterceptorCallback</literal>.</para>
 
         <para>By temporarily replacing the <literal>Authentication</literal>
-        object during a <literal>SecurityInterceptorCallback</literal>, the
-        secured invocation will be able to call other objects which require
-        different authentication and authorization credentials. It will also
-        be able to perform any internal security checks for specific
+        object during the secure object callback phase, the secured invocation
+        will be able to call other objects which require different
+        authentication and authorization credentials. It will also be able to
+        perform any internal security checks for specific
         <literal>GrantedAuthority</literal> objects. Because Acegi Security
         provides a number of helper classes that automatically configure
         remoting protocols based on the contents of the