diff --git a/docs/modules/ROOT/pages/servlet/authentication/anonymous.adoc b/docs/modules/ROOT/pages/servlet/authentication/anonymous.adoc
index 8485b2e9b6..2ac5d4783c 100644
--- a/docs/modules/ROOT/pages/servlet/authentication/anonymous.adoc
+++ b/docs/modules/ROOT/pages/servlet/authentication/anonymous.adoc
@@ -22,7 +22,7 @@ Classes can be authored more robustly if they know the `SecurityContextHolder` a
 
 [[anonymous-config]]
 == Configuration
-Anonymous authentication support is provided automatically when you use the HTTP configuration (introduced inSpring Security 3.0).
+Anonymous authentication support is provided automatically when you use the HTTP configuration (introduced in Spring Security 3.0).
 You can customize (or disable) it by using the `<anonymous>` element.
 You need not configure the beans described here unless you are using traditional bean configuration.
 
diff --git a/docs/modules/ROOT/pages/servlet/authentication/architecture.adoc b/docs/modules/ROOT/pages/servlet/authentication/architecture.adoc
index ed8542a607..725fd46d7e 100644
--- a/docs/modules/ROOT/pages/servlet/authentication/architecture.adoc
+++ b/docs/modules/ROOT/pages/servlet/authentication/architecture.adoc
@@ -200,7 +200,7 @@ If the `Authentication` contains a reference to an object in the cache (such as
 You need to take this into account if you use a cache.
 An obvious solution is to first make a copy of the object, either in the cache implementation or in the `AuthenticationProvider` that creates the returned `Authentication` object.
 Alternatively, you can disable the `eraseCredentialsAfterAuthentication` property on `ProviderManager`.
-See the Javadoc for the {security-api-url}org/springframework/security/authentication/ProviderManager.html[Javadoc] class.
+See the Javadoc for the {security-api-url}org/springframework/security/authentication/ProviderManager.html[ProviderManager] class.
 
 [[servlet-authentication-authenticationprovider]]
 == AuthenticationProvider