(DOCSP-43014) [OM] OM nested components group 5 (#381)

## Unnesting components in 11 OM pages. 
[This
spreadsheet](https://docs.google.com/spreadsheets/d/1M2IlsyV0-6mY-AvBBrX-4uSDtQrbt9zuoXsqIJaVqlk/edit?gid=0#gid=0)
tracks the number of nested components on each page, and [this
doc](https://docs.google.com/document/d/1yMbng-EPOQ82bAzBTC2VJwIvsUBOSCJh21cGbDoe1a8/edit#heading=h.7hxlffls9cx6)
provides guidelines for fixing nested components.

## [DOCSP-43014](https://jira.mongodb.org/browse/DOCSP-43014)

## STAGING
1.
[ops-manager/current/reference/api/events/get-all-events-global/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/events/get-all-events-global/)
— Unnested 1 example in table, and reworked example for style guide.
2.
[ops-manager/current/reference/api/events/get-one-event-global/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/events/get-one-event-global/)
— Unnested 1 example in table, same commit include as in Get All Events
Global.
3.
[ops-manager/current/reference/api/global-alert-configuration-get-all-open-alerts-triggered/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/global-alert-configuration-get-all-open-alerts-triggered/)
— Unnested 1 example in table, same commit as above.
4.
[ops-manager/current/reference/api/global-alert-configurations-create-one/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/global-alert-configurations-create-one/)
— Unnested 2 notes in tables and deleted a redundant extra
``metricThreshold.units`` table entry. Note: could not find the 7
admonitions in tables reported in the spreadsheet.
5.
[ops-manager/current/reference/api/global-alert-configurations-get-all/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/global-alert-configurations-get-all/)
— Unnested 1 example in table in previous commit. Note: Could not find
the 6 admonitions in tables reported in the spreadsheet.
6.
[ops-manager/current/reference/api/global-alert-configurations-get-one/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/global-alert-configurations-get-one/)
— Unnested 1 example in table in previous commit. Note: Could not find
the 6 admonitions in tables reported in the spreadsheet.
7.
[ops-manager/current/reference/api/global-alert-configurations-toggle-one/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/global-alert-configurations-toggle-one/)
— Unnested 1 example in table in previous commit. Note: Could not find
the 6 admonitions in tables reported in the spreadsheet.
8.
[ops-manager/current/reference/api/global-alert-configurations-update-one/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/global-alert-configurations-update-one/)
— Unnested 2 examples in tables in previous commit. Note: Could not find
the 7 admonitions in tables reported in the spreadsheet.
9.
[ops-manager/current/reference/api/global-alerts-ack-one/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/global-alerts-ack-one/)—
Unnested 1 example in table in previous commit.
10.
[ops-manager/current/reference/api/global-alerts-get-all/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/global-alerts-get-all/)
— Unnested 1 example in table in previous commit.
11.
[ops-manager/current/reference/api/global-alerts-get-one/](https://deploy-preview-381--10gen-docs-ops-manager.netlify.app/reference/api/global-alerts-get-one/)
— Unnested 1 example in previous commit.

## [LATEST BUILD
LOG](https://app.netlify.com/sites/10gen-docs-ops-manager/deploys/66f45494db00a83d5e5a3f18)

## Self-Review Checklist

- [ ]
[Define](https://wiki.corp.mongodb.com/display/DE/Taxonomy+tagging+instructions)
taxonomy
[values](https://wiki.corp.mongodb.com/display/DE/Docs+Taxonomy) at top
of page.
- [ ] Add genre facets (tutorial or reference), as in this [example
PR](10gen/cloud-docs#5042).
- [ ] Add programmingLanguage (if necessary).
- [ ] Add meta keywords (if necessary).
- [x] Resolve any new warnings or errors in the build.
- [x] Proofread for spelling and grammatical errors.
- [x] Check staging for rendering issues.
- [x] Confirm links are working.

---------

Co-authored-by: Elyse Foreman <elyse-mdb>

Author: elyse-mdb

source/includes/api/list-tables/events/responses/global-onprem.rst

@@ -54,16 +54,15 @@
    * - | currentValue
        | .units
      - 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.
+     - Units for ``currentValue.number``. The units depend on the type of metric.
 
        Accepted values are:
 
        .. include:: /includes/possibleValues-api-units.rst
 
+       For example, a metric that measures memory consumption can use ``BYTES``, 
+       while a metric that measures time can use ``HOURS``. 
+
    * - database
      - string
      - Name of the database on which the event occurred. This field

source/includes/api/list-tables/global-alert-configuration-request-body.rst

@@ -122,13 +122,16 @@
        | ``.units``
      - string
      - Conditional
-     - Units for ``metricThreshold.threshold``. The value depends on
-       the type of metric. For example, a metric that measures memory 
-       consumption has a byte measurement, while a metric that 
-       measures time has a time unit. Accepted values are:
+     - Units for ``metricThreshold.threshold``. The units depend on
+       the type of metric. 
+       
+       Accepted values are:
 
        .. include:: /includes/possibleValues-api-units.rst
 
+       For example, a metric that measures memory consumption can use ``BYTES``, 
+       while a metric that measures time can use ``HOURS``. 
+
    * - ``notifications``
      - array of objects
      - Required
@@ -294,22 +297,6 @@
      - Threshold value outside of which this alert configuration
        triggers an alert.
 
-   * - ``metricThreshold.units``
-     - string
-     - Conditional
-     - Units for ``metricThreshold.threshold``. The value depends on
-       the type of metric. 
-
-       .. example:: 
-
-          A metric that measures memory consumption has a byte 
-          measurement, while a metric that measures time has a time 
-          unit. 
- 
-       Accepted values are:
-
-       .. include:: /includes/possibleValues-api-units.rst
-
    * - ``tags``
      - array of strings
      - Optional

source/includes/api/list-tables/global-alert-configuration-response.rst

@@ -107,19 +107,16 @@
 
    * - ``metricThreshold.units``
      - string
-     - Units for ``metricThreshold.threshold``. The value depends on
+     - Units for ``metricThreshold.threshold``. The units depend on
        the type of metric. 
 
-       .. example::
-
-          A metric that measures memory consumption has a byte 
-          measurement, while a metric that measures time has a time 
-          unit. 
- 
-       Possible values are:
+       Accepted values are:
 
        .. include:: /includes/possibleValues-api-units.rst
 
+       For example, a metric that measures memory consumption can use ``BYTES``, 
+       while a metric that measures time can use ``HOURS``. 
+
    * - ``notifications``
      - array of objects
      - Notifications |mms| sends when it detects an alert that this 

source/includes/api/list-tables/global-alert-response.rst

@@ -61,17 +61,15 @@
 
    * - ``currentValue.units``
      - string
-     - Units in which this value is expressed. Depends on the type of metric.
+     - Units for ``currentValue.number``. The units depend on the type of metric.
 
-       .. example::
-       
-          - A metric that measures memory consumption would have a byte measurement
-          - A metric that measures time would have a time unit.
-          
-       Possible values that can be returned include:
+       Accepted values are:
 
        .. include:: /includes/possibleValues-api-units.rst
 
+       For example, a metric that measures memory consumption can use ``BYTES``, 
+       while a metric that measures time can use ``HOURS``. 
+
    * - ``eventTypeName``
      - string
      - Name of the event that triggered the alert.