[3.0.x] Fixed #31423 -- Clarified nested atomic() example.

Backport of fa5e7e46d875d4143510944f19d79df7b1739bab from master

1 files changed, 4 insertions, 4 deletions

diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt
index 12e695b2f6..cebec3d7d1 100644
--- a/docs/topics/db/transactions.txt
+++ b/docs/topics/db/transactions.txt
@@ -146,10 +146,10 @@ Django provides a single API to control database transactions.
     In this example, even if ``generate_relationships()`` causes a database
     error by breaking an integrity constraint, you can execute queries in
     ``add_children()``, and the changes from ``create_parent()`` are still
-    there. Note that any operations attempted in ``generate_relationships()``
-    will already have been rolled back safely when ``handle_exception()`` is
-    called, so the exception handler can also operate on the database if
-    necessary.
+    there and bound to the same transaction. Note that any operations attempted
+    in ``generate_relationships()`` will already have been rolled back safely
+    when ``handle_exception()`` is called, so the exception handler can also
+    operate on the database if necessary.
 
     .. admonition:: Avoid catching exceptions inside ``atomic``!