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: extend a particular class hierarchy.
  
  The following section provides an overview of the internals of the TestContext
  framework. If you are only interested in using the framework and not necessarily
  interested in extending it with your own custom listeners or custom loaders, feel free
  to go directly to the configuration (<<testcontext-ctx-management,context management>>,
  <<testcontext-fixture-di,dependency injection>>, <<testcontext-tx,transaction
  management>>), <<testcontext-support-classes,support classes>>, and
  
negative.code: methods within a single test class in JUnit 4). The `TestContextManager` in turn manages a
  `TestContext` that holds the context of the current test. The `TestContextManager` also
  updates the state of the `TestContext` as the test progresses and delegates to
  `TestExecutionListener` implementations, which instrument the actual test execution by
  providing dependency injection, managing transactions, and so on. A `SmartContextLoader`
  is responsible for loading an `ApplicationContext` for a given test class. Consult the
  javadocs and the Spring test suite for further information and examples of various
  implementations.
  
  