From 50946a3693fd443d063e8b3c8347e3d3bb6a56b7 Mon Sep 17 00:00:00 2001 From: Mark Paluch Date: Thu, 17 Apr 2025 15:22:05 +0200 Subject: [PATCH] Polishing. Tweak wording. See #3842 Original pull request: #3843 --- src/main/antora/modules/ROOT/pages/jpa/transactions.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main/antora/modules/ROOT/pages/jpa/transactions.adoc b/src/main/antora/modules/ROOT/pages/jpa/transactions.adoc index c5625296f..c3ca330b3 100644 --- a/src/main/antora/modules/ROOT/pages/jpa/transactions.adoc +++ b/src/main/antora/modules/ROOT/pages/jpa/transactions.adoc @@ -91,5 +91,5 @@ You can use transactions for read-only queries and mark them as such by setting [NOTE] ==== -While this example shows `@Transactional` on the repository interface, we generally recommend defining transaction boundaries at the service layer to reflect business logic units and ensure consistency. -==== \ No newline at end of file +While examples discuss `@Transactional` usage on the repository, we generally recommend declaring transaction boundaries when starting a unit of work to ensure proper consistency and desired transaction participation. +====