md formatting

Author: caseyclements

source/bson-binary-vector/bson-binary-vector.md

@@ -181,17 +181,17 @@ End Function
 #### Validation
 
 Drivers MUST validate vector metadata and raise an error if any invariant is violated:
- 
+
 - When unpacking binary data into a FLOAT32 Vector structure, the length of the binary data following the dtype and
     padding MUST be a multiple of 4 bytes.
-- Padding MUST be 0 for all dtypes where padding doesn’t apply, and MUST be within \[0, 7\] for PACKED_BIT.
-- A PACKED_BIT vector MUST NOT be empty if padding is in the range \[1, 7\].
-  - For a PACKED_BIT vector with non-zero padding, ignored bits SHOULD be zero.
-    - When encoding, if ignored bits aren't zero, drivers SHOULD zero out or raise an exception,
-        but drivers MAY leave them as-is if backwards-compatibility is a concern.
-    - When decoding, drivers SHOULD raise an error if decoding non-zero ignored bits,
-        but drivers MAY choose not to for backwards compatibility.
-    - Drivers SHOULD use the next major release to conform to ignored bits being zero. 
+- Padding MUST be 0 for all dtypes where padding doesn’t apply, and MUST be within [0, 7] for PACKED_BIT.
+- A PACKED_BIT vector MUST NOT be empty if padding is in the range [1, 7].
+    - For a PACKED_BIT vector with non-zero padding, ignored bits SHOULD be zero.
+        - When encoding, if ignored bits aren't zero, drivers SHOULD zero out or raise an exception, but drivers MAY leave
+            them as-is if backwards-compatibility is a concern.
+        - When decoding, drivers SHOULD raise an error if decoding non-zero ignored bits, but drivers MAY choose not to for
+            backwards compatibility.
+        - Drivers SHOULD use the next major release to conform to ignored bits being zero.
 
 Drivers MUST perform this validation when a numeric vector and padding are provided through the API, and when unpacking
 binary data (BSON or similar) into a Vector structure.

source/bson-binary-vector/tests/README.md

@@ -59,14 +59,14 @@ MUST assert that the input float array is the same after encoding and decoding.
 
 ### Treatment of non-zero ignored bits
 
-Drivers SHOULD test this behavior, whether an error is thrown or bits are preserved,
-according to their design and version.
-For drivers that haven't been completed, raise an exception.
-For those that have, update to this behavior according to semantic versioning rules.
+Drivers SHOULD test this behavior, whether an error is thrown or bits are preserved, according to their design and
+version. For drivers that haven't been completed, raise an exception. For those that have, update to this behavior
+according to semantic versioning rules.
 
 A vector of length 1 with non-zero ignored bits provides a good example to use.
 
 #### 1. Encoding
+
 ```python
 v = Binary.from_vector([0b11111111], BinaryVectorDtype.PACKED_BIT, padding=7)
 ```
@@ -80,9 +80,8 @@ v = Binary.from_vector([0b11111111], BinaryVectorDtype.PACKED_BIT, padding=7)
 
 ### 3. Comparison
 
-Here is an example that shows that in pymongo < 5.0, one can decode non-zero ignored
-bits, but though these vectors are equivalent after ignoring the last 7 bits, we
-cannot compare their binary representations directly.
+Here is an example that shows that in pymongo < 5.0, one can decode non-zero ignored bits, but though these vectors are
+equivalent after ignoring the last 7 bits, we cannot compare their binary representations directly.
 
 ```python
 b1 = Binary.from_vector([0b10000000], BinaryVectorDtype.PACKED_BIT, padding=7)