Stop referring to JUnit 5 in documentation

Closes gh-34970

framework-docs/modules/ROOT/pages/languages/kotlin/spring-projects-in.adoc

@@ -324,7 +324,7 @@ progresses.
 == Testing
 
 This section addresses testing with the combination of Kotlin and Spring Framework.
-The recommended testing framework is https://junit.org/junit5/[JUnit 5] along with
+The recommended testing framework is https://junit.org/junit5/[JUnit] along with
 https://mockk.io/[Mockk] for mocking.
 
 NOTE: If you are using Spring Boot, see
@@ -335,7 +335,7 @@ NOTE: If you are using Spring Boot, see
 === Constructor injection
 
 As described in the xref:testing/testcontext-framework/support-classes.adoc#testcontext-junit-jupiter-di[dedicated section],
-JUnit Jupiter (JUnit 5) allows constructor injection of beans which is pretty useful with Kotlin
+JUnit Jupiter allows constructor injection of beans which is pretty useful with Kotlin
 in order to use `val` instead of `lateinit var`. You can use
 {spring-framework-api}/test/context/TestConstructor.html[`@TestConstructor(autowireMode = AutowireMode.ALL)`]
 to enable autowiring for all parameters.
@@ -360,7 +360,7 @@ file with a `spring.test.constructor.autowire.mode = all` property.
 === `PER_CLASS` Lifecycle
 
 Kotlin lets you specify meaningful test function names between backticks (```).
-With JUnit Jupiter (JUnit 5), Kotlin test classes can use the `@TestInstance(TestInstance.Lifecycle.PER_CLASS)`
+With JUnit Jupiter, Kotlin test classes can use the `@TestInstance(TestInstance.Lifecycle.PER_CLASS)`
 annotation to enable single instantiation of test classes, which allows the use of `@BeforeAll`
 and `@AfterAll` annotations on non-static methods, which is a good fit for Kotlin.
 
@@ -404,8 +404,8 @@ class IntegrationTests {
 [[specification-like-tests]]
 === Specification-like Tests
 
-You can create specification-like tests with JUnit 5 and Kotlin.
-The following example shows how to do so:
+You can create specification-like tests with Kotlin and JUnit Jupiter's `@Nested` test
+class support. The following example shows how to do so:
 
 [source,kotlin,indent=0]
 ----

framework-docs/modules/ROOT/pages/testing/annotations/integration-junit-jupiter.adoc

@@ -2,8 +2,8 @@
 = Spring JUnit Jupiter Testing Annotations
 
 The following annotations are supported when used in conjunction with the
-xref:testing/testcontext-framework/support-classes.adoc#testcontext-junit-jupiter-extension[`SpringExtension`] and JUnit Jupiter
-(that is, the programming model in JUnit 5):
+xref:testing/testcontext-framework/support-classes.adoc#testcontext-junit-jupiter-extension[`SpringExtension`]
+and JUnit Jupiter (that is, the programming model in JUnit):
 
 * xref:testing/annotations/integration-junit-jupiter.adoc#integration-testing-annotations-junit-jupiter-springjunitconfig[`@SpringJUnitConfig`]
 * xref:testing/annotations/integration-junit-jupiter.adoc#integration-testing-annotations-junit-jupiter-springjunitwebconfig[`@SpringJUnitWebConfig`]

framework-docs/modules/ROOT/pages/testing/annotations/integration-meta.adoc

@@ -140,8 +140,8 @@ Kotlin::
 ======
 
 If we write tests that use JUnit Jupiter, we can reduce code duplication even further,
-since annotations in JUnit 5 can also be used as meta-annotations. Consider the following
-example:
+since annotations in JUnit Jupiter can also be used as meta-annotations. Consider the
+following example:
 
 [tabs]
 ======

framework-docs/modules/ROOT/pages/testing/testcontext-framework.adoc

@@ -9,11 +9,11 @@ deal of importance on convention over configuration, with reasonable defaults th
 can override through annotation-based configuration.
 
 In addition to generic testing infrastructure, the TestContext framework provides
-explicit support for JUnit 4, JUnit Jupiter (AKA JUnit 5), and TestNG. For JUnit 4 and
-TestNG, Spring provides `abstract` support classes. Furthermore, Spring provides a custom
-JUnit `Runner` and custom JUnit `Rules` for JUnit 4 and a custom `Extension` for JUnit
-Jupiter that let you write so-called POJO test classes. POJO test classes are not
-required to extend a particular class hierarchy, such as the `abstract` support classes.
+explicit support for JUnit Jupiter, JUnit 4, and TestNG. For JUnit 4 and TestNG, Spring
+provides `abstract` support classes. Furthermore, Spring provides a custom JUnit `Runner`
+and custom JUnit `Rules` for JUnit 4 and a custom `Extension` for JUnit Jupiter that let
+you write so-called POJO test classes. POJO test classes are not required to extend a
+particular class hierarchy, such as the `abstract` support classes.
 
 The following section provides an overview of the internals of the TestContext framework.
 If you are interested only in using the framework and are not interested in extending it

framework-docs/modules/ROOT/pages/testing/testcontext-framework/support-classes.adoc

@@ -9,7 +9,7 @@ in JUnit and TestNG.
 == SpringExtension for JUnit Jupiter
 
 The Spring TestContext Framework offers full integration with the JUnit Jupiter testing
-framework, introduced in JUnit 5. By annotating test classes with
+framework, originally introduced in JUnit 5. By annotating test classes with
 `@ExtendWith(SpringExtension.class)`, you can implement standard JUnit Jupiter-based unit
 and integration tests and simultaneously reap the benefits of the TestContext framework,
 such as support for loading application contexts, dependency injection of test instances,
@@ -72,8 +72,8 @@ Kotlin::
 ----
 ======
 
-Since you can also use annotations in JUnit 5 as meta-annotations, Spring provides the
-`@SpringJUnitConfig` and `@SpringJUnitWebConfig` composed annotations to simplify the
+Since you can also use annotations in JUnit Jupiter as meta-annotations, Spring provides
+the `@SpringJUnitConfig` and `@SpringJUnitWebConfig` composed annotations to simplify the
 configuration of the test `ApplicationContext` and JUnit Jupiter.
 
 The following example uses `@SpringJUnitConfig` to reduce the amount of configuration