diff --git a/framework-docs/modules/ROOT/pages/testing/annotations/integration-spring/annotation-beanoverriding.adoc b/framework-docs/modules/ROOT/pages/testing/annotations/integration-spring/annotation-beanoverriding.adoc
index 77a210773ca..f2f7655f1f3 100644
--- a/framework-docs/modules/ROOT/pages/testing/annotations/integration-spring/annotation-beanoverriding.adoc
+++ b/framework-docs/modules/ROOT/pages/testing/annotations/integration-spring/annotation-beanoverriding.adoc
@@ -99,9 +99,10 @@ The three annotations introduced above build upon the `@BeanOverride` meta-annot
 and associated infrastructure, which allows to define custom bean overriding variants.
 
 In order to provide an extension, three classes are needed:
- - a concrete `BeanOverrideProcessor<P>`
- - a concrete `OverrideMetadata` created by said processor
- - an annotation meta-annotated with `@BeanOverride(P.class)`
+
+ - A concrete `BeanOverrideProcessor<P>`.
+ - A concrete `OverrideMetadata` created by said processor.
+ - An annotation meta-annotated with `@BeanOverride(P.class)`.
 
 The Spring TestContext Framework includes infrastructure classes that support bean
 overriding: a `BeanPostProcessor`, a `TestExecutionListener` and a `ContextCustomizerFactory`.