DOCSP-35201 edit for clarity, add list of functions

Author: mballard-mdb

source/crud/transactions.txt

@@ -315,14 +315,20 @@ transaction must be retried:
   an error.
 
 If you are using the Core API to perform a transaction, you must implement the
-error-handling logic into your application. To do so, you must create separate
-functions within your application that explicitly retry transaction and commit
-operations when these errors are detected. To see an
-example of this retry logic, see the :manual:`Core API section
+error-handling logic into your application. To do so, you must create the following functions:
+
+- A function that retries the entire transaction when the driver encounters a
+  ``TransientTransactionError``
+- A function that retries the commit operation when the driver encounters an
+  ``UnknownTransactionCommitResult``
+
+These functions should continue to retry the operation until there is a
+successful commit or a different error. For an example of this retry
+logic, see the :manual:`Core API section
 </core/transactions-in-applications/#core-api>` on the Drivers API page in the
 Server manual.
 
 The Convenient Transaction API incorporates retry logic for these error types,
 so the driver automatically retries the transaction until there is a successful
 commit. You do not have to explicitly declare functions for the API to retry
-transaction operations with these errors. 
+transaction operations when the driver produces these errors.