feat(Sonic): Added mobile monitoring key popover

src/content/docs/accounts/accounts-billing/account-setup/downgradecancel-account.mdx

@@ -25,7 +25,8 @@ If you want to stop reporting some data to New Relic without downgrading or canc
 For how to manage data ingest, see [Manage your data](/docs/telemetry-data-platform/get-data-new-relic/manage-data/manage-your-data).
 
 To uninstall agents or integrations, here are some recommended procedures:
-* [Remove <InlinePopover type="apm" />, <InlinePopover type="browser" />, and mobile apps](/docs/apm/new-relic-apm/maintenance/remove-applications-new-relic/)
+
+* [Remove <InlinePopover type="apm" />, <InlinePopover type="browser" />, and <InlinePopover type="mobile" /> apps](/docs/apm/new-relic-apm/maintenance/remove-applications-new-relic/)
 * [Remove infrastructure agent](/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent/)
 * For how to disable other New Relic tools, see their specific docs. You can [search New Relic solutions here](https://newrelic.com/instant-observability/).
 

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx

@@ -497,5 +497,6 @@ Here are some technical details about how `bytecountestimate()` works:
 
 * There are several types of data that [don't count towards ingest](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#usage-calculation) but that is returned by the `bytecountestimate()` function. This means that this function sometimes shows **more** data than actually is counted towards your usage. It may rarely show a lower amount but, if it does, it will be only slightly lower. 
 * Some telemetry data reported from an entity shares common attributes (for example, attributes about your New Relic account). We don't count the duplicated attributes towards your ingest, but `bytecountestimate()` does count those attributes. This can sometimes result in a large discrepency between a `bytecountestimate()` query and your actual usage. 
-* Our <InlinePopover type="apm" />, <InlinePopover type="browser" />, and mobile monitoring report a type of data known as [metric timeslice data](/docs/data-apis/understand-data/new-relic-data-types/#timeslice-data). This data isn't stored in NRDB like our other data types are, and so trying to use `bytecountestimate()` on this data can result in confusing results. When querying this data, we recommend faceting by application name, and not by the metric name. 
+* Our <InlinePopover type="apm" />, <InlinePopover type="browser" />, and <InlinePopover type="mobile" /> report a type of data known as [metric timeslice data](/docs/data-apis/understand-data/new-relic-data-types/#timeslice-data). This data isn't stored in NRDB like our other data types are, and so trying to use `bytecountestimate()` on this data can result in confusing results. When querying this data, we recommend faceting by application name, and not by the metric name. 
+
 

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions.mdx

@@ -255,7 +255,7 @@ These permissions pertain to [incident intelligence](/docs/alerts-applied-intell
     id="mobile"
     title="Mobile"
   >
-* **Applications**: relates to [mobile monitoring features](/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring) for your monitored apps. 
+* **Applications**: relates to [<InlinePopover type="mobile" /> features](/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring) for your monitored apps. 
 * **Crashes**: relates to [crash analysis features](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/crash-analysis-group-filter-your-crashes).
 </Collapser>
 

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx

@@ -71,7 +71,7 @@ Here's a brief summary of what each user type gets access to:
       </td>
 
       <td>
-        Full platform users can access everything, including our more curated observability UI experiences, such as APM, infrastructure monitoring, browser monitoring, mobile monitoring, synthetic monitors, and more.
+        Full platform users can access everything, including our more curated observability UI experiences, such as APM, infrastructure monitoring, browser monitoring, <InlinePopover type="mobile" />, synthetic monitors, and more.
       </td>
     </tr>
   </tbody>

src/content/docs/accounts/accounts/account-maintenance/account-email-settings.mdx

@@ -61,4 +61,4 @@ There are a few different product-related emails, with different ways to control
 
 * Alerts: For how to control alert-related emails, see [Alert notifications](/docs/alerts/new-relic-alerts/managing-notification-channels/view-or-update-user-email-channels).
 * <InlinePopover type="apm" /> weekly report emails: See [APM performance reports](/docs/apm/reports/other-performance-analysis/weekly-performance-report#opting_out).
-* Mobile reports: see [Crash report emails](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/receive-crash-notifications-email) and [Version trend emails](/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/version-trends-compare-user-adoption-metrics-performance).
+* Reports from <InlinePopover type="mobile" />: see [Crash report emails](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/receive-crash-notifications-email) and [Version trend emails](/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/version-trends-compare-user-adoption-metrics-performance).

src/content/docs/accounts/original-accounts-billing/product-based-pricing/overview-data-retention-components.mdx

@@ -1086,7 +1086,7 @@ For organizations on our [original pricing model](/docs/accounts/original-accoun
     id="components-metric-data"
     title="Metric timeslice data: reported by APM, Browser, and Mobile"
   >
-    [Metric timeslice data](/docs/using-new-relic/data/understand-data/new-relic-data-types#timeslice-data) is a specific type of data that is used for most metric charts and reports in APM, mobile, and browser.
+    [Metric timeslice data](/docs/using-new-relic/data/understand-data/new-relic-data-types#timeslice-data) is a specific type of data that is used for most metric charts and reports in APM, <InlinePopover type="mobile" />, and browser.
 
     <Callout variant="important">
       Note that metric timeslice data differs from other [metric data types](/docs/using-new-relic/data/understand-data/new-relic-data-types#metrics).

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/rest-api-alerts/disable-enable-alerts-conditions-using-api.mdx

@@ -45,7 +45,7 @@ The process for disabling or enabling a condition is the same general process fo
      >
        If you don't know the category of the condition you want to change, you must search for it by making API calls using the four condition categories. Here are the different API call formats for the various condition categories.
 
-       * [<InlinePopover type="apm" />, <InlinePopover type="browser" />, and mobile monitoring](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions-list)  
+       * [<InlinePopover type="apm" />, <InlinePopover type="browser" />, and <InlinePopover type="mobile" />](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions-list)  
          Conditions available: `apm_app_metric`, `apm_kt_metric`, `browser_metric`, and `mobile_metric`  
          [API Explorer link Get>List](https://rpm.newrelic.com/api/explore/alerts_conditions/list)
        * [External services](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#ext-conditions-list)  

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/rest-api-alerts/manage-entities-alerts-conditions.mdx

@@ -35,7 +35,7 @@ To update the entity list for a condition:
 1. Locate the appropriate [entity ID](/docs/alerts/new-relic-alerts/getting-started/alerts-glossary#alert-entity); for example, [Application ID](/docs/apis/rest-api-v2/requirements/listing-host-instance-application-server-ids) and [browser ID](/docs/apis/rest-api-v2/browser-examples-v2/adding-or-listing-browser-apps-api-v2#specific-browser-app).
 2. [Identify the policy ID by name or type](/docs/apm/apis/alert-examples-v2/listing-policies-api-v2#single_policy).
 3. Get the list of conditions associated with the policy and choose the one you want to modify for the appropriate category:
-   * [<InlinePopover type="apm" />, <InlinePopover type="browser" />, and mobile](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions)
+   * [<InlinePopover type="apm" />, <InlinePopover type="browser" />, and <InlinePopover type="mobile" />](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions)
    * [External services](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#ext-services-conditions)
    * [Synthetic monitoring](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#synthetics-conditions)
 4. Modify the condition using the [add](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#add-entity) or [remove](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#remove_entity) API requests.

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/rest-api-alerts/rest-api-calls-alerts.mdx

@@ -99,7 +99,7 @@ Also, if you haven't already, create your free New Relic account below to start
         List output will be [paginated](/docs/apis/rest-api-v2/requirements/pagination-api-output). Available functions include:
 
         * [Alert policies](#policies-list)
-        * Conditions for [APM, <InlinePopover type="browser" />, and mobile](#conditions-list) ([Some limitations apply.](#excluded))
+        * Conditions for [<InlinePopover type="apm" />, <InlinePopover type="browser" />, and <InlinePopover type="mobile" />](#conditions-list) ([Some limitations apply.](#excluded))
         * Conditions for [external services](#ext-conditions-list)
         * Conditions for [synthetic monitoring](#synthetics-conditions)
         * Conditions for [Multi-location synthetic monitoring](#multilocation-synthetics-conditions)
@@ -318,7 +318,7 @@ These API functions include links to the API Explorer, where you can create, upd
 * Browser: Apps and key transactions
 * Mobile: Mobile apps
 
-**Exception:** The following <InlinePopover type="apm" /> conditions are **not available** from this API endpoint:
+**Exception:** The following APM conditions are **not available** from this API endpoint:
 
 * Conditions targeting labels (dynamic targeting)
 * Web transaction percentile conditions
@@ -612,7 +612,7 @@ These API functions include links to the API Explorer, where you can create, upd
     id="ext-conditions-create"
     title="External services: Create conditions for policies"
   >
-    To add conditions for external services to policies that have <InlinePopover type="apm" /> or mobile monitoring apps, include these values in the API call:
+    To add conditions for external services to policies that have APM or mobile monitoring apps, include these values in the API call:
 
     * Your [user key](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#user-api-key)
     * The `policy_id` (available from **[API Explorer](https://rpm.newrelic.com/api/explore/alerts_policies/list) > Alerts Policies > GET > List**)
@@ -656,7 +656,7 @@ These API functions include links to the API Explorer, where you can create, upd
     id="ext-conditions-update"
     title="External services: Update conditions for policies"
   >
-    To update conditions for external services to policies that have <InlinePopover type="apm" /> or mobile monitoring apps, include these values in the API call:
+    To update conditions for external services to policies that have APM or mobile monitoring apps, include these values in the API call:
 
     * Your [user key](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#user-api-key)
     * The external service condition's `id` (available from **[API Explorer](https://rpm.newrelic.com/api/explore/alerts_external_service_conditions/list) > Alerts External Service Conditions > GET > List**)
@@ -698,7 +698,7 @@ These API functions include links to the API Explorer, where you can create, upd
     id="ext-conditions-delete"
     title="External services: Delete conditions from policies"
   >
-    To delete conditions for external services from policies with <InlinePopover type="apm" /> or mobile monitoring apps, include these values in the API call:
+    To delete conditions for external services from policies with APM or mobile monitoring apps, include these values in the API call:
 
     * Your [user key](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#user-api-key)
     * The `condition_id` (available from **[API Explorer](https://rpm.newrelic.com/api/explore/alerts_conditions/list) > Alerts External Service Conditions > GET > List**)
@@ -1100,7 +1100,7 @@ These API functions include links to the API Explorer, where you can list, add a
     To add an [entity](/docs/alerts/new-relic-alerts-beta/getting-started/alerts-glossary#alert-entity) to a condition, include these values in the API call:
 
     * Your [user key](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#user-api-key)
-    * The `entity_id` This is the [entity (alert target)](/docs/alerts/new-relic-alerts-beta/getting-started/alerts-glossary#alert-entity) to be monitored. It is the numeric ID for the <InlinePopover type="apm" /> application, browser app, key transaction, or mobile app.
+    * The `entity_id` This is the [entity (alert target)](/docs/alerts/new-relic-alerts-beta/getting-started/alerts-glossary#alert-entity) to be monitored. It is the numeric ID for the APM application, browser app, key transaction, or mobile app.
     * The `condition_id` (available from **[API Explorer](https://rpm.newrelic.com/api/explore/alerts_conditions/list) > Alerts Conditions > GET > List**)
     * The `entity_type`, which must be one of the following:
 
@@ -1126,7 +1126,7 @@ These API functions include links to the API Explorer, where you can list, add a
     To remove an [entity](/docs/alerts/new-relic-alerts-beta/getting-started/alerts-glossary#alert-entity) being monitored from a condition, include these values in the API call:
 
     * Your [user key](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#user-api-key)
-    * The `entity_id` This is the specific monitored [entity (alert target)](/docs/alerts/new-relic-alerts-beta/getting-started/alerts-glossary#alert-entity) to be removed. It is the numeric ID for the <InlinePopover type="apm" /> application, browser app, key transaction, or mobile app.
+    * The `entity_id` This is the specific monitored [entity (alert target)](/docs/alerts/new-relic-alerts-beta/getting-started/alerts-glossary#alert-entity) to be removed. It is the numeric ID for the APM application, browser app, key transaction, or mobile app.
     * The `condition_id` (available from **[API Explorer](https://rpm.newrelic.com/api/explore/alerts_conditions/list) > Alerts Conditions > GET > List**)
     * The `entity_type`, which must be one of the following:
 

src/content/docs/alerts-applied-intelligence/new-relic-alerts/alert-notifications/muting-rules-suppress-notifications.mdx

@@ -480,7 +480,7 @@ For more information about making requests to NerdGraph, see the [NerdGraph docu
     id="rule-product"
     title="Create muting rule for specific hosts or products"
   >
-    To create a muting rule and return the muting rule's `id` for muting incidents from infrastructure conditions where the target host is `host-1` or the incident was from synthetic or mobile monitoring:
+    To create a muting rule and return the muting rule's `id` for muting incidents from infrastructure conditions where the target host is `host-1` or the incident was from synthetic or <InlinePopover type="mobile" />:
 
     ```
     mutation {

src/content/docs/apis/intro-apis/introduction-new-relic-apis.mdx

@@ -341,7 +341,7 @@ For querying your data and managing your logging, see the [NerdGraph docs](/docs
     id="mobile-api"
     title="Mobile monitoring"
   >
-    Mobile monitoring-related API resources include:
+    The <InlinePopover type="mobile" />-related API resources include:
 
     <table>
       <thead>

src/content/docs/apis/intro-apis/new-relic-api-keys.mdx

@@ -105,7 +105,7 @@ To get started with API keys:
       </td>
 
       <td>
-        License keys are used to report almost all data (except for browser and mobile monitoring data, which use their own keys). Each key is tied to a specific account and you can create as many as you want.
+        License keys are used to report almost all data (except for browser and <InlinePopover type="mobile" /> data, which use their own keys). Each key is tied to a specific account and you can create as many as you want.
       </td>
 
       <td>
@@ -218,7 +218,7 @@ Here's how to rotate each of our four most common API keys:
         id="rotate-license-key"
         title="Rotate license key"
     >
-      [License keys](/docs/apis/intro-apis/new-relic-api-keys/#license-key) are used to report almost all data (except for browser and mobile monitoring data, which use their own keys). Each key is tied to a specific account and users can create as many as they’d like. License keys can't be updated, and must be deleted and replaced by creating a new key. 
+      [License keys](/docs/apis/intro-apis/new-relic-api-keys/#license-key) are used to report almost all data (except for browser and mobile monitoring data, which use their own keys). Each key is tied to a specific account and users can create as many as they'd like. License keys can't be updated, and must be deleted and replaced by creating a new key. 
 
       You can find license keys for your account in the API keys UI at [**one.newrelic.com/api-keys**](https://one.newrelic.com/api-keys) (or [**one.eu.newrelic.com/api-keys**](https://one.eu.newrelic.com/api-keys) for our EU datacenter). You'll only see keys you have permission to use, unless you have [All product admin permissions](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#standard-roles) or a custom role that enables you to see those keys.
 

src/content/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph.mdx

@@ -102,7 +102,7 @@ Variables:
 
 ## Examples of configuring mobile monitoring [#configure-mobile-application]
 
-Here's an example of how to configure mobile monitoring settings via NerdGraph:
+Here's an example of how to configure <InlinePopover type="mobile" /> settings via NerdGraph:
 
 Mutation:
 

src/content/docs/apis/nerdgraph/examples/nerdgraph-entities-api-tutorial.mdx

@@ -311,7 +311,8 @@ Entities in NerdGraph rely on [GraphQL interfaces](/docs/apis/graphql-api/gettin
     id="search-entity"
     title="Get data specific to each entity type in search results"
   >
-    Different entity types have specific data associated with them. This NerdGraph query example requests the name for all entities regardless of which entity type they are, as well as the error rate for APM, <InlinePopover type="browser" />, and mobile entities.
+
+    Different entity types have specific data associated with them. This NerdGraph query example requests the name for all entities regardless of which entity type they are, as well as the error rate for APM, <InlinePopover type="browser" />, and <InlinePopover type="mobile" /> entities.
 
     * If entities of other types are returned in your search results, they will not include an error rate field.
 

src/content/docs/apis/nerdgraph/examples/provisions-your-subscriptions-nerdgraph.mdx

@@ -306,7 +306,7 @@ With each account creation call, you must supply at least one New Relic product
     id="mapping-mobile"
     title="Mobile"
   >
-    New Relic Mobile's pricing structure allows 100,000 monthly active users per account at the Enterprise subscription level. Data retention varies by subscription level. Use the product ID’s integer format to identify the subscription level.
+    New Relic Mobile's pricing structure allows 100,000 monthly active users per account at the Enterprise subscription level. Data retention varies by subscription level. Use the product ID's integer format to identify the subscription level.
 
     <table>
       <thead>

src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx

@@ -20,7 +20,8 @@ You can use the [API keys UI](https://one.newrelic.com/launcher/api-keys-ui.api-
 
 * [User keys](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#personal-api-key), required for using NerdGraph
 * Data ingest keys, including:
-  * The <InlinePopover type="licenseKey" />: required for the ingest of most data to New Relic, except for <InlinePopover type="browser" /> data and mobile monitoring data
+
+  * The <InlinePopover type="licenseKey" />: required for the ingest of most data to New Relic, except for <InlinePopover type="browser" /> data and <InlinePopover type="mobile" /> data
   * [Browser key](/docs/browser/new-relic-browser/configuration/copy-browser-monitoring-license-key-app-id): required for the ingest of browser monitoring data
 
 One common use case for this feature is the ability to rotate keys for security purposes. Note that you can't use this NerdGraph functionality to delete the license key or browser key that was originally created with an account; those original keys can't be deleted. You can only create additional license keys and manage the ones you've created.