diff --git a/source/includes/options-conf.yaml b/source/includes/options-conf.yaml
index 1ae0841d724..1a164b93180 100644
--- a/source/includes/options-conf.yaml
+++ b/source/includes/options-conf.yaml
@@ -185,7 +185,7 @@ description: |
   storage. See :data:`STORAGE` components.
 
   The :setting:`systemLog.component.storage.verbosity` level applies to
-  jounaling components as well *if*
+  journaling components as well *if*
   :setting:`systemLog.component.storage.journal.verbosity` is unset.
 
   .. include:: /includes/log-verbosity-levels.rst
diff --git a/source/includes/steps-2.8-upgrade-sharded-cluster.yaml b/source/includes/steps-2.8-upgrade-sharded-cluster.yaml
index fdfd6756638..972190f8202 100644
--- a/source/includes/steps-2.8-upgrade-sharded-cluster.yaml
+++ b/source/includes/steps-2.8-upgrade-sharded-cluster.yaml
@@ -80,7 +80,7 @@ content: |
 
   After you have successfully upgraded *all* :program:`mongos`
   instances, you can proceed to upgrade the other components in your
-  shareded cluster.
+  sharded cluster.
 
   .. include:: /includes/warning-upgrade-sharded-cluster-ordering.rst
 
diff --git a/source/reference/command/collMod.txt b/source/reference/command/collMod.txt
index b062b11cbbd..f9d3aa012e4 100644
--- a/source/reference/command/collMod.txt
+++ b/source/reference/command/collMod.txt
@@ -102,7 +102,9 @@ Powers of Two Record Allocation
 
    The :collflag:`usePowerOf2Sizes` flag changes the method that
    MongoDB uses to allocate space on disk for documents in this
-   collection. By setting :collflag:`usePowerOf2Sizes`, yousthat
+   collection. By setting :collflag:`usePowerOf2Sizes`,
+   you ensure
+   that MongoDB will allocate space for documents in sizes that
    are powers of 2 (e.g. 32, 64, 128, 256, 512...16777216.) The
    smallest allocation for a document is 32 bytes.
 
diff --git a/source/reference/command/serverStatus.txt b/source/reference/command/serverStatus.txt
index 5ceb0b06407..18fcbb667ff 100644
--- a/source/reference/command/serverStatus.txt
+++ b/source/reference/command/serverStatus.txt
@@ -1011,7 +1011,7 @@ section <server-status-example-opcounters>` of the
 .. data:: serverStatus.opcounters.update
 
    :data:`~serverStatus.opcounters.update` provides a counter of the total number
-   of update operations recieved since the :program:`mongod` instance last
+   of update operations received since the :program:`mongod` instance last
    started.
 
 .. data:: serverStatus.opcounters.delete
diff --git a/source/reference/explain-results.txt b/source/reference/explain-results.txt
index ac469dd23e0..bc077ffbf7e 100644
--- a/source/reference/explain-results.txt
+++ b/source/reference/explain-results.txt
@@ -354,7 +354,7 @@ MongoDB does not need to examine documents from the collection to
 return the results.
 
 When an index covers a query, the explain result has an ``IXSCAN``
-stage that is **not** a descendent of a ``FETCH`` stage, and in the
+stage that is **not** a descendant of a ``FETCH`` stage, and in the
 :ref:`executionStats`, the :data:`~explain.totalDocsExamined` is ``0``.
 
 In earlier versions of MongoDB, ``cursor.explain()`` returned the
diff --git a/source/tutorial/backup-with-mongodump.txt b/source/tutorial/backup-with-mongodump.txt
index 86655acef4c..e5371c3865e 100644
--- a/source/tutorial/backup-with-mongodump.txt
+++ b/source/tutorial/backup-with-mongodump.txt
@@ -131,7 +131,7 @@ The :program:`mongorestore` utility restores a binary backup created by
 :program:`mongodump`. By default, :program:`mongorestore` looks for a
 database backup in the :file:`dump/` directory.
 
-The :program:`mongorestore` utility restores data by connectiing to a
+The :program:`mongorestore` utility restores data by connecting to a
 running :program:`mongod` or :program:`mongos` directly.
 
 :program:`mongorestore` can restore either an entire database backup