@@ -3128,9 +3128,9 @@ include::{testDir}/example/TempDirectoryDemo.java[tags=user_guide_field_injectio
31283128----
31293129
31303130The `@TempDir` annotation has an optional `cleanup` attribute that can be set to either
3131- `NEVER`, `ON_SUCCESS`, or `ALWAYS`. If the cleanup mode is set to `NEVER`, temporary
3132- directories are not deleted after a test completes. If it is set to `ON_SUCCESS`,
3133- temporary directories are deleted only after a test completed successfully.
3131+ `NEVER`, `ON_SUCCESS`, or `ALWAYS`. If the cleanup mode is set to `NEVER`, the temporary
3132+ directory will not be deleted after the test completes. If it is set to `ON_SUCCESS`, the
3133+ temporary directory will only be deleted after the test if the test completed successfully.
31343134
31353135The default cleanup mode is `ALWAYS`. You can use the
31363136`junit.jupiter.tempdir.cleanup.mode.default`
@@ -3166,7 +3166,7 @@ prefix instead of the `junit` constant value.
31663166include::{testDir}/example/TempDirectoryDemo.java[tags=user_guide_factory_name_prefix]
31673167----
31683168
3169- It's also possible to use an in-memory file system like `{Jimfs}` for the creation of the
3169+ It is also possible to use an in-memory file system like `{Jimfs}` for the creation of the
31703170temporary directory. The following example demonstrates how to achieve that.
31713171
31723172[source,java,indent=0]
@@ -3197,18 +3197,17 @@ include::{testDir}/example/TempDirectoryDemo.java[tags=user_guide_composed_annot
31973197Meta-annotations or additional annotations on the field or parameter the `TempDir`
31983198annotation is declared on might expose additional attributes to configure the factory.
31993199Such annotations and related attributes can be accessed via the `AnnotatedElementContext`
3200- parameter of `createTempDirectory` .
3200+ parameter of the `createTempDirectory(...)` method .
32013201
3202- You can use the `junit.jupiter.tempdir.factory.default`
3203- <<running-tests-config-params, configuration parameter>> to specify the fully qualified
3204- class name of the `TempDirFactory` you would like to use by default. Just like for
3205- factories configured via the `factory` attribute of the `@TempDir` annotation,
3206- the supplied class has to implement the `TempDirFactory` interface. The default factory
3207- will be used for all `@TempDir` annotations unless the `factory` attribute of the
3208- annotation specifies a different factory.
3202+ You can use the `junit.jupiter.tempdir.factory.default` <<running-tests-config-params,
3203+ configuration parameter>> to specify the fully qualified class name of the
3204+ `TempDirFactory` you would like to use by default. Just like for factories configured via
3205+ the `factory` attribute of the `@TempDir` annotation, the supplied class has to implement
3206+ the `TempDirFactory` interface. The default factory will be used for all `@TempDir`
3207+ annotations unless the `factory` attribute of the annotation specifies a different factory.
32093208
3210- In summary, the factory for a temporary directory is determined according to the
3211- following precedence rules:
3209+ In summary, the factory for a temporary directory is determined according to the following
3210+ precedence rules:
32123211
321332121. The `factory` attribute of the `@TempDir` annotation, if present
321432132. The default `TempDirFactory` configured via the configuration
0 commit comments