anchor.diff:  they are particular to an individual request. When the request completes processing, the
   bean that is scoped to the request is discarded.
   
  -When using Java Config, the `@RequestScope` annotation can be used to assign a component
  -to the `request` scope.
  -
  -[source,java,indent=0]
  -[subs="verbatim,quotes"]
  -----
  -	@RequestScope
  +When using annotation-driven components or Java Config, the `@RequestScope` annotation
  +can be used to assign a component to the `request` scope.
  +
  +[source,java,indent=0]
  +[subs="verbatim,quotes"]
  +----
  +	**@RequestScope**
   	@Component
   	public class LoginAction {
   		// ...
  
positive.code: HTTP `Session` is eventually discarded, the bean that is scoped to that particular HTTP
  `Session` is also discarded.
  
  When using Java Config, the `@SessionScope` annotation can be used to assign a component
  to the `session` scope.
  
  [source,java,indent=0]
  [subs="verbatim,quotes"]
  ----
  	@SessionScope
  	@Component
  	public class UserPreferences {
  		// ...
  
negative.code: 'ApplicationContext' (for which there may be several in any given web application),
  and it is actually exposed and therefore visible as a `ServletContext` attribute.
  
  When using annotation-driven components or Java Config, the `@ApplicationScope`
  annotation can be used to assign a component to the `application` scope.
  
  [source,java,indent=0]
  [subs="verbatim,quotes"]
  ----
  	**@ApplicationScope**
  	@Component
  	public class AppPreferences {
  		// ...
  