anchor.diff:  @AfterAll AbstractDatabaseTests.destroyDatabase()
   ----
   
  -The following sequence diagram helps to shed further light on actually what goes on within
  +The following sequence diagram helps to shed further light on what actually goes on within
   the `JupiterTestEngine` when the `DatabaseTestsDemo` test class is executed.
   
   ////
  
positive.code: callbacks implemented by `Extension2`. `Extension1` is therefore said to _wrap_
  `Extension2`.
  
  JUnit Jupiter also guarantees _wrapping_ behavior within class hierarchies for
  user-supplied lifecycle callbacks such as `@BeforeAll`, `@AfterAll`, `@BeforeEach`, and
  `@AfterEach`.
  
  The following examples demonstrate this behavior. Please note that the examples do not
  actually do anything realistic. Instead, they mimic common scenarios for testing
  
negative.code: 
  See corresponding *.txt file in images folder for the source.
  ////
  image::extensions_BrokenLifecycleMethodConfigDemo.png[caption='',title='BrokenLifecycleMethodConfigDemo']
  
  Due to the aforementioned behavior, the JUnit Team recommends that developers declare at
  most one of each type of lifecycle method (i.e., `@BeforeAll`, `@AfterAll`, `@BeforeEach`,
  