simplify the paragraph

mongodb · Dec 15, 2023 · 2dccf6f · 2dccf6f
1 parent 686f8e6
commit 2dccf6f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 10 deletions.
diff --git a/source/retryable-reads/retryable-reads.rst b/source/retryable-reads/retryable-reads.rst
@@ -332,11 +332,8 @@ the caller can infer that an attempt was made and the second error is likely
 more relevant (with respect to the current topology state).
 
 If a driver associates server information (e.g. the server address or
-description) with an error, the driver MUST ensure the server information
-reported with that error corresponds to the server that was selected when the
-error occurred. Specifically, if a retry attempt fails, the server reported
-with the error MUST correspond to the server that was selected for the retry
-and MUST NOT simply be carried over from the original error.
+description) with an error, the driver MUST ensure that the reported server
+information corresponds to the server that originated the error.
 
 4. Implementation constraints
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

diff --git a/source/retryable-writes/retryable-writes.rst b/source/retryable-writes/retryable-writes.rst
@@ -412,11 +412,8 @@ the previous attempt should be raised. If all server errors are labeled
 "NoWritesPerformed", then the first error should be raised.
 
 If a driver associates server information (e.g. the server address or
-description) with an error, the driver MUST ensure the server information
-reported with that error corresponds to the server that was selected when the
-error occurred. Specifically, if a retry attempt fails, the server reported
-with the error MUST correspond to the server that was selected for the retry
-and MUST NOT simply be carried over from the original error.
+description) with an error, the driver MUST ensure that the reported server
+information corresponds to the server that originated the error.
 
 The above rules are implemented in the following pseudo-code: