fix typos caught by spell checker

source/administration.txt

@@ -21,7 +21,7 @@ MongoDB.
 .. admin-introduction-end
 
 .. seealso:: The MongoDB Manual contains administrative documentation
-   and tutorials thoughout several sections. See
+   and tutorials throughout several sections. See
    :doc:`/administration/replica-sets` and
    :doc:`/sharding` for additional tutorials and
    information.

source/core/index-case-insensitive.txt

@@ -53,7 +53,7 @@ benefits of indexes.
 To use an index that specifies a collation, query and sort operations
 must specify the same collation as the index. If a collection has
 defined a collation, all queries and indexes inherit that collation
-unless they explictly specify a different collation.
+unless they explicitly specify a different collation.
 
 Examples
 --------

source/core/read-isolation-consistency-recency.txt

@@ -183,7 +183,7 @@ These guarantees hold across all members of the MongoDB deployment.
       outside the session. If a concurrent write operation interleaves
       between the session's write and read operations, the session's
       read operation may return results that reflect a write operation
-      that occured *after* the session's write operation.
+      that occurred *after* the session's write operation.
 
 Operations can be causally consistent across different sessions.
    MongoDB drivers and the :program:`mongo` shell provide the methods

source/core/replica-set-elections.txt

@@ -107,7 +107,7 @@ Vetoes in Elections
 .. versionchanged:: 3.2
 
    The :rsconf:`protocolVersion: 1 <protocolVersion>` obviates the need
-   for vetos. The following veto discussion applies to replica sets
+   for vetoes. The following veto discussion applies to replica sets
    that use the older :rsconf:`protocolVersion: 0 <protocolVersion>`.
 
 For replica sets using :rsconf:`protocolVersion: 0 <protocolVersion>`,

source/includes/extracts-collation.yaml

@@ -16,10 +16,10 @@ content: |
    If you specify a collation at the collection level:
 
    - Indexes on that collection will be created with that collation unless
-     the index creation operation explictly specify a different collation.
+     the index creation operation explicitly specify a different collation.
 
    - Operations on that collection use the collection's default
-     collation unless they explictly specify a different collation.
+     collation unless they explicitly specify a different collation.
 
      .. include:: /includes/extracts/collation-single-per-operation.rst
 ---

source/includes/fact-arbiter-priority.rst

@@ -1,4 +1,4 @@
 Starting in MongoDB 3.6, arbiters have priority ``0``. When you upgrade
-a replica set to MongoDB 3.6, if the exisiting configuration has an
+a replica set to MongoDB 3.6, if the existing configuration has an
 arbiter with priority ``1``, MongoDB 3.6 reconfigures the arbiter to
 have priority ``0``.

source/includes/limits-sharding-existing-collection-data-size.rst

@@ -23,7 +23,7 @@ collection size.
    megabyte.
 
 If ``maxCollectionSize`` is less than or nearly equal to the target
-collection, increase the chunk size to ensure sucessful initial sharding.
+collection, increase the chunk size to ensure successful initial sharding.
 If there is doubt as to whether the result of the calculation is too
 'close' to the target collection size, it is likely better to increase the
 chunk size.

source/reference/command/balancerStatus.txt

@@ -76,7 +76,7 @@ The following is an example of a document returned by the command:
 
    * - ``"numBalancerRounds"``
 
-     - The number of balancer rounds which have occured since the
+     - The number of balancer rounds which have occurred since the
        config servers were started. This value is not persisted and is
        reset to 0 upon restart of the config servers.
 

source/reference/command/buildInfo.txt

@@ -89,7 +89,7 @@ These fields are stable and should provide consistent behavior.
 
    .. versionadded:: 3.2
 
-   A list of :doc:`storage engines </faq/storage>` avilable to the
+   A list of :doc:`storage engines </faq/storage>` available to the
    :program:`mongod` server.
 
 .. data:: buildInfo.javascriptEngine

