@@ -304,9 +304,9 @@ the ``startTransaction()`` method:
304304Transaction Errors
305305------------------
306306
307- Since MongoDB transactions are :website:`ACID compliant
308- </basics/acid-transactions>`, the driver may produce errors during operation to
309- ensure your data maintains consistent. If the following errors occur, the
307+ Because MongoDB transactions are :website:`ACID compliant
308+ </basics/acid-transactions>`, the driver might produce errors during operation
309+ to ensure your data maintains consistent. If the following errors occur, the
310310transaction must be retried:
311311
312312- ``TransientTransactionError``: Raised if a write operation encounters an error
@@ -320,16 +320,20 @@ transaction must be retried:
320320 description </core/transactions-in-applications/#unknowntransactioncommitresult>`
321321 on the Drivers API page in the Server manual.
322322
323+ The following sections describe how to handle these errors for different APIs.
324+
325+ Convenient Transaction Error Handling
326+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
327+
323328The Convenient Transaction API incorporates retry logic for these error types,
324329so the driver automatically retries the transaction until there is a successful
325330commit.
326331
327332Core API Error Handling
328333~~~~~~~~~~~~~~~~~~~~~~~
329334
330- If you are using the Core API to perform a transaction, you must implement the
331- error-handling logic into your application. To do so, you must create the
332- following functions:
335+ If you are using the Core API to perform a transaction, you must add the following
336+ error-handling functions to your application:
333337
334338- A function that retries the entire transaction when the driver encounters a
335339 ``TransientTransactionError``
0 commit comments