more linting

Author: prestonvasquez

source/retryable-writes/retryable-writes.md

@@ -318,7 +318,6 @@ Drivers MUST then retry the operation as many times as necessary until any one o
 
 - CSOT is enabled and the operation times out per
     [Client Side Operations Timeout: Retryability](../client-side-operations-timeout/client-side-operations-timeout.md#retryability).
-    
 
 - CSOT is not enabled and one retry was attempted.
 

source/server-discovery-and-monitoring/server-discovery-and-monitoring.md

@@ -240,7 +240,6 @@ Fields:
     Default null. (Only mongos and shard servers record this field when monitoring config servers as replica sets, at
     least until
     [drivers allow applications to use readConcern "afterOptime".](../max-staleness/max-staleness.md#future-feature-to-support-readconcern-afteroptime))
-    
 
 - (=) `type`: a [ServerType](#servertype) enum value. Default Unknown.
 
@@ -898,7 +897,7 @@ else:
         ):
             # Stale primary.
             # The error field MUST include the substring "primary marked stale due to electionId/setVersion mismatch"
-            replace serverDescription with a default ServerDescription of type "Unknown" 
+            replace serverDescription with a default ServerDescription of type "Unknown"
             checkIfHasPrimary()
             return
 

source/unified-test-format/unified-test-format.md

@@ -1265,7 +1265,6 @@ The structure of each object is as follows:
     When `failureIsRedacted` is present and its value is `true`, the test runner MUST assert that a failure is present and
     that the failure has been redacted according to the rules defined for error redaction in the
     [command logging and monitoring specification](../command-logging-and-monitoring/command-logging-and-monitoring.md#security).
-    
 
     When `false`, the test runner MUST assert that a failure is present and that the failure has NOT been redacted.