DOCS-16823 fixed inital typo (#385)

Author: kyuan-mongodb

source/includes/api/list-tables/backup-config/request-body-onprem.rst

@@ -23,7 +23,7 @@
        configuration. You must include the **syncSource** parameter
        when enabling encryption for a backup configuration. For
        existing backups in a project, enabling encryption requires an
-       :opsmgr:`inital sync </reference/glossary/#std-term-initial-sync>` to recreate the backups’ head databases.
+       :opsmgr:`initial sync </reference/glossary/#std-term-initial-sync>` to recreate the backups’ head databases.
 
        .. include:: /includes/head-database-deprecated-encrypt.rst
 

source/includes/api/list-tables/backup-config/response-body-onprem.rst

@@ -24,7 +24,7 @@
        configuration. You must include the **syncSource** field when
        enabling encryption for a backup configuration. For existing
        backups in a project, enabling encryption requires an 
-       :opsmgr:`inital sync </reference/glossary/#std-term-initial-sync>` to recreate the backups’ head databases.
+       :opsmgr:`initial sync </reference/glossary/#std-term-initial-sync>` to recreate the backups’ head databases.
 
        .. include:: /includes/head-database-deprecated-encrypt.rst
 

source/includes/backup/legacy-process-initial-backup.rst

@@ -3,7 +3,7 @@
 #. The Backup-enabled {+mdbagent+} connects to, and authenticates with,
    the databases associated with the backup job.
 
-#. The :opsmgr:`inital sync </reference/glossary/#std-term-initial-sync>` begins and enters its ``starting`` phase.
+#. The :opsmgr:`initial sync </reference/glossary/#std-term-initial-sync>` begins and enters its ``starting`` phase.
    Initial sync is a transition state between :guilabel:`Inactive` and
    :guilabel:`Active`. Initial Sync goes through a series of phases
    that are displayed on the :guilabel:`Backup` page to show progress.

source/includes/backup/legacy-process-overview-main-om.rst

@@ -3,7 +3,7 @@ This process works like
 
 The backup process:
 
-1. Performs an :opsmgr:`inital sync </reference/glossary/#std-term-initial-sync>` to back up all of your existing
+1. Performs an :opsmgr:`initial sync </reference/glossary/#std-term-initial-sync>` to back up all of your existing
    data in its current state.
    In :manual:`sharded clusters </reference/glossary/#std-term-sharded-cluster>`, this occurs on each
    shard and on the config servers.

source/includes/backup/legacy-process-overview.rst

@@ -3,7 +3,7 @@ This process works like
 
 The backup process:
 
-1. Performs an :opsmgr:`inital sync </reference/glossary/#std-term-initial-sync>` to back up all of your existing
+1. Performs an :opsmgr:`initial sync </reference/glossary/#std-term-initial-sync>` to back up all of your existing
    data in its current state.
    In :manual:`sharded clusters </reference/glossary/#std-term-sharded-cluster>`, this occurs on each
    shard and on the config servers.

source/includes/considerations-edit-deployment.rst

@@ -34,7 +34,7 @@ Storage Engine
 If you run or upgrade to MongoDB 3.0 or later and modify the MongoDB
 storage engine, |mms| shuts down and restarts the MongoDB process. For
 a multi-member replica set, |mms| performs a rolling
-:opsmgr:`inital sync </reference/glossary/#std-term-initial-sync>` of each member.
+:opsmgr:`initial sync </reference/glossary/#std-term-initial-sync>` of each member.
 
 |mms| creates backup directories during the migration from one storage
 engine to the other if the host has adequate disk space. If disk space

source/includes/extracts-alerts.yaml

@@ -96,7 +96,7 @@ content: |
 
      * - Sync slice transfer has not progressed in...
 
-       - An :opsmgr:`inital sync </reference/glossary/#std-term-initial-sync>` has started but then subsequently
+       - An :opsmgr:`initial sync </reference/glossary/#std-term-initial-sync>` has started but then subsequently
          stalled. Issues that can cause this, include, but are not
          limited to:
 

source/includes/steps-restore-primary.yaml

@@ -123,7 +123,7 @@ action:
       This script recreates the oplog :term:`collection` and seeds it with the
       timestamp of the snapshot's creation. This tells the secondary to
       recreate all operations to the current time without requiring a full
-      :opsmgr:`inital sync </reference/glossary/#std-term-initial-sync>`. |mms| customizes this script for this particular
+      :opsmgr:`initial sync </reference/glossary/#std-term-initial-sync>`. |mms| customizes this script for this particular
       snapshot and includes it in the snapshot archive.
 
       To run the script, issue the following command, where:

source/reference/api/backup/get-all-backup-configs-for-group.txt

@@ -103,7 +103,7 @@ Response
        backup configuration. You must include the ``syncSource`` 
        field when enabling encryption for a backup configuration. 
        For existing backups in a project, enabling encryption 
-       requires an :opsmgr:`inital sync </reference/glossary/#std-term-initial-sync>` to recreate the backups’ 
+       requires an :opsmgr:`initial sync </reference/glossary/#std-term-initial-sync>` to recreate the backups’ 
        head databases.
 
        .. include:: /includes/head-database-deprecated-encrypt.rst

source/reference/api/backup/get-one-backup-config-by-cluster-id.txt

@@ -88,7 +88,7 @@ Response
        backup configuration. You must include the ``syncSource`` 
        field when enabling encryption for a backup configuration. 
        For existing backups in a project, enabling encryption 
-       requires an :opsmgr:`inital sync </reference/glossary/#std-term-initial-sync>` to recreate the backups’ 
+       requires an :opsmgr:`initial sync </reference/glossary/#std-term-initial-sync>` to recreate the backups’ 
        head databases.
 
        .. include:: /includes/head-database-deprecated-encrypt.rst