Backports DOCSP-37037 to v6.0 (#112)

Backports #110 

[Build](https://workerpool-boxgs.mongodbstitch.com/pages/job.html?collName=queue&jobId=65d64ac77111165982e9f911)

Author: sarahsimpers

source/core/backup-preparations.txt

@@ -480,7 +480,7 @@ You may also want to resync your backup if you:
 - :manual:`Drop a collection </reference/method/db.collection.drop>`
   (MMAPv1 only).
 
-- Run a :manual:`sharded cluster </reference/glossary/#std-term-sharded-cluster>``, and move chunks
+- Run a :manual:`sharded cluster </reference/glossary/#std-term-sharded-cluster>`, and move chunks
   from a particular shard.
 
 - Switch storage engines, if you want |mms| to provide snapshots

source/core/system-alerts.txt

@@ -208,8 +208,7 @@ Blockstore
 
    * - ``OUTSIDE_SPACE_USED_THRESHOLD``
      - .. alert:: Blockstore space used exceeds threshold
-     - Sent when the disk space the :opsmgr:`blockstore <term-Backup Blockstore
-       Database>` uses exceeds the configured :setting:`threshold
+     - Sent when the disk space the :opsmgr:`blockstore </reference/glossary/#std-term-backup-blockstore-database>` uses exceeds the configured :setting:`threshold
        <mms.alerts.OutsideSpaceUsedThreshold.maximumSpaceUsedPercent>`
        setting. The default threshold is 85% of the total disk capacity
        on which the blockstore is stored. You can change the

source/includes/api/list-tables/restore-job-request-documents.rst

@@ -165,7 +165,7 @@
        hours of the current time.
 
        If you provide this setting, this endpoint restores all data up
-       to this :opsmgr:`Point in Time </reference/glossary/#std-term-point-in-time-restore>  to the
+       to this :opsmgr:`Point in Time </reference/glossary/#std-term-point-in-time-restore>`  to the
        database you specified in the ``delivery`` object.
 
        ``"delivery.methodName" : "AUTOMATED_RESTORE"``

source/includes/api/list-tables/restore-jobs/body-parameters/pit.rst

@@ -63,7 +63,7 @@
        hours of the current time.
 
        If you provide this setting, this endpoint restores all data up
-       to this :opsmgr:`Point in Time </reference/glossary/#std-term-point-in-time-restore>  to the
+       to this :opsmgr:`Point in Time </reference/glossary/#std-term-point-in-time-restore>` to the
        database you specified in the ``delivery`` object.
 
 

source/includes/steps-deploy-standalone.yaml

@@ -36,9 +36,7 @@ content: |
      * - :guilabel:`Auth Schema Version`
        - Select the schema for storing the user data for your
          deployment. MongoDB 3.0 uses a different schema for user data
-         than previous versions. For compatibility information, see the
-         :ref:`Security Changes <legacy-auth-model-removed>`
-         in the MongoDB 3.0 release notes.
+         than previous versions.
 
      * - :guilabel:`Feature Compatibility` (Optional)
        - Select the :manual:`feature compatibility set

source/includes/steps-edit-replica-set-configuration.yaml

@@ -25,9 +25,7 @@ content: |
        - Select the schema for storing the user data for your
          deployment. If you are upgrading from a MongoDB version older
          than 3.0, MongoDB 3.0 uses a different schema for user data
-         than previous versions. For compatibility information, see the
-         :ref:`Security Changes <legacy-auth-model-removed>`
-         in the MongoDB 3.0 release notes.
+         than previous versions.
 
      * - :guilabel:`Feature Compatibility` (Optional)
        - Select the :manual:`feature compatibility set

source/includes/upgrade-path-onprem-upgrade.rst

@@ -101,5 +101,5 @@ The following table lists upgrade paths for all versions:
 
    * - 2.x or earlier
      - Use the
-       `v3.4 upgrade tutorial <https://www.mongodb.com/docs/ops-manager/v3.4/tutorial/nav/upgrade-application/tutorial/nav/upgrade-application>`__
+       `v3.4 upgrade tutorial <https://www.mongodb.com/docs/ops-manager/v3.4/tutorial/nav/upgrade-application/>`__
        to upgrade from |onprem| 2.x or earlier.

source/reference/alerts/query-targeting.txt

@@ -72,7 +72,7 @@ query generated the alert:
   all queries.
 
 - The :manual:`Data Profiler 
-  </tutorial/manage-the-database-profiler/index.html>`
+  </tutorial/manage-the-database-profiler>`
   records operations that |service| considers slow when compared to
   average execution time for all operations on your cluster.
 

source/reference/api/admin/backup/groups/get-all-backup-group-configurations.txt

@@ -1,3 +1,5 @@
+.. _get-all-backup-group-configurations:
+
 ==========================================
 Get All Project Backup Jobs Configurations
 ==========================================

source/reference/api/admin/backup/groups/update-one-backup-group-configuration.txt

@@ -1,3 +1,5 @@
+.. _update-one-backup-group-configuration:
+
 ============================================
 Update One Project Backup Jobs Configuration
 ============================================

source/reference/glossary.txt

@@ -106,7 +106,7 @@ Glossary
 
 
    backup cursor
-      A :manual:`tailable cursor <tailable-cursors>` pointing to a list of
+      A :manual:`tailable cursor </core/tailable-cursors>` pointing to a list of
       backup files. Starting with FCV 4.2, |onprem| uses
       :manual:`backup cursors </reference/glossary/#std-term-backup-cursor>` instead of 
       :opsmgr:`head databases </reference/glossary/#std-term-head-database>`.

source/release-notes/changelogs/ops-manager/changelog-onprem-eol.rst

@@ -545,8 +545,7 @@ Considerations for Upgrade (v1.8)
   :ref:`backup-database` run MongoDB 2.6 or later.
   |onprem| will not start after upgrade if your backing databases are
   using an earlier version of MongoDB. The MongoDB Manual provides
-  upgrade tutorials with each release. To upgrade from MongoDB 2.4 to
-  2.6, see: :manual:`Upgrade MongoDB to 2.6 </release-notes/2.6-upgrade/>`.
+  upgrade tutorials with each release.
 
 - When you upgrade to |onprem| 1.8, |onprem| disables all Automation
   Agents until they are upgraded to :ref:`automation-2.0.9.1201`. You

source/release-notes/changelogs/ops-manager/changelog-onprem-v4.0.rst

@@ -464,10 +464,6 @@
     :abbr:`API (Application Programming Interface)` keys created
     before |onprem| 3.4.
 
-    The change to the Agent
-    :abbr:`API (Application Programming Interface)` Key model is
-    :v3.6:`described in the v3.6 documentation </tutorial/manage-agent-api-key>`.
-
 - Provided :doc:`new option </tutorial/configure-local-mode>` to only
   have |onprem| connect to the internet to download MongoDB installer
   binaries.

source/release-notes/changelogs/ops-manager/changelog-onprem-v4.2.rst

@@ -332,7 +332,7 @@ Upgrades Agent: :ref:`mongodb-10.2.16.5960`.
 
 - Bootstrapping a Backup
   :term:`initial sync <initial sync>` using
-  :manual:`rsync </core/backups/index.html#back-up-with-cp-or-rsync>` 
+  :manual:`rsync </core/backups/#back-up-with-cp-or-rsync>` 
   can now complete when syncing from a hidden secondary.
 - Logs are viewable in the |onprem| Admin panel.
 - Ensures initial sync can complete after FCV downgrades.

source/release-notes/changelogs/ops-manager/changelog-onprem-v4.4.rst

@@ -248,7 +248,7 @@
 - Fixes a bug that disallows configuring |ldap| group names longer
   than 100 characters.
 - Updates the {+mdbagent+} to :ref:`10.14.22.6489 <mongodb-10.14.22.6489>`.
-- Requires :dbtools:`MongoDB Database Tools 100.3.1 <//release-notes/database-tools-changelog#100.3.1-changelog>`.
+- Requires `MongoDB Database Tools 100.3.1 <https://www.mongodb.com/docs/database-tools/release-notes/database-tools-changelog#100.3.1-changelog>`__.
 - Changes the :ref:`protocolVersion <autoconfig-mongodb-replicasets>` 
   API parameter from an integer to a string. For example, previously, 
   you could specify  ``1`` for this parameter. Now, you must specify 

source/tutorial/configure-local-mode.txt

@@ -106,7 +106,7 @@ To use earlier versions, you must download them from
 Prerequisites
 -------------
 
-If you :doc:`configure an HTTP proxy <use-with-http-proxy>` for |onprem|,
+If you :ref:`configure an HTTP proxy <use-with-http-proxy>` for |onprem|,
 the Backup Daemon, and the MongoDB Agents:
 
 - Consider :ref:`adding sites from which to download the version

source/tutorial/convert-config-servers-to-replica-set.txt

@@ -16,7 +16,7 @@ Convert Config Servers to a Replica Set
    longer supported.
 
 In a sharded cluster, :manual:`config servers  </reference/glossary/#std-term-config-server>` store the
-metadata for the :manual:`sharded cluster </reference/glossary/#std-term-sharded-cluster>``. For a
+metadata for the :manual:`sharded cluster </reference/glossary/#std-term-sharded-cluster>`. For a
 sharded cluster to be fully operational, the config servers must be
 available and the metadata must be consistent across the config
 servers.

source/tutorial/create-cluster-with-api.txt

@@ -117,4 +117,4 @@ Next Steps
 ----------
 
 To make an additional version of MongoDB available in the cluster,
-see :doc:`update-mongodb-version-of-deployment-via-api`.
+see :ref:`update-mongodb-version-of-deployment-via-api`.

source/tutorial/edit-deployment.txt

@@ -15,7 +15,7 @@ Edit a Deployment's Configuration
 You can modify a deployment's configuration and topology, including its
 MongoDB versions, storage engines, and numbers of hosts or shards. You
 can make modifications at all levels of a deployment's topology from a
-top-level :manual:`sharded cluster </reference/glossary/#std-term-sharded-cluster>`` or
+top-level :manual:`sharded cluster </reference/glossary/#std-term-sharded-cluster>` or
 :manual:`replica set </reference/glossary/#std-term-replica-set>` to lower levels, such as a replica set within a
 sharded cluster, or an individual process within a replica set. You can
 also modify :term:`standalone <standalone>` processes.

source/tutorial/move-jobs-to-new-backup-daemon.txt

@@ -16,7 +16,7 @@ then an administrator with the :authrole:`Global Owner`
 or :ref:`global backup admin role <global-backup-admin-role>` :doc:`role </reference/user-roles>`
 can move all the daemon's jobs to another Backup Daemon. The new
 daemon takes over the responsibility to back up the associated
-:manual:`shards <shard>` and :manual:`replica sets </reference/glossary/#std-term-replica-set>`.
+:manual:`shards </sharding>` and :manual:`replica sets </reference/glossary/#std-term-replica-set>`.
 
 When you move jobs, the destination daemon reconstructs the data using
 a snapshot and the :manual:`oplog </reference/glossary/#std-term-oplog>` from the :ref:`backup-database`.
@@ -36,7 +36,7 @@ backups to the new Backup Daemon:
 - Restores of previous snapshots are still available.
 
 - |mms| can produce restore artifacts using existing snapshots with
-  :manual:`point-in-time restore` for :manual:`replica sets </reference/glossary/#std-term-replica-set>`
+  :term:`point-in-time restore` for :manual:`replica sets </reference/glossary/#std-term-replica-set>`
   or :manual:`sharded clusters </reference/glossary/#std-term-sharded-cluster>` that run |fcv-link| of
   4.2 or later. (:manual:`Sharded clusters </reference/glossary/#std-term-sharded-cluster>` that run
   |fcv| of 4.0 or earlier can use :ref:`checkpoints <checkpoint>`.)

source/tutorial/update-mongodb-version-of-deployment-via-api.txt

@@ -1,3 +1,5 @@
+.. _update-mongodb-version-of-deployment-via-api:
+
 ==========================================
 Update the MongoDB Version of a Deployment
 ==========================================

source/tutorial/use-with-http-proxy.txt

@@ -1,3 +1,5 @@
+.. _use-with-http-proxy:
+
 ============================================================
 Configure |onprem| to Use an HTTP Proxy for Outgoing Traffic
 ============================================================