@@ -127,7 +127,7 @@ describe('Retry Timeout is Enforced', function () {
127127 } ) ;
128128
129129 // Case 1: If the callback raises an error with the TransientTransactionError label and the retry
130- // timeout has been exceeded, withTransaction should propagate the error (see Note 1) to its caller.
130+ // timeout has been exceeded, withTransaction should propagate the error to its caller.
131131 test (
132132 'callback TransientTransactionError propagated as timeout error when retry timeout exceeded' ,
133133 {
@@ -166,7 +166,7 @@ describe('Retry Timeout is Enforced', function () {
166166 ) ;
167167
168168 // Case 2: If committing raises an error with the UnknownTransactionCommitResult label, and the
169- // retry timeout has been exceeded, withTransaction should propagate the error (see Note 1) to
169+ // retry timeout has been exceeded, withTransaction should propagate the error to
170170 // its caller.
171171 test (
172172 'commit UnknownTransactionCommitResult propagated as timeout error when retry timeout exceeded' ,
@@ -206,7 +206,7 @@ describe('Retry Timeout is Enforced', function () {
206206 ) ;
207207
208208 // Case 3: If committing raises an error with the TransientTransactionError label and the retry
209- // timeout has been exceeded, withTransaction should propagate the error (see Note 1) to its
209+ // timeout has been exceeded, withTransaction should propagate the error to its
210210 // caller. This case may occur if the commit was internally retried against a new primary after a
211211 // failover and the second primary returned a NoSuchTransaction error response.
212212 test (
0 commit comments