Backports #449 to v8.0 (#451)

sarahsimpers · web-flow · commit 221f5c63665d · 2024-10-04T14:36:06.000-04:00
Some pages ported changes from CM to OM but missed OM-specific nested components. This PR fixes those Backports #449
diff --git a/source/includes/api/list-tables/events/query-params/get-one.rst b/source/includes/api/list-tables/events/query-params/get-one.rst
@@ -26,8 +26,5 @@ The following query parameters are optional:
       The ``raw`` document contains additional meta information about
       the event.
 
-      .. important::
-
-        The values in the ``raw`` document are subject to change. Do
-        not rely on ``raw`` values for formal monitoring.
+      :gold:`IMPORTANT:` The values in the ``raw`` document are subject to change. Do not rely on ``raw`` values for formal monitoring.
     - ``false``
diff --git a/source/includes/api/list-tables/events/responses/orgs-cloud.rst b/source/includes/api/list-tables/events/responses/orgs-cloud.rst
@@ -140,10 +140,7 @@
      - Additional meta information about the event. This field only
        appears when the ``includeRaw`` query parameter is ``true``.
 
-       .. important::
-
-          The values in the ``raw`` document are subject to change. Do
-          not rely on ``raw`` values for formal monitoring.
+       :gold:`IMPORTANT:` The values in the ``raw`` document are subject to change. Do not rely on ``raw`` values for formal monitoring.
 
    * - remoteAddress
      - string
diff --git a/source/includes/api/list-tables/events/responses/orgs-onprem.rst b/source/includes/api/list-tables/events/responses/orgs-onprem.rst
@@ -56,9 +56,7 @@
      - string
      - Relevant units for the value.
 
-       .. example::
-        
-          A metric that measures memory consumption would have a byte measurement, while a metric that measures time would have a time unit.
+       For example, a metric that measures memory consumption would have a byte measurement, while a metric that measures time would have a time unit.
 
        Accepted values are:
 
@@ -131,10 +129,7 @@
      - Additional meta information about the event. This field only
        appears when the ``includeRaw`` query parameter is ``true``.
 
-       .. important::
-
-          The values in the ``raw`` document are subject to change. Do
-          not rely on ``raw`` values for formal monitoring.
+       :gold:`IMPORTANT:` The values in the ``raw`` document are subject to change. Do not rely on ``raw`` values for formal monitoring.
 
    * - remoteAddress
      - string
diff --git a/source/includes/api/list-tables/events/responses/projects-cloud.rst b/source/includes/api/list-tables/events/responses/projects-cloud.rst
@@ -138,10 +138,7 @@
      - Additional meta information about the event. This field only
        appears when the ``includeRaw`` query parameter is ``true``.
 
-       .. important::
-
-          The values in the ``raw`` document are subject to change. Do
-          not rely on ``raw`` values for formal monitoring.
+       :gold:`IMPORTANT:` The values in the ``raw`` document are subject to change. Do not rely on ``raw`` values for formal monitoring.
 
    * - remoteAddress
      - string
diff --git a/source/includes/api/list-tables/events/responses/projects-onprem.rst b/source/includes/api/list-tables/events/responses/projects-onprem.rst
@@ -56,11 +56,8 @@
      - string
      - Relevant units for the value.
 
-       .. example::
-        
-          A metric that measures memory consumption would have a byte
-          measurement, while a metric that measures time would have a
-          time unit.
+       For example, a metric that measures memory consumption would
+       have a byte measurement, while a metric that measures time would have a time unit.
 
        Accepted values are:
 
@@ -76,12 +73,10 @@
      - array of objects
      - Changes made to the deployment during this event.
 
-       .. note::
-
-          |mms| returns different elements depending upon what was
-          changed: user privileges or roles, restore jobs, automation
-          modules, and so on. The list of this array and its objects is
-          not exhaustive.
+       |mms| returns different elements depending upon what was
+       changed: user privileges or roles, restore jobs, automation
+       modules, and so on. The list of this array and its objects is
+       not exhaustive.
 
    * - | diffs
        | .id
@@ -205,10 +200,7 @@
      - Additional meta information about the event. This field only
        appears when the ``includeRaw`` query parameter is ``true``.
 
-       .. important::
-
-          The values in the ``raw`` document are subject to change. Do
-          not rely on ``raw`` values for formal monitoring.
+       :gold:`IMPORTANT:` The values in the ``raw`` document are subject to change. Do not rely on ``raw`` values for formal monitoring.
 
    * - remoteAddress
      - string
