diff --git a/spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/data-access.adoc b/spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/data-access.adoc
index 0ece8a00a5..471724ec90 100644
--- a/spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/data-access.adoc
+++ b/spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/data-access.adoc
@@ -178,9 +178,9 @@ include-code::MyApplication[]
 
 
 [[howto.data-access.filter-scanned-entity-definitions]]
-== Filter scanned @Entity definitions
+== Filter Scanned @Entity Definitions
 
-It is possible to exclude some `@Entity` definitions using a `ManagedClassNameFilter` bean.
+It is possible to filter the `@Entity` definitions using a `ManagedClassNameFilter` bean.
 This can be useful in tests when only a sub-set of the available entities should be considered.
 In the following example, only entities from the `com.example.app.customer` package are included: