diff --git a/framework-docs/modules/ROOT/pages/testing/testcontext-framework/ctx-management/context-customizers.adoc b/framework-docs/modules/ROOT/pages/testing/testcontext-framework/ctx-management/context-customizers.adoc
index e30a962de5..1698c61692 100644
--- a/framework-docs/modules/ROOT/pages/testing/testcontext-framework/ctx-management/context-customizers.adoc
+++ b/framework-docs/modules/ROOT/pages/testing/testcontext-framework/ctx-management/context-customizers.adoc
@@ -42,13 +42,15 @@ become cumbersome if a custom factory needs to be used across an entire test sui
 issue is addressed through support for automatic discovery of default
 `ContextCustomizerFactory` implementations through the `SpringFactoriesLoader` mechanism.
 
-Specifically, the modules that make up the testing support in Spring Framework and Spring
+For example, the modules that make up the testing support in Spring Framework and Spring
 Boot declare all core default `ContextCustomizerFactory` implementations under the
 `org.springframework.test.context.ContextCustomizerFactory` key in their
-{spring-framework-code}/spring-test/src/main/resources/META-INF/spring.factories[`META-INF/spring.factories`]
-properties files. Third-party frameworks and developers can contribute their own
-`ContextCustomizerFactory` implementations to the list of default factories in the same
-manner through their own `META-INF/spring.factories` properties files.
+`META-INF/spring.factories` properties files. The `spring.factories` file for the
+`spring-test` module can be viewed
+{spring-framework-code}/spring-test/src/main/resources/META-INF/spring.factories[here].
+Third-party frameworks and developers can contribute their own `ContextCustomizerFactory`
+implementations to the list of default factories in the same manner through their own
+`spring.factories` files.
 
 
 [[testcontext-context-customizers-merging]]
diff --git a/framework-docs/modules/ROOT/pages/testing/testcontext-framework/tel-config.adoc b/framework-docs/modules/ROOT/pages/testing/testcontext-framework/tel-config.adoc
index 358f305b0f..c4117c5d4d 100644
--- a/framework-docs/modules/ROOT/pages/testing/testcontext-framework/tel-config.adoc
+++ b/framework-docs/modules/ROOT/pages/testing/testcontext-framework/tel-config.adoc
@@ -80,13 +80,12 @@ become cumbersome if a custom listener needs to be used across an entire test su
 issue is addressed through support for automatic discovery of default
 `TestExecutionListener` implementations through the `SpringFactoriesLoader` mechanism.
 
-Specifically, the `spring-test` module declares all core default `TestExecutionListener`
+For example, the `spring-test` module declares all core default `TestExecutionListener`
 implementations under the `org.springframework.test.context.TestExecutionListener` key in
-{spring-framework-code}/spring-test/src/main/resources/META-INF/spring.factories[its
-`META-INF/spring.factories` properties file]. Third-party frameworks and developers can
-contribute their own `TestExecutionListener` implementations to the list of default
-listeners in the same manner through their own `META-INF/spring.factories` properties
-file.
+its {spring-framework-code}/spring-test/src/main/resources/META-INF/spring.factories[`META-INF/spring.factories`
+properties file]. Third-party frameworks and developers can contribute their own
+`TestExecutionListener` implementations to the list of default listeners in the same
+manner through their own `spring.factories` files.
 
 [[testcontext-tel-config-ordering]]
 == Ordering `TestExecutionListener` Implementations