From c96d62a4ea0ce1d4e7478224f1b2da2b05ba060d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Delaporte?=
 <12201973+fredericdelaporte@users.noreply.github.com>
Date: Wed, 31 Jan 2024 17:54:45 +0100
Subject: [PATCH] Adjust the doc about flush on commit

Some warnings are required for the transaction scope case.
---
 doc/reference/modules/manipulating_data.xml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/doc/reference/modules/manipulating_data.xml b/doc/reference/modules/manipulating_data.xml
index c65f9fe6ffe..c57952af1f9 100644
--- a/doc/reference/modules/manipulating_data.xml
+++ b/doc/reference/modules/manipulating_data.xml
@@ -838,9 +838,11 @@ sess.Lock(pk, LockMode.Upgrade);]]></programlisting>
             It is possible to change the default behavior so that flush occurs less frequently.
             The <literal>FlushMode</literal> class defines three different modes:
             only flush at commit time (and only when the NHibernate <literal>ITransaction</literal>
-            API is used, or inside a transaction scope), flush automatically using the explained
-            routine (will only work inside an explicit NHibernate <literal>ITransaction</literal> or
-            inside a transaction scope), or never flush unless
+            API is used, or inside a transaction scope with a legacy option enabled - see
+            <xref linkend="transactions-scopes"/>), flush automatically using the explained
+            routine (will only work inside an explicit NHibernate <literal>ITransaction</literal>, or
+            inside a transaction scope with limitations for flushes on commit - see
+            <xref linkend="transactions-scopes"/>), or never flush unless
             <literal>Flush()</literal> is called explicitly. The last mode is useful for long
             running units of work, where an ISession is kept open and disconnected for a long time
             (see <xref linkend="transactions-optimistic" />).