diff --git a/source/core/create.txt b/source/core/create.txt index 70e50e5aecb..f44d53773fb 100644 --- a/source/core/create.txt +++ b/source/core/create.txt @@ -490,8 +490,8 @@ collection [#previous-versions-upsert]_: .. _crud-create-save: -Update operations with with ``save()`` -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Update operations with ``save()`` +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The :method:`~db.collection.save()` method is identical to an :ref:`update operation with the upsert flag ` diff --git a/source/core/indexes.txt b/source/core/indexes.txt index a8fa66077a6..fbab9131932 100644 --- a/source/core/indexes.txt +++ b/source/core/indexes.txt @@ -406,7 +406,7 @@ arrays, as in the following example: and would add items to the index for all of the sub-documents in the array. - With an index, such as ``{ comments.text: 1 }`` you, consider the + With an index, such as ``{ comments.text: 1 }``, consider the following query: .. code-block:: javascript diff --git a/source/core/replication-internals.txt b/source/core/replication-internals.txt index 0cf1f353897..c3bd8d01447 100644 --- a/source/core/replication-internals.txt +++ b/source/core/replication-internals.txt @@ -247,7 +247,7 @@ entries from other members. Members sync data at two different points: restored member, populating the member with the replica set's data. When a new or restored member joins or rejoins a set, the member waits to receive heartbeats from other members. By default, the member - syncs from the *the closest* member of the set that is either the + syncs from the *closest* member of the set that is either the primary or another secondary with more recent oplog entries. This prevents two secondaries from syncing from each other. diff --git a/source/faq/concurrency.txt b/source/faq/concurrency.txt index a0de591aa9e..4c0e9304145 100644 --- a/source/faq/concurrency.txt +++ b/source/faq/concurrency.txt @@ -125,11 +125,10 @@ Which administrative commands lock the database? Certain administrative commands can exclusively lock the database for extended periods of time. In some deployments, for large databases, -you may consider taking the -the :program:`mongod` instance offline so that clients are not affected. -For example, if a :program:`mongod` is part of a :term:`replica set`, -take the :program:`mongod` offline and let other members of the set -service load while maintenance is in progress. +you may consider taking the :program:`mongod` instance offline so that +clients are not affected. For example, if a :program:`mongod` is part +of a :term:`replica set`, take the :program:`mongod` offline and let +other members of the set service load while maintenance is in progress. The following administrative operations require an exclusive (i.e. write) lock to a the database for extended periods: diff --git a/source/faq/diagnostics.txt b/source/faq/diagnostics.txt index 9a7b83f1024..0541c551b77 100644 --- a/source/faq/diagnostics.txt +++ b/source/faq/diagnostics.txt @@ -23,8 +23,8 @@ Where can I find information about a ``mongod`` process that stopped running une If :program:`mongod` shuts down unexpectedly on a UNIX or UNIX-based platform, and if :program:`mongod` fails to log a shutdown or error message, then check your system logs for messages pertaining to MongoDB. -For example, for logs located in in ``/var/log/messages``, -use the following commands: +For example, for logs located in ``/var/log/messages``, use the +following commands: .. code-block:: sh diff --git a/source/reference/method/db.collection.findAndModify.txt b/source/reference/method/db.collection.findAndModify.txt index b043997623d..89467c88f7f 100644 --- a/source/reference/method/db.collection.findAndModify.txt +++ b/source/reference/method/db.collection.findAndModify.txt @@ -97,7 +97,7 @@ db.collection.findAndModify() .. note:: - If no document is found for the ``update`` or ``remove``, the - the method returns ``null``. + method returns ``null``. - If no document is found for an ``upsert``, which means the command performs an insert, and ``new`` is ``false``, **and** diff --git a/source/tutorial/deploy-shard-cluster.txt b/source/tutorial/deploy-shard-cluster.txt index c2ef0f8ec07..4a2705556b1 100644 --- a/source/tutorial/deploy-shard-cluster.txt +++ b/source/tutorial/deploy-shard-cluster.txt @@ -117,7 +117,7 @@ You would issue the following command: Add Shards to the Cluster ------------------------- -A :term:`shard` can be a standalone :program:`mongod` or or a +A :term:`shard` can be a standalone :program:`mongod` or a :term:`replica set`. In a production environment, each shard should be a replica set. diff --git a/source/tutorial/migrate-config-servers-with-different-hostnames.txt b/source/tutorial/migrate-config-servers-with-different-hostnames.txt index 08aa0428931..0af4b222eec 100644 --- a/source/tutorial/migrate-config-servers-with-different-hostnames.txt +++ b/source/tutorial/migrate-config-servers-with-different-hostnames.txt @@ -9,7 +9,7 @@ in a :doc:`sharded cluster ` to a new server that uses a different hostname. Use this procedure only if the config server *will not* be accessible via the same hostname. If possible, avoid changing the hostname so that you can instead use the -the procedure to :doc:`migrate a config server and use the same hostname +procedure to :doc:`migrate a config server and use the same hostname `. #. Disable the cluster balancer process temporarily. See