diff --git a/source/includes/api/list-tables/restore-job-request-documents.rst b/source/includes/api/list-tables/restore-job-request-documents.rst
@@ -15,11 +15,11 @@
        that represents the point in time to which your data will be
        restored.
 
-       .. note:: Conditions
+       Conditions include:
 
-          - Set ``"delivery.methodName" : "AUTOMATED_RESTORE"``.
-          - Can't set ``oplogInc``, ``oplogTs``, or
-            ``pointInTimeUTCMillis``.
+       - Set ``"delivery.methodName" : "AUTOMATED_RESTORE"``.
+       - Can't set ``oplogInc``, ``oplogTs``, or
+         ``pointInTimeUTCMillis``.
 
        If you provide this setting, this endpoint restores all data up
        to this :opsmgr:`checkpoint  </reference/glossary/#std-term-checkpoint>` to the database you
diff --git a/source/includes/api/list-tables/restore-jobs/response-elements/onprem/http.rst b/source/includes/api/list-tables/restore-jobs/response-elements/onprem/http.rst
@@ -100,13 +100,13 @@
 
           "<authHeader>:<authBearer> <authValue>" <urlV2>
 
-       .. example:: 
+       For example:
 
-          .. code-block:: sh 
-             :copyable: false
+       .. code-block:: sh 
+          :copyable: false
 
-             curl -H "Authorization: Bearer {AUTH-TOKEN}" \
-                  https://{OPSMANAGER-HOST}:{PORT}/backup/restore/v3/pull/{restoreJobId}/{filename}"
+          curl -H "Authorization: Bearer {AUTH-TOKEN}" \
+              https://{OPSMANAGER-HOST}:{PORT}/backup/restore/v3/pull/{restoreJobId}/{filename}"
 
    * - ``groupId``
      - string
diff --git a/source/includes/api/list-tables/snapshot-schedule/requests-opsmgr.rst b/source/includes/api/list-tables/snapshot-schedule/requests-opsmgr.rst
@@ -28,10 +28,8 @@
      - Number of days to retain daily snapshots. You can set a value
        between ``1`` and ``365``, inclusive.
 
-       .. note::
-
-          Setting ``dailySnapshotRetentionDays`` to ``0`` disables this
-          rule.
+       Setting ``dailySnapshotRetentionDays`` to ``0`` disables this
+       rule.
 
    * - ``fullIncrementalDayOfWeek``
      - string
@@ -57,9 +55,7 @@
      - Number of months to retain monthly snapshots. You can set a
        value between ``1`` and ``36``, inclusive.
 
-       .. note::
-
-          Setting ``monthlySnapshotRetentionMonths`` to ``0`` disables this rule.
+       Setting ``monthlySnapshotRetentionMonths`` to ``0`` disables this rule.
 
    * - ``pointInTimeWindowHours``
      - number
@@ -91,12 +87,10 @@
        ``+0000`` before storing it, and adjusts the 
        ``referenceHourOfDay`` value accordingly.
 
-       .. example::
-
-          You pass in a request with a ``referenceHourOfDay`` of ``5``
-          and a ``referenceTimeZoneOffset`` of ``"+0200". |onprem|
-          stores a ``referenceHourOfDay`` of ``3`` and a 
-          ``referenceTimeZoneOffset`` of ``"+0000"``.
+       For example, you pass in a request with a ``referenceHourOfDay``
+       of ``5`` and a ``referenceTimeZoneOffset`` of ``"+0200". |onprem|
+       stores a ``referenceHourOfDay`` of ``3`` and a 
+       ``referenceTimeZoneOffset`` of ``"+0000"``.
 
    * - ``snapshotIntervalHours``
      - number
diff --git a/source/includes/api/list-tables/snapshot-schedule/responses-opsmgr.rst b/source/includes/api/list-tables/snapshot-schedule/responses-opsmgr.rst
@@ -24,10 +24,8 @@
      - Number of days to retain daily snapshots. |mms| may return
        values between ``1`` and ``365``, inclusive.
 
-       .. note::
-
-          Setting ``dailySnapshotRetentionDays`` to ``0`` disables this
-          rule.
+       Setting ``dailySnapshotRetentionDays`` to ``0`` disables this
+       rule.
 
    * - ``fullIncrementalDayOfWeek``
      - string
