diff --git a/source/includes/apiargs-method-db.createCollection-options-param.yaml b/source/includes/apiargs-method-db.createCollection-options-param.yaml
index 9dd6143f543..6f4dc2c7f2e 100644
--- a/source/includes/apiargs-method-db.createCollection-options-param.yaml
+++ b/source/includes/apiargs-method-db.createCollection-options-param.yaml
@@ -80,7 +80,7 @@ description: |2
      ``noPadding`` flag disables the :ref:`power of 2 sizes allocation
      <power-of-2-allocation>` for the collection. With ``noPadding``
      flag set to true, the allocation strategy does not include
-     additional space to accomodate document growth, as such, document
+     additional space to accommodate document growth, as such, document
      growth will result in new allocation. Use for collections with
      workloads that are insert-only or in-place updates (such as
      incrementing counters).
diff --git a/source/includes/fact-wiredtiger-cachesizegb.rst b/source/includes/fact-wiredtiger-cachesizegb.rst
index 3a8fd883352..df0d0aa5587 100644
--- a/source/includes/fact-wiredtiger-cachesizegb.rst
+++ b/source/includes/fact-wiredtiger-cachesizegb.rst
@@ -1,7 +1,7 @@
 The default :setting:`storage.wiredTiger.engineConfig.cacheSizeGB` setting
 assumes that there is a single :program:`mongod` instance per node. If a single
 node contains multiple instances, then you should adjust the
-:setting:`storage.wiredTiger.engineConfig.cacheSizeGB` setting to accomodate the
+:setting:`storage.wiredTiger.engineConfig.cacheSizeGB` setting to accommodate the
 working set as well as the other :program:`mongod` instances.
 
 If you run :program:`mongod` in a container (e.g. ``lxc``, ``cgroups``,
diff --git a/source/includes/steps-backup-sharded-cluster-with-snapshots.yaml b/source/includes/steps-backup-sharded-cluster-with-snapshots.yaml
index 169364c07c8..9deac91c7b7 100644
--- a/source/includes/steps-backup-sharded-cluster-with-snapshots.yaml
+++ b/source/includes/steps-backup-sharded-cluster-with-snapshots.yaml
@@ -26,7 +26,7 @@ content: |
   If your :program:`mongod` has journaling enabled and your journal
   and data files are on the same volume, you may skip this step.
 
-  If you need to lock the :program:`monogd`, attempt to lock one
+  If you need to lock the :program:`mongod`, attempt to lock one
   secondary member of each replica set in each shard so that your
   backups reflect the state of your database at the nearest possible
   approximation of a single moment in time.
diff --git a/source/includes/steps-backup-sharded-clusters-dumps.yaml b/source/includes/steps-backup-sharded-clusters-dumps.yaml
index c55b9a1b59f..17dec4c09ea 100644
--- a/source/includes/steps-backup-sharded-clusters-dumps.yaml
+++ b/source/includes/steps-backup-sharded-clusters-dumps.yaml
@@ -73,7 +73,7 @@ stepnum: 5
 ref: restart-replica-set-members
 pre: |
    Use :method:`db.fsyncUnlock()` to unlock the locked replica set
-   members of each shard. Allow these mebers to catch up with the state
+   members of each shard. Allow these members to catch up with the state
    of the primary.
 ---
 title: Re-enable the balancer process.
diff --git a/source/reference/command/serverStatus.txt b/source/reference/command/serverStatus.txt
index dbba100171a..824e07795bc 100644
--- a/source/reference/command/serverStatus.txt
+++ b/source/reference/command/serverStatus.txt
@@ -1609,7 +1609,7 @@ section <server-status-example-wiredTiger>` of the
    .. versionadded:: 3.0.0
 
    :data:`serverStatus.wiredTiger.async` returns statistics related to
-   the ascynchronous operations API. This is unused by MongoDB.
+   the asynchronous operations API. This is unused by MongoDB.
 
 .. data:: serverStatus.wiredTiger.block-manager