From 954ba57cf23464d64e638b13509ccb006bf7e81f Mon Sep 17 00:00:00 2001
From: Rob Winch <rwinch@vmware.com>
Date: Fri, 15 Jun 2012 14:44:12 -0500
Subject: [PATCH] SEC-1970: Cleanup of pre authentication documentation

* Removed custom-authentication-provider from documentation
* Rephrased to make the pre authentication documentation a little more concise
* Removed nested () within text (not code)
* Removed user which should have been use
---
 docs/manual/src/docbook/preauth.xml | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/docs/manual/src/docbook/preauth.xml b/docs/manual/src/docbook/preauth.xml
index 050f0d6e00..8c0fa1b6d0 100644
--- a/docs/manual/src/docbook/preauth.xml
+++ b/docs/manual/src/docbook/preauth.xml
@@ -169,13 +169,9 @@ class="org.springframework.security.web.authentication.preauth.PreAuthenticatedA
       <security:authentication-provider ref="preauthAuthProvider" />
     </security:authentication-manager>
 ]]>
-</programlisting> We've assumed here that the security namespace is being used for configuration
-                    (hence the user of the <literal>custom-filter</literal>,
-                    <literal>authentication-manager</literal> and
-                    <literal>custom-authentication-provider</literal> elements (you can read more
-                    about them in the <link xlink:href="#ns-config">namespace chapter</link>). You
-                    would leave these out of a traditional bean configuration. It's also assumed
-                    that you have added a <interfacename>UserDetailsService</interfacename> (called
+</programlisting> We've assumed here that the <link xlink:href="#ns-config">security namespace</link>
+                    is being used for configuration. It's also assumed that you have added a
+                    <interfacename>UserDetailsService</interfacename> (called
                     <quote>userDetailsService</quote>) to your configuration to load the user's
                     roles. </para>
             </section>