@@ -49,9 +47,7 @@
      - Number of months to retain monthly snapshots. |mms| may return
        values between ``1`` and ``36``, inclusive.
 
-       .. note::
-
-          Setting ``monthlySnapshotRetentionMonths`` to ``0`` disables this rule.
+       Setting ``monthlySnapshotRetentionMonths`` to ``0`` disables this rule.
 
    * - ``pointInTimeWindowHours``
      - number
@@ -79,12 +75,10 @@
        ``+0000`` before storing it, and adjusts the 
        ``referenceHourOfDay`` value accordingly.
 
-       .. example::
-
-          You pass in a request with a ``referenceHourOfDay`` of ``5``
-          and a ``referenceTimeZoneOffset`` of ``"+0200". |onprem|
-          stores a ``referenceHourOfDay`` of ``3`` and a 
-          ``referenceTimeZoneOffset`` of ``"+0000"``.
+       For example, you pass in a request with a ``referenceHourOfDay``
+       of ``5`` and a ``referenceTimeZoneOffset`` of ``"+0200". |onprem|
+       stores a ``referenceHourOfDay`` of ``3`` and a 
+       ``referenceTimeZoneOffset`` of ``"+0000"``.
 
    * - ``snapshotIntervalHours``
      - number
diff --git a/source/includes/extracts-alerts.yaml b/source/includes/extracts-alerts.yaml
@@ -17,16 +17,17 @@ content: |
      :stub-columns: 1
 
      * - {+bagent+} has too many conf call failures
-       - The cluster topology known to monitoring does not match the backup
-         configuration from :term:`conf calls <conf call>` the {+bagent+}
-         makes. 
+
+       - The cluster topology known to monitoring does not match the
+         backup configuration from :term:`conf calls <conf call>` the {+bagent+} makes. 
 
          The number of attempts meets the threshold you specified in
          :setting:`maximumFailedConfCalls
          <mms.alerts.BackupAgentConfCallFailure.maximumFailedConfCalls>`
          setting.
 
-         .. note:: :doc:`Global alert </tutorial/manage-global-alerts>` only
+         You can use this alert as a :ref:`global alert <mms-manage-global-alerts>` only.
+
 
 ---
 ref: alert-global-alerts
@@ -40,25 +41,23 @@ content: |
 
        - A backup job fails to bind to a Backup Daemon. 
 
-         .. example::
+         For example, reasons that a job might fail to bind include, but are not limited to:
 
-            Reasons that a job might fail to bind include, but are not
-            limited to:
-
-            - No :manual:`primary </reference/glossary/#std-term-primary>` is found for the backed-up replica
-              set. At the time the binding occurred, the {+magent+} did not detect a primary. Ensure that the replica
-              set is healthy.
+         - No :manual:`primary </reference/glossary/#std-term-primary>`
+           is found for the backed-up replica
+           set. At the time the binding occurred, the {+magent+} did not detect a primary. Ensure that the replica
+           set is healthy.
      
-            - Not enough space is available on any Backup Daemon.
+         - Not enough space is available on any Backup Daemon.
 
-            In both cases, resolve the issue and then :doc:`restart the
-            initial sync of the backup </tutorial/enable-backup>`.
+           In both cases, resolve the issue and then :doc:`restart the
+           initial sync of the backup </tutorial/enable-backup>`.
 
-            As an alternative, you can manually bind jobs to daemons
-            through the :guilabel:`Admin` interface. See
-            :ref:`jobs-page` for more information.
+           As an alternative, you can manually bind jobs to daemons
+           through the :guilabel:`Admin` interface. See
+           :ref:`jobs-page` for more information.
 
-         .. note:: :doc:`Global alert </tutorial/manage-global-alerts>` only
+         You can use this alert as a :ref:`global alert <mms-manage-global-alerts>` only.
 
      * - Backup has reached a high number of retries
 
@@ -70,7 +69,7 @@ content: |
          Contact MongoDB Support if you need help interpreting the
          error message.
 
-         .. note:: :doc:`Global alert </tutorial/manage-global-alerts>` only
+         You can use this alert as a :ref:`global alert <mms-manage-global-alerts>` only.
 
      * - Backup is in an unexpected state
 
@@ -84,15 +83,15 @@ content: |
          error message explaining the problem. Contact MongoDB Support
          if you need help interpreting the error message.
 
