anchor.diff:  [[writing-tests-built-in-extensions-TempDirectory]]
   ==== The TempDirectory Extension
   
  -The `TempDirectory` extension can be used to create and clean up a temporary directory for
  -an individual test or all tests in a test class. To use it, simply register the extension
  -and add a parameter of type `java.nio.file.Path` annotated with `@TempDir` to your test,
  -lifecycle method, or test class constructor.
  +The `TempDirectory` extension can be used to create and clean up a temporary directory
  +for an individual test or all tests in a test class. To use it, register the extension
  +and add a parameter of type `java.nio.file.Path` annotated with `@TempDir` to your test
  +method, lifecycle method, or test class constructor.
   
   For example, the following test registers the extension for a single test method, creates
  -and writes a file to the temporary directory, and checks its content.
  +and writes to a file in the temporary directory, and checks its content.
   
   [source,java,indent=0]
   .A test method that requires a temporary directory
  
positive.code: If a test class or test interface is not annotated with `@TestInstance`, JUnit Jupiter
  will use a _default_ lifecycle mode. The standard _default_ mode is `PER_METHOD`;
  however, it is possible to change the _default_ for the execution of an entire test plan.
  To change the default test instance lifecycle mode, simply set the
  `junit.jupiter.testinstance.lifecycle.default` _configuration parameter_ to the name of
  an enum constant defined in `TestInstance.Lifecycle`, ignoring case. This can be supplied
  as a JVM system property, as a _configuration parameter_ in the
  
negative.code: `@DisabledOnOs`, etc.) even when the "per-method" test instance lifecycle mode is active.
  
  If you would prefer that JUnit Jupiter execute all test methods on the same test
  instance, annotate your test class with `@TestInstance(Lifecycle.PER_CLASS)`. When using
  this mode, a new test instance will be created once per test class. Thus, if your test
  methods rely on state stored in instance variables, you may need to reset that state in
  `@BeforeEach` or `@AfterEach` methods.
  
  The "per-class" mode has some additional benefits over the default "per-method" mode.
  Specifically, with the "per-class" mode it becomes possible to declare `@BeforeAll` and
  