Skip to content

Commit 6a1efb9

Browse files
committed
SA feedback
1 parent 10781e0 commit 6a1efb9

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

source/serialization.txt

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,8 @@ types into BSON when you insert a document into a collection. Similarly, when yo
2929
document from a collection, {+driver-short+} automatically converts the returned BSON
3030
back into the corresponding {+language+} types.
3131

32-
The following list shows some {+language+} types that {+driver-short+} can serialize
33-
and deserialize:
32+
You can use {+driver-short+} to serialize and deserialize the following {+language+}
33+
types:
3434

3535
- ``str``
3636
- ``int``
@@ -55,7 +55,7 @@ Serializing Custom Classes
5555
~~~~~~~~~~~~~~~~~~~~~~~~~~
5656

5757
To serialize a custom class, you must convert the class to a dictionary. The following
58-
example serializes a custom class by using the ``vars()`` method, then inserts the
58+
example serializes a custom class by using the ``vars()`` method, and then inserts the
5959
serialized object into a collection:
6060

6161
.. code-block:: python
@@ -77,7 +77,7 @@ Deserializing Custom Classes
7777
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7878

7979
To deserialize a custom class, you must convert the dictionary back into an instance of
80-
the class. The following example retrieves a document from a collection, then converts
80+
the class. The following example retrieves a document from a collection, and then converts
8181
it back into a ``Restaurant`` object from the preceding example:
8282

8383
.. code-block:: python
@@ -95,9 +95,9 @@ Serializing Ordered Documents
9595
-----------------------------
9696

9797
Because the key-value pairs in {+language+} dictionaries are unordered, the order of
98-
fields in serialized BSON documents can differ from the order of fields in the original
98+
fields in serialized BSON documents can differ from the original
9999
dictionary. This behavior can cause issues when {+driver-short+} compares subdocuments
100-
to each other, since {+driver-short+} only considers subdocuments to be equal if their fields
100+
to each other, because {+driver-short+} only considers subdocuments to be equal if their fields
101101
are in identical order.
102102

103103
To preserve the order of keys when serializing and deserializing BSON,

0 commit comments

Comments
 (0)