diff --git a/source/core/index-single.txt b/source/core/index-single.txt index a8c28ca4ade..18c1815ae16 100644 --- a/source/core/index-single.txt +++ b/source/core/index-single.txt @@ -59,7 +59,7 @@ field. Think of the ``_id`` field as the :term:`primary key` for a collection. Every document *must* have a unique ``_id`` field. You may store any unique value in the ``_id`` field. The default value of ``_id`` is an -:term:`ObjectId` on generated when the client inserts the document. An +:term:`ObjectId` which is generated when the client inserts the document. An :term:`ObjectId` is a 12-byte unique identifier suitable for use as the value of an ``_id`` field. diff --git a/source/core/read-operations-introduction.txt b/source/core/read-operations-introduction.txt index 3d6d148c2da..d90cd9a86d9 100644 --- a/source/core/read-operations-introduction.txt +++ b/source/core/read-operations-introduction.txt @@ -109,7 +109,7 @@ applications, include a :term:`projection` in the queries. By projecting results with a subset of fields, applications reduce their network overhead and processing requirements. -Projections, which are the the *second* argument to the +Projections, which are the *second* argument to the :method:`~db.collection.find()` method, may either specify a list of fields to return *or* list fields to exclude in the result documents. diff --git a/source/includes/steps-2.6-downgrade-replica-set.yaml b/source/includes/steps-2.6-downgrade-replica-set.yaml index 5f1b65437b8..047654a87a4 100644 --- a/source/includes/steps-2.6-downgrade-replica-set.yaml +++ b/source/includes/steps-2.6-downgrade-replica-set.yaml @@ -29,7 +29,7 @@ title: character: "`" ref: step-down-primary pre: | - Use :method:`rs.stepDown()` in the the :program:`mongo` shell to + Use :method:`rs.stepDown()` in the :program:`mongo` shell to step down the :term:`primary` and force the normal :ref:`failover ` procedure. action: diff --git a/source/includes/steps-2.6-upgrade-authorization.yaml b/source/includes/steps-2.6-upgrade-authorization.yaml index bc3896b4071..f1f24f809c7 100644 --- a/source/includes/steps-2.6-upgrade-authorization.yaml +++ b/source/includes/steps-2.6-upgrade-authorization.yaml @@ -21,7 +21,7 @@ action: - heading: text: Run ``authSchemaUpgrade`` command. character: "'" - langauge: javascript + language: javascript code: | res = db.getSiblingDB("admin").runCommand({authSchemaUpgrade: 1 }); print(tojson(res)); @@ -37,7 +37,7 @@ action: upgrade is complete. You can, however, override this behavior by including ``upgradeShards: false`` in the command, as in the following example: - langauge: javascript + language: javascript code: | res = db.getSiblingDB("admin").runCommand({authSchemaUpgrade: 1, upgradeShards: false }); diff --git a/source/includes/steps-2.6-upgrade-downgrade-procedure.yaml b/source/includes/steps-2.6-upgrade-downgrade-procedure.yaml index 73cc07c9733..ac74183aef7 100644 --- a/source/includes/steps-2.6-upgrade-downgrade-procedure.yaml +++ b/source/includes/steps-2.6-upgrade-downgrade-procedure.yaml @@ -4,7 +4,7 @@ ref: stop-mongod pre: | Use the :option:`--shutdown ` option as follows: action: - langauge: sh + language: sh code: | mongod --dbpath /var/mongod/data --shutdown post: | diff --git a/source/includes/steps-2.6-upgrade-replica-set.yaml b/source/includes/steps-2.6-upgrade-replica-set.yaml index c8cb5063ac6..a073369163e 100644 --- a/source/includes/steps-2.6-upgrade-replica-set.yaml +++ b/source/includes/steps-2.6-upgrade-replica-set.yaml @@ -14,7 +14,7 @@ title: Step down the replica set primary. stepnum: 2 ref: upgrade-secondaries content: | - Use :method:`rs.stepDown()` in the the :program:`mongo` shell to + Use :method:`rs.stepDown()` in the :program:`mongo` shell to step down the :term:`primary` and force the set to :ref:`failover `. :method:`rs.stepDown()` expedites the failover procedure and is preferable to shutting down diff --git a/source/includes/steps-adjust-replica-set-member-priority.yaml b/source/includes/steps-adjust-replica-set-member-priority.yaml index acfa13c7608..037dc70caae 100644 --- a/source/includes/steps-adjust-replica-set-member-priority.yaml +++ b/source/includes/steps-adjust-replica-set-member-priority.yaml @@ -1,6 +1,6 @@ title: Copy the replica set configuration to a variable. stepnum: 1 -ref: copy-configration-object +ref: copy-configuration-object pre: | In the :program:`mongo` shell, use :method:`rs.conf()` to retrieve the replica set configuration and assign it to a variable. For diff --git a/source/reference/operator/aggregation/redact.txt b/source/reference/operator/aggregation/redact.txt index a2e599fd854..09012dd43ac 100644 --- a/source/reference/operator/aggregation/redact.txt +++ b/source/reference/operator/aggregation/redact.txt @@ -254,7 +254,7 @@ The aggregation operation returns the following "redacted" document: "status" : "A" } -The result set shows that the the :pipeline:`$redact` stage excluded +The result set shows that the :pipeline:`$redact` stage excluded the field ``cc`` as a whole, including the ``shipping_addr`` field which contained subdocuments that had ``level`` field values equal to ``3`` and not ``5``. diff --git a/source/reference/operator/update/rename.txt b/source/reference/operator/update/rename.txt index 262037ca8e2..653284a8b8e 100644 --- a/source/reference/operator/update/rename.txt +++ b/source/reference/operator/update/rename.txt @@ -43,7 +43,7 @@ elements. Examples -------- -A collection ``students`` the the following document where a field +A collection ``students`` the following document where a field ``nmae`` appears misspelled, i.e. should be ``name``: .. code-block:: javascript diff --git a/source/reference/operator/update/slice.txt b/source/reference/operator/update/slice.txt index 2b395a1e336..8d03354552c 100644 --- a/source/reference/operator/update/slice.txt +++ b/source/reference/operator/update/slice.txt @@ -48,7 +48,7 @@ $slice The ```` can be: - - **zero** to update the the array ```` to an empty array, + - **zero** to update the array ```` to an empty array, - **negative** to update the array ```` to contain only the last ```` elements, or diff --git a/source/release-notes/2.6-upgrade-authorization.txt b/source/release-notes/2.6-upgrade-authorization.txt index 565a666edeb..653babe9d3b 100644 --- a/source/release-notes/2.6-upgrade-authorization.txt +++ b/source/release-notes/2.6-upgrade-authorization.txt @@ -43,7 +43,7 @@ Sharded Clusters ```````````````` For a sharded cluster, connect to a :program:`mongos` and run the -upgrade procedure to upgrade the the cluster's authorization data. By +upgrade procedure to upgrade the cluster's authorization data. By default, the procedure will upgrade the authorization data of the shards as well. diff --git a/source/tutorial/adjust-replica-set-member-priority.txt b/source/tutorial/adjust-replica-set-member-priority.txt index 7a4fd880c15..9de50f86cab 100644 --- a/source/tutorial/adjust-replica-set-member-priority.txt +++ b/source/tutorial/adjust-replica-set-member-priority.txt @@ -21,7 +21,7 @@ Considerations -------------- To modify priorities, you update the :data:`~local.system.replset.members` -array in the the replica configuration object. The array index begins with +array in the replica configuration object. The array index begins with ``0``. Do **not** confuse this index value with the value of the replica set member's :data:`~local.system.replset.members[n]._id` field in the array. diff --git a/source/tutorial/manage-mongodb-processes.txt b/source/tutorial/manage-mongodb-processes.txt index 4639c80592f..7f319312c3c 100644 --- a/source/tutorial/manage-mongodb-processes.txt +++ b/source/tutorial/manage-mongodb-processes.txt @@ -113,7 +113,7 @@ operations, flushes all data to data files, and closes all data files. Other shutdowns are *unclean* and can compromise the validity the data files. -.. COMMENT add the following to the last sentence when the pargarph +.. COMMENT add the following to the last sentence when the paragraph when maintain-valid-data-files is published. and may lead to corruption. See