source/reference/command/create.txt

@@ -82,7 +82,7 @@ the following privilege to run the :dbcommand:`create` command:
 
    * - Create a capped collection
 
-     - :authaction:`convertToCapped` for the colleciton
+     - :authaction:`convertToCapped` for the collection
 
 
        :authaction:`createCollection` in the database

source/reference/command/serverStatus.txt

@@ -1814,7 +1814,7 @@ metrics
 
 .. serverstatus:: metrics.operation.writeConflicts
 
-   The total number of queries that encounted write conflicts.
+   The total number of queries that encountered write conflicts.
 
 .. serverstatus:: metrics.queryExecutor
 

source/reference/operator/query/jsonSchema.txt

@@ -66,7 +66,7 @@ for the :query:`$type` operator.
 Omissions
 ---------
 
-The following will not be supported in MongoDB's implemenation of JSON Schema:
+The following will not be supported in MongoDB's implementation of JSON Schema:
 
 - `Hypertext definitions <https://tools.ietf.org/html/draft-luff-json-hyper-schema-00>`_ 
   in draft 4 of the JSON Schema spec.

source/reference/program/mongoexport.txt

@@ -41,7 +41,7 @@ Required Access
 
 :program:`mongoexport` requires read access on the target database.
 
-Ensure that the connecting user posseses, at a minimum, the :authrole:`read`
+Ensure that the connecting user possesses, at a minimum, the :authrole:`read`
 role on the target database.
 
 When connecting to a :program:`mongod` or :program:`mongos` that enforces

source/release-notes/3.6-downgrade-replica-set.txt

@@ -68,7 +68,7 @@ Procedure
 
 .. warning::
 
-   Before proceding with the downgrade procedure, ensure that all
+   Before proceeding with the downgrade procedure, ensure that all
    replica set members, including delayed replica set members, reflect
    the prerequisite changes. That is, check the
    ``featureCompatibilityVersion`` and the removal of incompatible

source/release-notes/3.6-downgrade-sharded-cluster.txt

@@ -88,7 +88,7 @@ Downgrade a Sharded Cluster
 
 .. warning::
 
-   Before proceding with the downgrade procedure, ensure that all
+   Before proceeding with the downgrade procedure, ensure that all
    members, including delayed replica set members in the sharded
    cluster, reflect the prerequisite changes.  That is, check the
    ``featureCompatibilityVersion`` and the removal of incompatible

source/tutorial/deploy-sharded-cluster-hashed-sharding.txt

@@ -71,7 +71,7 @@ tutorial on deploying a sharded cluster with a
 
 In production environments, sharded clusters should employ at
 minimum :doc:`/core/security-x.509` security for internal authentication
-and client acces:
+and client access:
 
 - For details on using x.509 for internal authentication, see
   :doc:`/tutorial/configure-x509-member-authentication`.

source/tutorial/deploy-sharded-cluster-with-keyfile-access-control.txt

@@ -37,7 +37,7 @@ CloudManager and OpsManager
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you are using Cloud Manager or Ops Manager to manage your deployment,
-see the repective :mms-docs:`Cloud Manager manual
+see the respective :mms-docs:`Cloud Manager manual
 </tutorial/edit-host-authentication-credentials>`
 or the :opsmgr:`Ops Manager manual
 </tutorial/edit-host-authentication-credentials>` to enforce authentication.

source/tutorial/enforce-keyfile-access-control-in-existing-replica-set-without-downtime.txt

@@ -39,7 +39,7 @@ Cloud Manager and Ops Manager
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you are using Cloud Manager or Ops Manager to manage your deployment,
-see the repective :mms-docs:`Cloud Manager manual
+see the respective :mms-docs:`Cloud Manager manual
 </tutorial/edit-host-authentication-credentials>`
 or the :opsmgr:`Ops Manager manual
 </tutorial/edit-host-authentication-credentials>` to enforce authentication.