anchor.diff:  ** `GenericPropertiesContextLoader`: loads a standard `ApplicationContext` from Java
   Properties files.
   
  -The following sections explain how to configure the TestContext framework through
  -annotations and provide working examples of how to write unit and integration tests with
  -the framework.
  +The following sections explain how to configure the TestContext framework and provide
  +working examples of how to write unit and integration tests with the framework.
   
   [[testcontext-tel-config]]
   ==== TestExecutionListener configuration
  
positive.code:   for the test instance for which it is responsible. The `TestContext` also delegates to a
    `SmartContextLoader` to load an `ApplicationContext` if requested.
  * `TestContextManager`: The main entry point into the __Spring TestContext Framework__,
    which manages a single `TestContext` and signals events to all registered
    ++TestExecutionListener++s at well-defined test execution points:
  ** prior to any __before class__ or __before all__ methods of a particular testing framework
  ** test instance post-processing
  ** prior to any __before__ or __before each__ methods of a particular testing framework
  ** after any __after__ or __after each__ methods of a particular testing framework
  ** after any __after class__ or __after all__ methods of a particular testing framework
  * `TestExecutionListener`: Defines a __listener__ API for reacting to test execution
    events published by the `TestContextManager` with which the listener is registered. See
    <<testcontext-tel-config>>.
  * `ContextLoader`: Strategy interface introduced in Spring 2.5 for loading an
  
negative.code: 
  Implement `SmartContextLoader` instead of this interface in order to provide support for
  annotated classes, active bean definition profiles, test property sources, context
  hierarchies, and `WebApplicationContext` support.
  
  * `SmartContextLoader`: Extension of the `ContextLoader` interface introduced in Spring
    3.1.
  