Backports #15 (#17)

Backports #15

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

Author: sarahsimpers

snooty.toml

@@ -2,7 +2,6 @@ name = "ops-manager"
 title = "MongoDB Ops Manager"
 
 intersphinx = [ "https://docs.mongodb.com/manual/objects.inv",
-                "https://www.mongodb.com/docs/ops-manager/current/objects.inv", 
                 "https://www.mongodb.com/docs/drivers/objects.inv",
                 "https://www.mongodb.com/docs/database-tools/objects.inv",
                 "https://www.mongodb.com/docs/mongocli/stable/objects.inv",

source/admin/admin-tab-backup.txt

@@ -15,7 +15,7 @@ Administration Console : Backup Tab
 
 The :guilabel:`Admin` interface's :guilabel:`Backup` tab provides
 information on Backup resources, including :term:`jobs <backup job>`,
-:opsmgr:`daemons </reference/glossary/#term-Backup-Daemon>`, and :opsmgr:`blockstores </reference/glossary/#term-backup-blockstore-database>`.
+:opsmgr:`daemons </reference/glossary/#term-Backup-Daemon>`, and :opsmgr:`blockstores </reference/glossary/#std-term-backup-blockstore-database>`.
 For an overview of Backup and Backup resources, see
 :doc:`/core/backup-overview`.
 

source/admin/backup/daemons-page.txt

@@ -12,7 +12,7 @@ Daemons
    :depth: 2
    :class: singlecol
 
-This page lists all active :opsmgr:`Backup Daemons </reference/glossary/#term-Backup-Daemon>` and
+This page lists all active :opsmgr:`Backup Daemons </reference/glossary/#std-term-Backup-Daemon>` and
 provides configuration options. |onprem| automatically detects Backup
 Daemons and displays them here. You can reconfigure daemons from this
 page. Changes can take up to 5 minutes to take effect.
@@ -24,7 +24,7 @@ you want to add a daemon but do not want it to take new jobs. Type the
 new Backup Daemon.
 
 For each daemon, the page lists the server name, configuration,
-:opsmgr:`head </reference/glossary/#term-head-database>` space used, head space free, the number of
+:opsmgr:`head </reference/glossary/#std-term-head-database>` space used, head space free, the number of
 replica sets backed up, the percentage of time the Backup Daemon
 Service was busy, and job runtime counts by 1 minute, 10 minutes,
 60 minutes, less than or equal to 180 minutes, and greater than 180
@@ -69,7 +69,7 @@ configure daemons:
        Clear this when performing maintenance on a daemon's host.
 
    * - Queryable Restore Jobs
-     - Select this to allow the daemon to process :term:`queryable backups <queryable backup>`.
+     - Select this to allow the daemon to process :opsmgr:`queryable backups </reference/glossary/#std-term-queryable-backup>`.
 
        .. note::
 

source/admin/backup/grooms-page.txt

@@ -15,8 +15,8 @@ Grooms
 This page lists active and recent :term:`groom` jobs.
 
 Groom jobs remove unused :term:`blocks <block>` in
-:opsmgr:`blockstores </reference/glossary/#term-backup-blockstore-database>` and
-:opsmgr:`S3 blockstores  </reference/glossary/#term-S3-Snapshot-Store>` to reclaim storage
+:opsmgr:`blockstores </reference/glossary/#std-term-backup-blockstore-database>` and
+:opsmgr:`S3 blockstores  </reference/glossary/#std-term-S3-Snapshot-Store>` to reclaim storage
 space.
 
 If no existing :manual:`snapshots </reference/glossary/#std-term-snapshot>` reference a given

source/admin/backup/job-timeline-page.txt

@@ -15,8 +15,8 @@ Job Timeline
 This page displays a graphical representation of information found on
 other :guilabel:`Admin` pages, in particular the :guilabel:`Jobs`
 page. The :guilabel:`Job Timeline` page displays critical timestamps
-(:opsmgr:`head </reference/glossary/#term-head-database>`, last snapshot, next snapshot) and
-offers a way to assign a :opsmgr:`daemon </reference/glossary/#term-Backup-Daemon>` to a given job.
+(:opsmgr:`head </reference/glossary/#std-term-head-database>`, last snapshot, next snapshot) and
+offers a way to assign a :opsmgr:`daemon </reference/glossary/#std-term-Backup-Daemon>` to a given job.
 
 .. include:: /includes/head-database-backup-deprecated.rst
 

source/admin/backup/jobs-page.txt

@@ -46,8 +46,8 @@ From the :guilabel:`Jobs` page, you can do the following:
      - Procedure
 
    * - Assign a project to particular set of
-       :opsmgr:`Backup Daemons </reference/glossary/#term-Backup-Daemon>` or
-       :opsmgr:`blockstores </reference/glossary/#term-backup-blockstore-database>`.
+       :opsmgr:`Backup Daemons </reference/glossary/#std-term-Backup-Daemon>` or
+       :opsmgr:`blockstores </reference/glossary/#std-term-backup-blockstore-database>`.
 
      - Click the project, select the Daemons or :term:`blockstores
        <blockstore>`, and select :guilabel:`Save Changes`.
@@ -67,7 +67,7 @@ From the :guilabel:`Jobs` page, you can do the following:
 
      - Click the job. On the job's page, click the
        :guilabel:`Move head` link, select the new
-       :opsmgr:`head </reference/glossary/#term-head-database>`, and click the
+       :opsmgr:`head </reference/glossary/#std-term-head-database>`, and click the
        :guilabel:`Move Head` button.
 
        .. include:: /includes/head-database-backup-deprecated.rst
@@ -78,7 +78,7 @@ From the :guilabel:`Jobs` page, you can do the following:
      - Click the name of the Daemon or blockstore.
 
    * - Toggle whether a job :term:`journals <journal>` its
-       :opsmgr:`head database </reference/glossary/#term-head-database>`.
+       :opsmgr:`head database </reference/glossary/#std-term-head-database>`.
 
      - Select or clear :guilabel:`Journal Head` to turn on or off
        journaling for your head database.
@@ -96,7 +96,7 @@ Manage Backup Resources
 -----------------------
 
 From the :guilabel:`Jobs` page, you can assign Backup resources to a
-particular :opsmgr:`project </reference/glossary/#term-project>`.
+particular :opsmgr:`project </reference/glossary/#std-term-project>`.
 
 You can make these changes for existing Backups, but only new
 :term:`backup jobs <backup job>` will follow the new rules. Making
@@ -111,9 +111,9 @@ procedural information, see
    * - Task
      - Procedure
 
-   * - Assign a project to particular :opsmgr:`Daemons </reference/glossary/#term-Backup-Daemon>`,
-       :opsmgr:`blockstores </reference/glossary/#term-backup-blockstore-database>`
-       or :opsmgr:`oplog stores  </reference/glossary/#term-Oplog-Store-Database>`.
+   * - Assign a project to particular :opsmgr:`Daemons </reference/glossary/#std-term-Backup-Daemon>`,
+       :opsmgr:`blockstores </reference/glossary/#std-term-backup-blockstore-database>`
+       or :opsmgr:`oplog stores  </reference/glossary/#std-term-Oplog-Store-Database>`.
 
      - Click the project to open the project's assignment page; make the
        assignments; select :guilabel:`Save Changes`.
@@ -151,12 +151,12 @@ procedural information, see
           After you change the labels applied to this backup job,
           :ref:`stop then restart backups <restart-backup>` for this
           deployment. Once Backup restarts, |onprem| changes the
-          :opsmgr:`oplog store  </reference/glossary/#term-Oplog-Store-Database>` assigned to this
+          :opsmgr:`oplog store  </reference/glossary/#std-term-Oplog-Store-Database>` assigned to this
           Backup job. The oplog store matches the job's assigned
           labels to an oplog store with the same
           :ref:`assigned labels <edit-oplogstore>`. This change halts
           new and removes existing
-          :opsmgr:`point-in-time restores </reference/glossary/#term-point-in-time-restore>` until
+          :opsmgr:`point-in-time restores </reference/glossary/#std-term-point-in-time-restore>` until
           |onprem| takes the next snapshot after reassigning the oplog
           store.
 

source/admin/backup/resource-usage-page.txt

@@ -27,7 +27,7 @@ basis for all projects for which you enabled backup.
      - Content
 
    * - HEAD Usage
-     - Displays the following statistics for the :opsmgr:`head database </reference/glossary/#term-head-database>`
+     - Displays the following statistics for the :opsmgr:`head database </reference/glossary/#std-term-head-database>`
        of any backup job with |fcv-link| 4.0 or earlier:
 
        - :dbcommand:`Data Size <dbStats>`

source/admin/backup/snapshot-storage-page.txt

@@ -19,7 +19,7 @@ stores and allows you to create or modify snapshot stores.
 |mms| supports the following snapshot stores:
 
 - On a File System,
-- In a MongoDB database (:opsmgr:`blockstore </reference/glossary/#term-backup-blockstore-database>`), or
+- In a MongoDB database (:opsmgr:`blockstore </reference/glossary/#std-term-backup-blockstore-database>`), or
 - In an S3 Bucket (S3 blockstore)
 
 .. list-table::

source/admin/general/projects-page.txt

@@ -15,7 +15,7 @@ Projects
    :class: singlecol
 
 The :guilabel:`Projects` page in the :guilabel:`Admin` interface lists
-:opsmgr:`projects </reference/glossary/#term-project>`, their creation dates, and their last pings
+:opsmgr:`projects </reference/glossary/#std-term-project>`, their creation dates, and their last pings
 from agents.
 
 View a Project's Details
@@ -48,7 +48,7 @@ Edit a Project's Backup Configuration
 -------------------------------------
 
 From the :guilabel:`Jobs` page, you can assign Backup resources to a
-particular :opsmgr:`project </reference/glossary/#term-project>`. To learn more, see 
+particular :opsmgr:`project </reference/glossary/#std-term-project>`. To learn more, see 
 :ref:`admin-manage-backup-resources`.
 
 1. Click :guilabel:`Admin`, :guilabel:`General`, and 

source/application.txt

@@ -106,7 +106,7 @@ one version earlier. For MongoDB 4.2, the FCV can be ``4.0`` or
 
       The {+mdbagent+} then tails each replica set's :manual:`oplog </reference/glossary/#std-term-oplog>`
       to maintain on disk a standalone database, called a
-      :opsmgr:`head database </reference/glossary/#term-head-database>`. |mms| maintains one
+      :opsmgr:`head database </reference/glossary/#std-term-head-database>`. |mms| maintains one
       head database for each backed-up replica set. The head
       database stays consistent with the original :manual:`primary </reference/glossary/#std-term-primary>` up
       to the last oplog that the {+mdbagent+} supplies.