@@ -31,15 +31,15 @@ transactions. Specifically, three cases should be checked:
3131
3232- If the callback raises an error with the ` TransientTransactionError ` label and the retry timeout has been exceeded,
3333 ` withTransaction ` should propagate the error as described in the
34- [ propagation mechanism] ( ../transactions-convenient-api.md#timeout-error-propagation-mechanism ) to its caller.
34+ [ propagation mechanism] ( ../transactions-convenient-api.md#timeout-error-propagation ) to its caller.
3535- If committing raises an error with the ` UnknownTransactionCommitResult ` label, and the retry timeout has been
3636 exceeded, ` withTransaction ` should propagate the error as described in the
37- [ propagation mechanism] ( ../transactions-convenient-api.md#timeout-error-propagation-mechanism ) to its caller
37+ [ propagation mechanism] ( ../transactions-convenient-api.md#timeout-error-propagation ) to its caller
3838- If committing raises an error with the ` TransientTransactionError ` label and the retry timeout has been exceeded,
3939 ` withTransaction ` should propagate the error as described in the
40- [ propagation mechanism] ( ../transactions-convenient-api.md#timeout-error-propagation-mechanism ) to its caller. This
41- case may occur if the commit was internally retried against a new primary after a failover and the second primary
42- returned a ` NoSuchTransaction ` error response.
40+ [ propagation mechanism] ( ../transactions-convenient-api.md#timeout-error-propagation ) to its caller. This case may
41+ occur if the commit was internally retried against a new primary after a failover and the second primary returned a
42+ ` NoSuchTransaction ` error response.
4343
4444If possible, drivers should implement these tests without requiring the test runner to block for the full duration of
4545the retry timeout. This might be done by internally modifying the timeout value used by ` withTransaction ` with some
0 commit comments