From a16ce61a36765c5010bc5b0c82ed6e9ff3f616cf Mon Sep 17 00:00:00 2001 From: Mark Paluch Date: Tue, 9 Feb 2021 11:53:13 +0100 Subject: [PATCH] Polishing. Slightly tweak wording. See #2283 Original pull request: #2285 --- src/main/asciidoc/auditing.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/main/asciidoc/auditing.adoc b/src/main/asciidoc/auditing.adoc index 4fd5dfca8..425adc33f 100644 --- a/src/main/asciidoc/auditing.adoc +++ b/src/main/asciidoc/auditing.adoc @@ -4,8 +4,8 @@ [[auditing.basics]] == Basics Spring Data provides sophisticated support to transparently keep track of who created or changed an entity and when the change happened. To benefit from that functionality, you have to equip your entity classes with auditing metadata that can be defined either using annotations or by implementing an interface. -Additionally auditing has to be enabled either via Java or XML configuration which ensures required infrastructure components get registered. -Please refer to the store specific section for configuration samples. +Additionally, auditing has to be enabled either through Annotation configuration or XML configuration to register the required infrastructure components. +Please refer to the store-specific section for configuration samples. [NOTE] ==== @@ -43,7 +43,6 @@ Auditing metadata does not necessarily need to live in the root level entity but ---- class Customer { - @Embedded private AuditMetadata auditingMetadata; // … further properties omitted