SEC-1359,SEC-1360,SEC-1361,SEC-1363,SEC-1364,SEC-1365,SEC-1366,SEC-1367: Minor doc and Javadoc typos.

docs/manual/src/docbook/appendix-namespace.xml

@@ -67,7 +67,7 @@
       <section xml:id="nsa-realm">
         <title><literal>realm</literal></title>
         <para> Sets the realm name used for basic authentication (if enabled). Corresponds to the
-            <literal>realmName</literal> proerty on
+            <literal>realmName</literal> property on
             <classname>BasicAuthenticationEntryPoint</classname>. </para>
       </section>
       <section xml:id="nsa-entry-point-ref">

docs/manual/src/docbook/core-filters.xml

@@ -246,7 +246,7 @@ class="org.springframework.security.web.context.SecurityContextPersistenceFilter
                     was called <classname>AuthenticationProcessingFilterEntryPoint</classname>.
                     Since the framework now supports many different forms of authentication, they
                     have both been given more specific names in 3.0.</para>
-            </footnote>. It also provides the implementation used by the &lt;form-login&gt; element
+            </footnote>. It also provides the implementation used by the <literal>&lt;form-login&gt;</literal> element
             from the namespace. There are three stages required to configure it. <orderedlist>
                 <listitem>
                     <para>Configure a <classname>LoginUrlAuthenticationEntryPoint</classname> with
@@ -298,8 +298,8 @@ class="org.springframework.security.web.context.SecurityContextPersistenceFilter
             <para>If authentication is successful, the resulting
                     <interfacename>Authentication</interfacename> object will be placed into the
                     <classname>SecurityContextHolder</classname>. The configured
-                AuthenticationSuccessHandler will then be called to either redirect or forward the
-                user to the approprate destination. By default a
+                <interfacename>AuthenticationSuccessHandler</interfacename> will then be called to either redirect or forward the
+                user to the appropriate destination. By default a
                     <classname>SavedRequestAwareAuthenticationSuccessHandler</classname> is used,
                 which means that the user will be redirected to the original destination they
                 requested before they were asked to login. <note>

docs/manual/src/docbook/core-services.xml

@@ -34,10 +34,9 @@
             from a successful authentication and stored in the
                 <classname>SecurityContext</classname>. </para>
         <para> If you are using the namespace, an instance of
-                <classname>ProviderMananger</classname> is created and maintained internally, and
-            you add providers to it either by using the namespace authentication provider elements,
-            or by adding the <literal>&lt;custom-authentication-provider&gt;</literal> element to a
-            bean (see <link xlink:href="#ns-auth-manager">the namespace chapter</link>). In this
+                <classname>ProviderManager</classname> is created and maintained internally, and
+            you add providers to it by using the namespace authentication provider elements 
+            (see <link xlink:href="#ns-auth-manager">the namespace chapter</link>). In this
             case, you should not declare a <classname>ProviderManager</classname> bean in your
             application context. However, if you are not using the namespace then you would declare
             it like so: <programlisting language="xml"><![CDATA[

docs/manual/src/docbook/form-authentication.xml

@@ -51,7 +51,7 @@
             <interfacename>Authentication</interfacename> object will be placed into the
             <classname>SecurityContextHolder</classname>.
             The configured AuthenticationSuccessHandler will then be called to either redirect or forward
-            the user to the approprate destination. By default a <classname>SavedRequestAwareAuthenticationSuccessHandler</classname>
+            the user to the appropriate destination. By default a <classname>SavedRequestAwareAuthenticationSuccessHandler</classname>
             is used, which means that the user will be redirected to the original destination they requested before they were asked to
             login.
             <note>

docs/manual/src/docbook/taglibs.xml

@@ -19,7 +19,7 @@
             </footnote>. The first approach uses a <link xlink:href="el-access-we">web-security
                 expression</link>, specified in the <literal>access</literal> attribute of the tag.
             The expression evaluation will be delegated to the
-                <interfacename>WebSecurityExpressionHandlder</interfacename> defined in the
+                <interfacename>WebSecurityExpressionHandler</interfacename> defined in the
             application context (you should have web expressions enabled in your
                 <literal>&lt;http></literal> namespace configuration to make sure this service is
             available). So, for example, you might

web/src/main/java/org/springframework/security/web/authentication/AbstractAuthenticationTargetUrlRequestHandler.java

@@ -134,7 +134,7 @@ public abstract class AbstractAuthenticationTargetUrlRequestHandler {
     }
 
     /**
-     * The current request will be checked for this parameter before and the value used as the target URL if resent.
+     * The current request will be checked for this parameter before and the value used as the target URL if present.
      *
      *  @param targetUrlParameter the name of the parameter containing the encoded target URL. Defaults
      *  to "redirect".

web/src/main/java/org/springframework/security/web/authentication/UsernamePasswordAuthenticationFilter.java

@@ -29,16 +29,16 @@ import org.springframework.util.Assert;
 
 
 /**
- * Processes an authentication form. Called <tt>AuthenticationProcessingFilter<tt> in previous versions
- * of the framework.
+ * Processes an authentication form submission. Called {@code AuthenticationProcessingFilter} prior to Spring Security
+ * 3.0.
  * <p>
  * Login forms must present two parameters to this filter: a username and
  * password. The default parameter names to use are contained in the
  * static fields {@link #SPRING_SECURITY_FORM_USERNAME_KEY} and {@link #SPRING_SECURITY_FORM_PASSWORD_KEY}.
- * The parameter names can also be changed by setting the <tt>usernameParameter</tt> and <tt>passwordParameter</tt>
+ * The parameter names can also be changed by setting the {@literal usernameParameter} and {@literal passwordParameter}
  * properties.
  * <p>
- * This filter by default responds to the URL <tt>/j_spring_security_check</tt>.
+ * This filter by default responds to the URL {@literal /j_spring_security_check}.
  *
  * @author Ben Alex
  * @author Colin Sampaleanu