Skip to content

Commit 7067dbd

Browse files
committed
feedback
1 parent cda9e05 commit 7067dbd

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

source/fundamentals/serialization/guid-serialization.txt

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,8 @@ also known as **universally unique identifiers** (UUIDs).
2828

2929
In MongoDB applications, you can use the
3030
`ObjectId <{+new-api-root+}/api/MongoDB.Bson/MongoDB.Bson.ObjectId.html>`__ type
31-
as a unique identifier for a document. Consider using ``ObjectId`` in place of a GUID
32-
in MongoDB applications where possible.
31+
as a unique identifier for a document. Consider using ``ObjectId`` instances in place
32+
of GUIDs in MongoDB applications where possible.
3333

3434
GUIDs in MongoDB
3535
----------------
@@ -43,11 +43,12 @@ The following code block shows an example GUID:
4343
00112233-4455-6677-8899-aabbccddeeff
4444

4545
Originally, MongoDB represented GUIDs as ``BsonBinaryData``
46-
values of subtype 3. Because subtype 3 didn't standardize the byte order of GUIDs
46+
values of :manual:`subtype 3. </reference/bson-types/#binary-data>`
47+
Because subtype 3 didn't standardize the byte order of GUIDs
4748
during encoding, different MongoDB drivers encoded GUIDs with different byte orders.
4849

49-
Use the following tabs to compare the ways in which different MongoDB language drivers
50-
encoded the preceding GUID to ``BsonBinaryData`` subtype 3:
50+
The following tabs show different driver encodings of the preceding GUID to
51+
``BsonBinaryData`` subtype 3:
5152

5253
.. tabs::
5354

0 commit comments

Comments
 (0)