anchor.diff:  
   The default execution mode is applied to all nodes of the test tree with a few notable
   exceptions, namely test classes that use the `Lifecycle.PER_CLASS` mode or a
  -`{MethodOrderer}` (except for `{Random}`). In the former case, test authors have to ensure
  -that the test class is thread-safe; in the latter, concurrent execution might conflict
  -with the configured execution order. Thus, in both cases, test methods in such test
  -classes are only executed concurrently if the `@Execution(CONCURRENT)` annotation is
  +`{MethodOrderer}` (except for `{Random}`). In the former case, test authors have to
  +ensure that the test class is thread-safe; in the latter, concurrent execution might
  +conflict with the configured execution order. Thus, in both cases, test methods in such
  +test classes are only executed concurrently if the `@Execution(CONCURRENT)` annotation is
   present on the test class or method.
   
  -All nodes of the test tree that with execution mode `CONCURRENT` will be executed fully in
  -parallel according to the provided <<writing-tests-parallel-execution-config,
  -configuration>> while observing the declarative
  -<<writing-tests-parallel-execution-synchronization, synchronization>> mechanism. Please
  -note that <<running-tests-capturing-output>> needs to be enabled separately.
  +All nodes of the test tree that are configured with the `CONCURRENT` execution mode will
  +be executed fully in parallel according to the provided
  +<<writing-tests-parallel-execution-config, configuration>> while observing the
  +declarative <<writing-tests-parallel-execution-synchronization, synchronization>>
  +mechanism. Please note that <<running-tests-capturing-output>> needs to be enabled
  +separately.
   
   [[writing-tests-parallel-execution-config]]
   ==== Configuration
  
positive.code: `custom` strategy.
  
  To select a strategy, set the `junit.jupiter.execution.parallel.config.strategy`
  configuration parameter to one of the following options:
  
  `dynamic`::
    Computes the desired parallelism based on the number of available processors/cores
  
negative.code: specific shared resource that requires synchronized access to ensure reliable test
  execution. The shared resource is identified by a unique name which is a `String`. The
  name can be user-defined or one of the predefined constants in `{Resources}`:
  `SYSTEM_PROPERTIES`, `SYSTEM_OUT`, `SYSTEM_ERR`, `LOCALE`, or `TIME_ZONE`.
  
  If the tests in the following example were run in parallel _without_ the use of
  {ResourceLock}, they would be _flaky_. Sometimes they would pass, and at other times they
  