@@ -25,7 +25,7 @@ database, see the following:
25
25
- :doc:`/applications/update`
26
26
- :doc:`/applications/delete`
27
27
28
- For information specific :program:`mongo` shell methods used in write
28
+ For information on specific :program:`mongo` shell methods used in write
29
29
operations, see the following:
30
30
31
31
- :method:`db.collection.insert()`
@@ -50,7 +50,7 @@ Write Concern
50
50
51
51
:term:`Write concern <write concern>` confirms the success of write
52
52
operations to MongoDB databases by returning an object indicating
53
- operational success. Beginning with version 2.4 , the :program:`mongo`
53
+ operational success. Beginning with version 2.2.x , the :program:`mongo`
54
54
shell enables write concern by default. In previous versions the shell
55
55
disabled write concern by default.
56
56
@@ -71,7 +71,7 @@ received the write operation and has committed the operation to the
71
71
in-memory representation of the database. This provides a simple and
72
72
low-latency level of write concern and will allow your application to
73
73
detect situations where the :program:`mongod` instance becomes
74
- inaccessible or insertion errors caused by :ref:`duplicate key errors
74
+ inaccessible or detect insertion errors caused by :ref:`duplicate key errors
75
75
<index-type-unique>`.
76
76
77
77
You can modify the level of write concern returned by issuing the
0 commit comments