anchor.diff:  Common use cases include acquiring the test instance from a dependency injection
   framework or invoking a static factory method to create the test class instance.
   
  -If no `TestInstanceFactory` is registered, the framework will simply invoke the _sole_
  +If no `TestInstanceFactory` is registered, the framework will invoke the _sole_
   constructor for the test class to instantiate it, potentially resolving constructor
   arguments via registered `ParameterResolver` extensions.
   
  
positive.code: The following examples demonstrate this behavior. Please note that the examples do not
  actually do anything realistic. Instead, they mimic common scenarios for testing
  interactions with the database. All methods imported statically from the `Logger` class
  simply log contextual information in order to help us better understand the execution
  order of user-supplied callback methods and callback methods in extensions.
  
  [source,java,indent=0]
  .Extension1
  
negative.code: ===== Enabling Automatic Extension Detection
  
  Auto-detection is an advanced feature and is therefore not enabled by default. To enable
  it, set the `junit.jupiter.extensions.autodetection.enabled` _configuration parameter_ to
  `true`. This can be supplied as a JVM system property, as a _configuration parameter_ in
  the `LauncherDiscoveryRequest` that is passed to the `Launcher`, or via the JUnit Platform
  configuration file (see <<running-tests-config-params>> for details).
  
  For example, to enable auto-detection of extensions, you can start your JVM with the
  following system property.
  