From b941d96ad786c19c5cbfaf802d29e7ac53bee7d4 Mon Sep 17 00:00:00 2001 From: atandon2024 Date: Fri, 18 Jul 2025 09:37:14 -0700 Subject: [PATCH] Fix to markdown in encryption docs Signed-off-by: atandon2024 --- .../antora/modules/ROOT/pages/mongodb/mongo-encryption.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/antora/modules/ROOT/pages/mongodb/mongo-encryption.adoc b/src/main/antora/modules/ROOT/pages/mongodb/mongo-encryption.adoc index 7e1d525db4..a3ceb85c30 100644 --- a/src/main/antora/modules/ROOT/pages/mongodb/mongo-encryption.adoc +++ b/src/main/antora/modules/ROOT/pages/mongodb/mongo-encryption.adoc @@ -146,7 +146,7 @@ It's useful when you need to explicitly manage data keys, encryption algorithms, ** ✅ Explicit configuration avoids the risk of surprises (e.g. missing configuration because of improper annotations or class-path scanning) ** ⚠️ An Explicit Field Configuration can diverge from the domain model and you must keep it in sync with the domain model -**Derived setup* +**Derived setup** Derived setup relies on annotations in your domain model and automatically generates the required encrypted field configuration from it. This is simpler and recommended for typical Spring applications where your data model is already annotated.