Copy edit run

source/administration/production-notes.txt

@@ -444,7 +444,7 @@ Additional Deployment Considerations
 - Check :doc:`ulimits </administration/ulimit/>` settings.
 
 - Use SSD if available and economical. Spinning disks can work well
-  but SSDs capcity for random I/O operations work well with the update
+  but SSDs capacity for random I/O operations work well with the update
   model of :program:`mongod`. See :ref:`production-nfs` for more info.
 
 - Ensure that clients keep reasonable pool sizes to avoid overloading

source/administration/sharded-clusters.txt

@@ -338,7 +338,7 @@ privileges:
 
   - Normal administrative privileges, which provide read-and-write
     access to the admin database and access to all administrative
-    commands, and which provide read-and-write accees to all other
+    commands, and which provide read-and-write access to all other
     databases on that shard.
 
   - Read-only administrative privileges, which provide read-only access

source/administration/snmp.txt

@@ -202,7 +202,7 @@ You may also choose to specify a the path to the MIB file:
 
 .. code-block:: sh
 
-   nmpwalk -m /usr/share/snmp/mibs/MONGO-MIB -v 2c -c mongodb 127.0.0.1:1161 1.3.6.1.4.1.37601
+   snmpwalk -m /usr/share/snmp/mibs/MONGO-MIB -v 2c -c mongodb 127.0.0.1:1161 1.3.6.1.4.1.37601
 
 Use this command *only* to ensure that you can retrieve and validate
 SNMP data from MongoDB.

source/core/sharded-clusters.txt

@@ -62,7 +62,7 @@ The ideal shard key:
 - is easily divisible which makes it easy for MongoDB to distribute
   content among the shards. Shard keys that have a limited number of
   possible values are not ideal as they can result in some chunks that
-  are "unsplittable." See the :ref:`sharding-shard-key-cardinality`
+  are "unsplitable." See the :ref:`sharding-shard-key-cardinality`
   section for more information.
 
 - will distribute write operations among the cluster, to prevent any

source/reference/command/captrunc.txt

@@ -30,7 +30,7 @@ captrunc (internal)
 
          db.runCommand({captrunc: "records", n:100, inc:true})
 
-   .. |dbcommand| replace:: :dbcommand:`captruc`
+   .. |dbcommand| replace:: :dbcommand:`captrunc`
    .. include:: /includes/note-enabletestcommands.rst
 
    .. write-lock

source/reference/configuration-options.txt

@@ -621,7 +621,7 @@ Settings
    mode that attempts to limit the amount of output. This option suppresses:
 
    - output from :term:`database commands <database command>`,
-     including :dbcommand:`drop`, :dbcommand:`dropIndexs`,
+     including :dbcommand:`drop`, :dbcommand:`dropIndexes`,
      :dbcommand:`diagLogging`, :dbcommand:`validate`, and
      :dbcommand:`clean`.
 

source/reference/mongoperf.txt

@@ -54,7 +54,7 @@ Options
 
    .. code-block:: sh
 
-      mongperf < config
+      mongoperf < config
 
    In this example ``config`` is the name of a file that holds a JSON
    document that resembles the following example:

source/reference/mongorestore.txt

@@ -159,7 +159,7 @@ Options
 
 .. option:: --objcheck
 
-   Forces the :program:`mongodrestore` to validate all requests from
+   Forces the :program:`mongorestore` to validate all requests from
    clients upon receipt to ensure that clients never insert invalid
    documents into the database. For objects with a high degree of
    sub-document nesting, :option:`--objcheck` can have a small impact

source/use-cases/storing-comments.txt

@@ -577,7 +577,7 @@ logic to support this:
 
 This :py:meth:`update() <pymongo:pymongo.collection.Collection.update>` operation
 includes the last known number of pages in the query to prevent a race
-condition where the number of pages incriments twice, that would
+condition where the number of pages increments twice, that would
 result in a nearly or totally empty document. If another
 process increments the number of pages, then update above does
 nothing.