Skip to content

Commit 995d1af

Browse files
author
Bob Grabar
committed
DOCS-249 minor edits
1 parent 748081b commit 995d1af

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

draft/core/write-operations.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ database, see the following:
2525
- :doc:`/applications/update`
2626
- :doc:`/applications/delete`
2727

28-
For information specific :program:`mongo` shell methods used in write
28+
For information on specific :program:`mongo` shell methods used in write
2929
operations, see the following:
3030

3131
- :method:`db.collection.insert()`
@@ -50,7 +50,7 @@ Write Concern
5050

5151
:term:`Write concern <write concern>` confirms the success of write
5252
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`
5454
shell enables write concern by default. In previous versions the shell
5555
disabled write concern by default.
5656

@@ -71,7 +71,7 @@ received the write operation and has committed the operation to the
7171
in-memory representation of the database. This provides a simple and
7272
low-latency level of write concern and will allow your application to
7373
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
7575
<index-type-unique>`.
7676

7777
You can modify the level of write concern returned by issuing the

0 commit comments

Comments
 (0)