@@ -27,6 +27,10 @@ transaction is committed. If any operation in the transaction returns an
2727error, the driver cancels the transaction and discards all data changes
2828before they ever become visible.
2929
30+ In MongoDB, transactions run within logical **sessions**. A
31+ session is a grouping of related read or write operations that you
32+ intend to run sequentially.
33+
3034When using the {+driver-short+}, you can create a new session from a
3135``MongoClient`` instance as a ``ClientSession`` type. We recommend that you reuse
3236your client for multiple sessions and transactions instead of
@@ -47,10 +51,6 @@ instantiating a new client each time.
4751Causal Consistency
4852~~~~~~~~~~~~~~~~~~
4953
50- In MongoDB, transactions run within logical **sessions**. A
51- session is a grouping of related read or write operations that you
52- intend to run sequentially.
53-
5454MongoDB enables **causal consistency** in client sessions, which allows
5555you to execute operations in an :website:`ACID transaction </basics/acid-transactions>`.
5656The causal consistency model guarantees that operations within a session
@@ -71,8 +71,8 @@ causal relationship between the following operations:
7171 To learn more about the concepts mentioned in this section, see the
7272 following {+mdb-server+} manual entries:
7373
74- - :manual:`Server Sessions </reference/server-sessions/>`
7574 - :manual:`Causal Consistency </core/read-isolation-consistency-recency/#causal-consistency>`
75+ - :manual:`Causal Consistency and Read and Write Concerns </core/causal-consistency-read-write-concerns/>`
7676
7777Methods
7878-------
0 commit comments