Polishing.

Fine tuned wording.
Fixed a minor typo.

Original pull request #3384
See #3383

Author: schauder

src/main/antora/modules/ROOT/pages/aot.adoc

@@ -39,18 +39,18 @@ However, there users may fine tune the configuration with following options.
 |`spring.aot.data.accessors.include`
 |Comma separated list of FQCN for which to contribute Bytecode for generated Type/Property Accessors.
 Ant-style include patterns matching package names (e.g. `example.springdata.**`) or type names inclusion.
-Inclusion pattern matches are evaluated before exclusions for broad exclusion and selective inclusion.
+If a type is matched by an inclusion and an exclusion, the inclusion wins and the type is considered included.
 
 |`spring.aot.data.accessors.exclude`
 |Comma separated list of FQCN for which to skip contribution of Bytecode for generated Type/Property Accessors.
 Ant-style exclude patterns matching package names (e.g. `example.springdata.**`) or type names exclusion.
-Exclusion pattern matches are evaluated after inclusions for broad exclusion and selective inclusion.
+If a type is matched by an inclusion and an exclusion, the inclusion wins and the type is considered included.
 
 |`spring.aot.repositories.enabled`
 |Boolean flag to control contribution of Source Code for Repository Interfaces
 
 |`spring.aot.[module-name].repositories.enabled`
-|Boolean flag to control contribution of Source Code for Repository Interfaces for a certain module (eg. `cassandra`, `jdbc`, `jpa`, `mongodb`)
+|Boolean flag to control contribution of Source Code for Repository Interfaces for a certain module (e.g. `cassandra`, `jdbc`, `jpa`, `mongodb`)
 
 |`spring.aot.repositories.metadata.enabled`
 |Boolean flag to control contribution of JSON repository metadata containing query methods and actual query strings.

src/main/antora/modules/ROOT/pages/auditing.adoc

@@ -34,7 +34,10 @@ class Customer {
 As you can see, the annotations can be applied selectively, depending on which information you want to capture.
 The annotations, indicating to capture when changes are made, can be used on properties of type JDK8 date and time types, `long`, `Long`, and legacy Java `Date` and `Calendar`.
 
-The time giving instance is provided by a `org.springframework.data.auditing.DateTimeProvider`, defaulting to `CurrentDateTimeProvider`, unless configured via the `dateTimeProviderRef` attribute when enabling auditing, or a dedicated `AuditingHandler` respectively `DateTimeProvider` bean being present in the `ApplicationContext`.
+The time giving instance is provided by a `org.springframework.data.auditing.DateTimeProvider`.
+By default this is a `CurrentDateTimeProvider`.
+This can be changed via the `dateTimeProviderRef` attribute when enabling auditing, or a dedicated `AuditingHandler` or `DateTimeProvider` bean being present in the `ApplicationContext`.
+
 
 Auditing metadata does not necessarily need to live in the root level entity but can be added to an embedded one (depending on the actual store in use), as shown in the snippet below.