@@ -48,7 +48,7 @@ You can set the write concern by setting the ``WriteConcern`` option on a
4848``MongoClientSettings``, ``MongoDatabaseSettings``, or ``MongoCollectionSettings`` object,
4949or by using the ``WithWriteConcern()`` method of a client, database, or collection instance.
5050
51- The ``WriteConcern`` option and ``WithWriteConcern()`` method both accept a
51+ The ``WriteConcern`` option and ``WithWriteConcern()`` method accept a
5252``WriteConcern`` instance as a parameter. You can specify the write concern by
5353using one of the following values:
5454
@@ -114,7 +114,7 @@ You can set the following read concern levels:
114114 that the data has been written to a majority of the replica set members.
115115- ``ReadConern.Available``: The query returns the instance's most recent data.
116116 Provides no guarantee that the data has been written to a majority of the
117- replica set members. ``ReadConcern.AVAILABLE `` is not available for use with
117+ replica set members. ``ReadConcern.Available `` is not available for use with
118118 causally consistent sessions and transactions.
119119- ``ReadConcern.Majority``: The query returns data that has been acknowledged by
120120 a majority of the replica set members.
@@ -148,7 +148,7 @@ collection:
148148 :dedent:
149149
150150To learn more about read concern, see :manual:`Read Concern
151- <reference/read-concern>` in the {+mdb-server+} manual.
151+ </ reference/read-concern>` in the {+mdb-server+} manual.
152152
153153Read Preference
154154---------------
0 commit comments