diff --git a/framework-docs/modules/ROOT/pages/testing/unit.adoc b/framework-docs/modules/ROOT/pages/testing/unit.adoc
index 6f6ce7a108e..249e58c07b7 100644
--- a/framework-docs/modules/ROOT/pages/testing/unit.adoc
+++ b/framework-docs/modules/ROOT/pages/testing/unit.adoc
@@ -26,7 +26,6 @@ are described in this chapter.
 Spring includes a number of packages dedicated to mocking:
 
 * xref:testing/unit.adoc#mock-objects-env[Environment]
-* xref:testing/unit.adoc#mock-objects-jndi[JNDI]
 * xref:testing/unit.adoc#mock-objects-servlet[Servlet API]
 * xref:testing/unit.adoc#mock-objects-web-reactive[Spring Web Reactive]
 
@@ -42,20 +41,6 @@ and xref:core/beans/environment.adoc#beans-property-source-abstraction[`Property
 out-of-container tests for code that depends on environment-specific properties.
 
 
-[[mock-objects-jndi]]
-=== JNDI
-
-The `org.springframework.mock.jndi` package contains a partial implementation of the JNDI
-SPI, which you can use to set up a simple JNDI environment for test suites or stand-alone
-applications. If, for example, JDBC `DataSource` instances get bound to the same JNDI
-names in test code as they do in a Jakarta EE container, you can reuse both application code
-and configuration in testing scenarios without modification.
-
-WARNING: The mock JNDI support in the `org.springframework.mock.jndi` package is
-officially deprecated as of Spring Framework 5.2 in favor of complete solutions from third
-parties such as https://github.com/h-thurow/Simple-JNDI[Simple-JNDI].
-
-
 [[mock-objects-servlet]]
 === Servlet API