-         .. note:: :doc:`Global alert </tutorial/manage-global-alerts>` only
+         You can use this alert as a :ref:`global alert <mms-manage-global-alerts>` only.
 
      * - Replica set has a late snapshot
 
        - A snapshot has failed to complete before the next snapshot is
          scheduled to begin. :ref:`Check the job log <jobs-page>` in
          the |mms| Admin interface for any errors.
 
-         .. note:: :doc:`Global alert </tutorial/manage-global-alerts>` only
+         You can use this alert as a :ref:`global alert <mms-manage-global-alerts>` only.
 
      * - Sync slice transfer has not progressed in...
 
@@ -104,7 +103,7 @@ content: |
          - network issues
          - incorrect authentication credentials
 
-         .. note:: :doc:`Global alert </tutorial/manage-global-alerts>` only
+         You can use this alert as a :ref:`global alert <mms-manage-global-alerts>` only.
 
      * - Backup job is busy for...
 
@@ -122,7 +121,7 @@ content: |
          for error messages. Contact MongoDB Support if you need help
          interpreting the error message.
 
-         .. note:: :doc:`Global alert </tutorial/manage-global-alerts>` only
+         You can use this alert as a :ref:`global alert <mms-manage-global-alerts>` only.
 
 ---
 
@@ -134,6 +133,7 @@ content: |
      :stub-columns: 1
 
      * - Host is down
+
        - |mms| does not receive a ping from a host for more than 4
          minutes. Under normal operation, the {+magent+} connects
          to each monitored host about once per minute. |mms| waits 4
diff --git a/source/includes/extracts-api-alert-configuration.yaml b/source/includes/extracts-api-alert-configuration.yaml
@@ -415,11 +415,9 @@ content: |
        - Units for the threshold value. Depends on the type of 
          metric. 
          
-         .. example:: 
-
-            A metric that measures memory consumption would have a 
-            byte measurement, while a metric that measures time would 
-            have a time unit.
+         For example, a metric that measures memory consumption would
+         have a byte measurement, while a metric that measures time
+         would have a time unit.
          
          Accepted values are:
          
diff --git a/source/includes/note-scp-removed.rst b/source/includes/note-scp-removed.rst
@@ -1,4 +1,2 @@
-.. important::
-
-   Restore delivery via :abbr:`SCP (secure copy)` was removed in
-   |onprem| 4.0.
+:gold:`IMPORTANT:` Restore delivery using :abbr:`SCP (secure copy)` was
+removed in |onprem| 4.0.
diff --git a/source/includes/steps-create-custom-mongodb-version.yaml b/source/includes/steps-create-custom-mongodb-version.yaml
@@ -35,11 +35,11 @@ content: |
        - Your label for this build. It must begin with a valid MongoDB
          version number.
 
-         .. example::
+         For example:
 
-            .. code-block:: sh
+         .. code-block:: sh
 
-               3.6.2-myCustomBuild
+            3.6.2-myCustomBuild
 
      * - Download |url|
        - |url| from which the {+mdbagent+} can download this build.
@@ -49,21 +49,19 @@ content: |
          - Point to a host running an |http|\-compatible web server.
          - Point to the Custom Build binary file.
 
-         .. important::
-
-            The |application| does not check if this |url| exists, only
-            that it is `a complete URL
-            <https://www.w3.org/Addressing/URL/url-spec.html>`_.
+         :gold:`IMPORTANT:` The |application| does not check if this 
+         |url| exists, only that it is `a complete URL
+         <https://www.w3.org/Addressing/URL/url-spec.html>`_.
 
      * - Git Version
        - The complete 40-character ``git`` SHA-1 checksum (or *hash*)
          for this build.
 
-         .. example::
+         For example:
 
-            .. code-block:: sh
+         .. code-block:: sh
 
-               f3fa18bc6d8a749b7a526d83d2ad969fae1236c7
+            f3fa18bc6d8a749b7a526d83d2ad969fae1236c7
 
      * - Modules
        - If your Custom Build included any add-on modules, enter them
diff --git a/source/reference/alerts.txt b/source/reference/alerts.txt
diff --git a/source/reference/api/events/get-all-events-for-org.txt b/source/reference/api/events/get-all-events-for-org.txt
diff --git a/source/reference/api/events/get-all-events-for-project.txt b/source/reference/api/events/get-all-events-for-project.txt
diff --git a/source/reference/deployment-advanced-options.txt b/source/reference/deployment-advanced-options.txt
