diff --git a/src/content/docs/apis/intro-apis/new-relic-api-keys.mdx b/src/content/docs/apis/intro-apis/new-relic-api-keys.mdx
index 2f9a93c6f80..393c7e1a798 100644
--- a/src/content/docs/apis/intro-apis/new-relic-api-keys.mdx
+++ b/src/content/docs/apis/intro-apis/new-relic-api-keys.mdx
@@ -105,7 +105,7 @@ To get started with API keys:
|
- 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 data, which use their own keys). Each key is tied to a specific account and you can create as many as you want.
|
@@ -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.
diff --git a/src/content/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph.mdx b/src/content/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph.mdx
index 2ea7d7f4dab..52ce2603602 100644
--- a/src/content/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph.mdx
+++ b/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 settings via NerdGraph:
Mutation:
diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-entities-api-tutorial.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-entities-api-tutorial.mdx
index b7b6bfd6977..cc5283ae28b 100644
--- a/src/content/docs/apis/nerdgraph/examples/nerdgraph-entities-api-tutorial.mdx
+++ b/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, , 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, , and entities.
* If entities of other types are returned in your search results, they will not include an error rate field.
diff --git a/src/content/docs/apis/nerdgraph/examples/provisions-your-subscriptions-nerdgraph.mdx b/src/content/docs/apis/nerdgraph/examples/provisions-your-subscriptions-nerdgraph.mdx
index b6a50a74d5a..a35d7ba9bcf 100644
--- a/src/content/docs/apis/nerdgraph/examples/provisions-your-subscriptions-nerdgraph.mdx
+++ b/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.
diff --git a/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx b/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx
index 6c21d79572a..7a13eba2efa 100644
--- a/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx
+++ b/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 : required for the ingest of most data to New Relic, except for data and mobile monitoring data
+
+ * The : required for the ingest of most data to New Relic, except for data and 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.
diff --git a/src/content/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph.mdx b/src/content/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph.mdx
index 368b8956ab6..8f9cfc00853 100644
--- a/src/content/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph.mdx
+++ b/src/content/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph.mdx
@@ -233,7 +233,7 @@ Account management
|
* [Create a new mobile app](/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph/#create-mobile)
* [Retrieve an application token](/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph/#get-mobile-token)
- * [Examples of configuring mobile monitoring](/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph/#configure-mobile-application)
+ * [Examples of configuring ](/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph/#configure-mobile-application)
|
diff --git a/src/content/docs/apm/agents/c-sdk/get-started/introduction-c-sdk.mdx b/src/content/docs/apm/agents/c-sdk/get-started/introduction-c-sdk.mdx
index c69dc666719..529ad95a059 100644
--- a/src/content/docs/apm/agents/c-sdk/get-started/introduction-c-sdk.mdx
+++ b/src/content/docs/apm/agents/c-sdk/get-started/introduction-c-sdk.mdx
@@ -155,7 +155,7 @@ If your app meets the C SDK's [compatibility and requirements in Linux environme
* Monitor and troubleshoot your application users' desktop experience with your application, including page load timing problems, JavaScript errors, session trace timelines, etc., by using [](/docs/browser/new-relic-browser/getting-started/introduction-new-relic-browser).
* Use automated, scriptable tools to monitor your websites, critical business transactions, and API endpoints with [synthetic monitoring](/docs/synthetics/new-relic-synthetics/getting-started/introduction-new-relic-synthetics).
- * Analyze and fine-tune your Android and iOS application performance, troubleshoot crashes, compare multiple versions, and examine the performance of HTTP and other network components with [mobile monitoring](/docs/mobile-monitoring/new-relic-mobile/getting-started/introduction-new-relic-mobile).
+ * Analyze and fine-tune your Android and iOS application performance, troubleshoot crashes, compare multiple versions, and examine the performance of HTTP and other network components with [](/docs/mobile-monitoring/new-relic-mobile/getting-started/introduction-new-relic-mobile).
|
diff --git a/src/content/docs/apm/apm-ui-pages/events/record-deployments.mdx b/src/content/docs/apm/apm-ui-pages/events/record-deployments.mdx
index eec0d873b19..902eae5b6be 100644
--- a/src/content/docs/apm/apm-ui-pages/events/record-deployments.mdx
+++ b/src/content/docs/apm/apm-ui-pages/events/record-deployments.mdx
@@ -24,7 +24,7 @@ freshnessValidatedDate: never
import trackingIdentifyPreview from 'images/tracking_screenshot-crop_identify-preview.webp'
- We recommend that you use the [change tracking](/docs/change-tracking/change-tracking-introduction/) feature instead of the older deployment markers. If you've been using deployment markers feature, you can still use it, but keep in mind that the change tracking feature is available for and mobile, as well as .
+ We recommend that you use the [change tracking](/docs/change-tracking/change-tracking-introduction/) feature instead of the older deployment markers. If you've been using deployment markers feature, you can still use it, but keep in mind that the change tracking feature is available for and , as well as .
Deploying an app can be a risky event—when your app breaks, and a bad deployment is often the cause. New Relic allows you to track deployments so you can correlate deployments with changes in your app's performance. Tracking deployments creates deployment markers that appear in APM charts and dashboards.
diff --git a/src/content/docs/apm/apm-ui-pages/monitoring/external-services/external-services-intro.mdx b/src/content/docs/apm/apm-ui-pages/monitoring/external-services/external-services-intro.mdx
index f2248afd542..6fa0610987b 100644
--- a/src/content/docs/apm/apm-ui-pages/monitoring/external-services/external-services-intro.mdx
+++ b/src/content/docs/apm/apm-ui-pages/monitoring/external-services/external-services-intro.mdx
@@ -70,10 +70,10 @@ While you can still reach classic external services by using the UI toggle, the
* **Dependency:** To use the external services feature, you need to enable distributed tracing on services that make calls to each other.
* **Compatibility:** Distributed tracing is not backwards compatible with cross application tracing, so if you currently rely on classic external services, please note that you will only have visibility into calls between services using the same protocol.
-* **Data:** Unlike classic external services, the transaction-level detail of distributed tracing is based on sampling instead of metrics. This sampled data links into distributed tracing, which can give you deeper insights into what’s driving the performance of the transactions.
+* **Data:** Unlike classic external services, the transaction-level detail of distributed tracing is based on sampling instead of metrics. This sampled data links into distributed tracing, which can give you deeper insights into what's driving the performance of the transactions.
- The external services feature does not support and mobile data.
+ The external services feature does not support and data.
## What's next? [#next]
diff --git a/src/content/docs/apm/errors-inbox/errors-inbox-ui.mdx b/src/content/docs/apm/errors-inbox/errors-inbox-ui.mdx
index c724d2b9822..4be759de23c 100644
--- a/src/content/docs/apm/errors-inbox/errors-inbox-ui.mdx
+++ b/src/content/docs/apm/errors-inbox/errors-inbox-ui.mdx
@@ -19,7 +19,7 @@ No additional setup or workloads are needed to triage errors in APM. Just naviga
1. On the APM UI overview screen, click the **Errors inbox** option in the left-hand navigation in the triage section.
2. This errors inbox view groups errors related specifically to the APM service you are looking at. You can see all error details and also triage the error right in the APM UI.
3. Click an error group's details to see the stack trace, logs in context attributes, and other information without navigating to other screens or services.
-4. Click **Go to global inbox** for the broader errors inbox experience, which groups errors across the entire stack, including and mobile errors. New Relic automatically finds a workload that includes the APM service you were looking at or prompts you to create a new workload.
+4. Click **Go to global inbox** for the broader errors inbox experience, which groups errors across the entire stack, including and errors. New Relic automatically finds a workload that includes the APM service you were looking at or prompts you to create a new workload.
Using errors inbox in APM gives you an added layer of convenience, allowing you to triage errors without switching screens.
diff --git a/src/content/docs/apm/new-relic-apm/maintenance/remove-applications-new-relic.mdx b/src/content/docs/apm/new-relic-apm/maintenance/remove-applications-new-relic.mdx
index bc59cd5816f..abef69082d7 100644
--- a/src/content/docs/apm/new-relic-apm/maintenance/remove-applications-new-relic.mdx
+++ b/src/content/docs/apm/new-relic-apm/maintenance/remove-applications-new-relic.mdx
@@ -28,7 +28,7 @@ For more information, see our [data retention guidelines](/docs/accounts/account
## Before attempting to remove an app [#requirements]
-Before attempting to remove an app monitored by New Relic , , or mobile monitoring from the UI, keep in mind:
+Before attempting to remove an app monitored by New Relic , , or from the UI, keep in mind:
* You can [downgrade your New Relic organization](/docs/accounts/accounts-billing/account-setup/downgradecancel-account) to pay less or make it entirely free.
* The ability to remove an app from the UI may be dependent on [permissions](/docs/accounts/accounts-billing/account-structure/factors-affecting-access-features-data/#user-permissions).
diff --git a/src/content/docs/change-tracking/change-tracking-graphql.mdx b/src/content/docs/change-tracking/change-tracking-graphql.mdx
index 7a9dd5973c7..5a3f35015b1 100644
--- a/src/content/docs/change-tracking/change-tracking-graphql.mdx
+++ b/src/content/docs/change-tracking/change-tracking-graphql.mdx
@@ -62,7 +62,7 @@ The fields you'll use in your GraphQL queries fall into these general types:
`version`
- The version attribute value can be anything, although we recommend using the version number set during your build process. To see an example of how this can be done, see our [Jenkins deployments plugin documentation](#jenkins-markers) below. If you already report version numbers to New Relic mobile monitoring or by some other means, we recommend using the same here to set yourself up for forthcoming features that will allow you to facet and correlate data by version.
+ The version attribute value can be anything, although we recommend using the version number set during your build process. To see an example of how this can be done, see our [Jenkins deployments plugin documentation](#jenkins-markers) below. If you already report version numbers to New Relic or by some other means, we recommend using the same here to set yourself up for forthcoming features that will allow you to facet and correlate data by version.
|
diff --git a/src/content/docs/change-tracking/change-tracking-introduction.mdx b/src/content/docs/change-tracking/change-tracking-introduction.mdx
index 635d2ef7df3..9d748470e5c 100644
--- a/src/content/docs/change-tracking/change-tracking-introduction.mdx
+++ b/src/content/docs/change-tracking/change-tracking-introduction.mdx
@@ -17,7 +17,7 @@ import changetrackingIntroDeploymentExample from 'images/tracking_screenshot-cro
Change tracking allows you to capture changes, such as deployments, on any part of your system and use them to contextualize performance data. With this feature, you can:
* Record changes via API or configure your deployment pipelines to do it for you.
-* View those changes as markers on charts for APM, browser, mobile, service level management, custom dashboards, and many more experiences across New Relic.
+* View those changes as markers on charts for APM, browser, , service level management, custom dashboards, and many more experiences across New Relic.
Our change analysis UIs provide details and insights about each of the changes you track, such as faceted errors, log attribute trends, related issues and anomalies, and calculated impacts on key signals. With these insights, you'll be able to understand the impact of changes on system performance and quality. Change tracking metadata, such as commit SHAs, changelogs, and deep links, will help you resolve issues more quickly.
diff --git a/src/content/docs/data-apis/custom-data/custom-events/collect-custom-attributes.mdx b/src/content/docs/data-apis/custom-data/custom-events/collect-custom-attributes.mdx
index ae02c3cbded..51c2dc06ef2 100644
--- a/src/content/docs/data-apis/custom-data/custom-events/collect-custom-attributes.mdx
+++ b/src/content/docs/data-apis/custom-data/custom-events/collect-custom-attributes.mdx
@@ -270,7 +270,7 @@ Our [Infrastructure monitoring](/docs/infrastructure/new-relic-infrastructure/ge
Mobile agents include API calls to record custom attributes:
-* For an overview of mobile monitoring custom data, see [Insert custom events and attributes](/docs/insights/insights-data-sources/custom-events/insert-custom-events-attributes-mobile-data)
+* For an overview of custom data, see [Insert custom events and attributes](/docs/insights/insights-data-sources/custom-events/insert-custom-events-attributes-mobile-data)
* Android method: [`setAttribute`](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/create-attribute/)
* iOS method: [`setAttribute`](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/create-attribute/)
diff --git a/src/content/docs/data-apis/custom-data/custom-events/report-custom-event-data.mdx b/src/content/docs/data-apis/custom-data/custom-events/report-custom-event-data.mdx
index 19105fb5aa9..5091de52c85 100644
--- a/src/content/docs/data-apis/custom-data/custom-events/report-custom-event-data.mdx
+++ b/src/content/docs/data-apis/custom-data/custom-events/report-custom-event-data.mdx
@@ -33,7 +33,7 @@ Two popular solutions for reporting custom data are reporting custom events and
Custom attributes are often used to add important business and operational context to existing events. For example, for New Relic , you might create a custom attribute to track the user name associated with a slow or failing request. This would then allow you to create queries and custom charts to analyze that data.
-Custom attributes are a good option when you're using a New Relic solution (like APM, browser, mobile, infrastructure, and synthetic monitoring) and want to decorate existing events with your own metadata.
+Custom attributes are a good option when you're using a New Relic solution (like APM, browser, , infrastructure, and synthetic monitoring) and want to decorate existing events with your own metadata.
### Use cases for custom events
diff --git a/src/content/docs/data-apis/custom-data/custom-events/report-mobile-monitoring-custom-events-attributes.mdx b/src/content/docs/data-apis/custom-data/custom-events/report-mobile-monitoring-custom-events-attributes.mdx
index 5082dfbedee..5733c4b8d4a 100644
--- a/src/content/docs/data-apis/custom-data/custom-events/report-mobile-monitoring-custom-events-attributes.mdx
+++ b/src/content/docs/data-apis/custom-data/custom-events/report-mobile-monitoring-custom-events-attributes.mdx
@@ -25,7 +25,7 @@ By default, New Relic collects some [event data](/docs/insights/insights-data-so
## Create custom attributes and events [#custom-attributes-instructions]
-You can create custom session-level attributes for default mobile monitoring events using the mobile agent SDK. For example, to record a `username` attribute for some part of your iOS or Android app, you would use the [`setAttribute` API](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/create-attribute). These attributes are session-related information and are shared by multiple mobile event types.
+You can create custom session-level attributes for default events using the mobile agent SDK. For example, to record a `username` attribute for some part of your iOS or Android app, you would use the [`setAttribute` API](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/create-attribute). These attributes are session-related information and are shared by multiple mobile event types.
You can also create entirely new custom event types and assign them their own custom attributes, using the [`recordCustomEvent` API](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-custom-events).
diff --git a/src/content/docs/data-apis/custom-data/get-custom-data-from-any-source.mdx b/src/content/docs/data-apis/custom-data/get-custom-data-from-any-source.mdx
index f11fa6fc0bc..b7a802f8379 100644
--- a/src/content/docs/data-apis/custom-data/get-custom-data-from-any-source.mdx
+++ b/src/content/docs/data-apis/custom-data/get-custom-data-from-any-source.mdx
@@ -12,7 +12,7 @@ To get the most out of New Relic, you may need or want to report custom data. We
## First, check out our more curated solutions [#options]
-New Relic products report a lot of data automatically, no additional configuration required! When you use monitoring solutions like , , mobile monitoring, infrastructure monitoring, or any of our assorted [integrations and quickstarts](https://newrelic.com/instant-observability), by default you receive various types of performance data.
+New Relic products report a lot of data automatically, no additional configuration required! When you use monitoring solutions like , , , infrastructure monitoring, or any of our assorted [integrations and quickstarts](https://newrelic.com/instant-observability), by default you receive various types of performance data.
But you may want to bring data into New Relic that isn't collected by default. Maybe you want an API-based solution that doesn't require the installation of an agent. Maybe you want to bring telemetry data from another analysis service into New Relic. Below, we'll describe several ways to get more custom sets of data into New Relic.
diff --git a/src/content/docs/data-apis/manage-data/manage-data-retention.mdx b/src/content/docs/data-apis/manage-data/manage-data-retention.mdx
index 7111bbc016c..5e7c4a77d42 100644
--- a/src/content/docs/data-apis/manage-data/manage-data-retention.mdx
+++ b/src/content/docs/data-apis/manage-data/manage-data-retention.mdx
@@ -495,7 +495,8 @@ Metric retention periods are not editable.
id="metric-timeslice"
title="Metric timeslice data (APM, browser, mobile)"
>
- [Metric timeslice data](/docs/using-new-relic/data/understand-data/new-relic-data-types#timeslice-data) is generated by (both custom metrics and default metrics), mobile, and browser agents. A metric timeslice consists of three parts: a metric name, the segment of time the metric represents (the "timeslice"), and a numeric value (the measurement). APM, , and mobile agents can collect thousands of metric timeslices per minute for a variety of performance metrics, such as error rate, bandwidth usage, and garbage collection time.
+
+ [Metric timeslice data](/docs/using-new-relic/data/understand-data/new-relic-data-types#timeslice-data) is generated by (both custom metrics and default metrics), , and browser agents. A metric timeslice consists of three parts: a metric name, the segment of time the metric represents (the "timeslice"), and a numeric value (the measurement). APM, , and mobile agents can collect thousands of metric timeslices per minute for a variety of performance metrics, such as error rate, bandwidth usage, and garbage collection time.
Metric timeslice data is aggregated like this:
* first to 1-minute rollups that are stored for 8 days
diff --git a/src/content/docs/data-apis/manage-data/view-system-limits.mdx b/src/content/docs/data-apis/manage-data/view-system-limits.mdx
index 8693f1d6981..e3782ec75da 100644
--- a/src/content/docs/data-apis/manage-data/view-system-limits.mdx
+++ b/src/content/docs/data-apis/manage-data/view-system-limits.mdx
@@ -236,7 +236,7 @@ This table includes general max limits that apply across all New Relic accounts.
|
- Rate of [metric timeslice data](/docs/telemetry-data-platform/ingest-manage-data/understand-data/new-relic-data-types#timeslice-data) (used by APM, browser, mobile)
+ Rate of [metric timeslice data](/docs/telemetry-data-platform/ingest-manage-data/understand-data/new-relic-data-types#timeslice-data) (used by APM, browser, )
|
diff --git a/src/content/docs/data-apis/understand-data/event-data/events-reported-mobile-monitoring.mdx b/src/content/docs/data-apis/understand-data/event-data/events-reported-mobile-monitoring.mdx
index 31cd31a018a..b21e29c7f92 100644
--- a/src/content/docs/data-apis/understand-data/event-data/events-reported-mobile-monitoring.mdx
+++ b/src/content/docs/data-apis/understand-data/event-data/events-reported-mobile-monitoring.mdx
@@ -19,7 +19,7 @@ redirects:
freshnessValidatedDate: never
---
-[Mobile monitoring in New Relic](/docs/mobile-monitoring/new-relic-mobile/getting-started/introduction-new-relic-mobile) reports [event data](/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data) that is displayed in some UI displays and is also available for [querying and charting](/docs/using-new-relic/data/understand-data/query-new-relic-data). Select an event name in the following table to see its attributes.
+Our [](/docs/mobile-monitoring/new-relic-mobile/getting-started/introduction-new-relic-mobile) reports [event data](/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data) that is displayed in some UI displays and is also available for [querying and charting](/docs/using-new-relic/data/understand-data/query-new-relic-data). Select an event name in the following table to see its attributes.
diff --git a/src/content/docs/data-apis/understand-data/event-data/new-relic-event-limits-sampling.mdx b/src/content/docs/data-apis/understand-data/event-data/new-relic-event-limits-sampling.mdx
index 21077177021..bdc16a7d7df 100644
--- a/src/content/docs/data-apis/understand-data/event-data/new-relic-event-limits-sampling.mdx
+++ b/src/content/docs/data-apis/understand-data/event-data/new-relic-event-limits-sampling.mdx
@@ -16,7 +16,7 @@ redirects:
freshnessValidatedDate: never
---
-Our agents and mobile agents have limits on the number of events that can be reported. This document explains:
+Our agents and agents have limits on the number of events that can be reported. This document explains:
* Why event-reporting limits are necessary
* How sampling works
diff --git a/src/content/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql.mdx b/src/content/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql.mdx
index 71cf290c7e2..d48676bc41a 100644
--- a/src/content/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql.mdx
+++ b/src/content/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql.mdx
@@ -13,7 +13,7 @@ APM reports metric data in the form of [metric timeslice data](/docs/using-new-r
## Why query metric timeslice data? [#why]
-We report [metrics in several ways](/docs/using-new-relic/data/understand-data/new-relic-data-types#metrics). One variety of metric data we call **metric timeslice data**; this is the type of data used to generate many of the charts in APM, mobile, and browser (for more details, see [metric timeslice data](/docs/using-new-relic/data/understand-data/new-relic-data-types#timeslice-data)).
+We report [metrics in several ways](/docs/using-new-relic/data/understand-data/new-relic-data-types#metrics). One variety of metric data we call **metric timeslice data**; this is the type of data used to generate many of the charts in APM, , and browser (for more details, see [metric timeslice data](/docs/using-new-relic/data/understand-data/new-relic-data-types#timeslice-data)).
Historically, this type of data couldn't be queried via our query language, NRQL. But now we are converting popular metrics from metric timeslice data to more-detailed dimensional metric data, which opens them up for querying via NRQL and via our [NerdGraph API](/docs/apis/nerdgraph/examples/nerdgraph-nrql-tutorial). This capability allows you to create powerful, in-depth custom visualizations of these important APM metrics. And this includes being able to query your [custom metrics](/docs/agents/manage-apm-agents/agent-data/collect-custom-metrics).
diff --git a/src/content/docs/data-apis/understand-data/new-relic-data-types.mdx b/src/content/docs/data-apis/understand-data/new-relic-data-types.mdx
index f581a4c131e..faf49f7c718 100644
--- a/src/content/docs/data-apis/understand-data/new-relic-data-types.mdx
+++ b/src/content/docs/data-apis/understand-data/new-relic-data-types.mdx
@@ -97,7 +97,7 @@ Some of our other metric data types are exposed as dimensional metrics and are a
id="timeslice-data"
title="Metric timeslice data (used by APM, browser, mobile)"
>
- New Relic's APM, browser, and mobile report and display metrics in a simple data format that we refer to as **metric timeslice data**. A metric timeslice consists of three parts: a metric name, the segment of time the metric represents (the "timeslice"), and a numeric value (the measurement).
+ New Relic's APM, browser, and report and display metrics in a simple data format that we refer to as **metric timeslice data**. A metric timeslice consists of three parts: a metric name, the segment of time the metric represents (the "timeslice"), and a numeric value (the measurement).
For example: an metric timeslice for time spent in a particular transaction is named `WebTransaction/URI/foo`, and might have a response time of 0.793 for a one-minute time slice from 10:20am to 10:21am. These metrics usually follow a pattern like `//`.
diff --git a/src/content/docs/distributed-tracing/concepts/distributed-tracing-planning-guide.mdx b/src/content/docs/distributed-tracing/concepts/distributed-tracing-planning-guide.mdx
index e12cc20f909..8b8b435841b 100644
--- a/src/content/docs/distributed-tracing/concepts/distributed-tracing-planning-guide.mdx
+++ b/src/content/docs/distributed-tracing/concepts/distributed-tracing-planning-guide.mdx
@@ -94,7 +94,7 @@ We may provide backward compatibility with some or all of the affected features
>
APM-related impacts include:
- * When distributed tracing is enabled for an APM-monitored entity, legacy [service maps](/docs/understand-dependencies/understand-system-dependencies/service-maps/introduction-service-maps) will not show applications monitored by mobile.
+ * When distributed tracing is enabled for an APM-monitored entity, legacy [service maps](/docs/understand-dependencies/understand-system-dependencies/service-maps/introduction-service-maps) will not show applications monitored by .
* The [App server drill-down](/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-requests-page#details) feature of the legacy mobile HTTP requests UI page is not available.
diff --git a/src/content/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works.mdx b/src/content/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works.mdx
index 1ac9ff23bf0..f1ec5c740a9 100644
--- a/src/content/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works.mdx
+++ b/src/content/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works.mdx
@@ -203,7 +203,8 @@ Some of our tools don't use sampling. Sampling details for these tools:
>
[Browser monitoring distributed tracing](/docs/browser/new-relic-browser/browser-pro-features/browser-data-distributed-tracing) and [mobile monitoring](/docs/mobile-monitoring/new-relic-mobile-android/get-started/new-relic-mobile-and-dt) report all spans.
- Our language agents are often used in conjunction with mobile and [, and our language agents [use sampling](#trace-origin-sampling). This means that there will likely be many more browser and mobile spans than backend spans, which can result in browser and mobile app spans disconnected from backend spans. For tips on querying for traces that contain front and backend spans, see [Find browser span data](/docs/browser/new-relic-browser/browser-pro-features/browser-data-distributed-tracing#find-data).
+ Our language agents are often used in conjunction with and [, and our language agents [use sampling](#trace-origin-sampling). This means that there will likely be many more browser and mobile spans than backend spans, which can result in browser and mobile app spans disconnected from backend spans. For tips on querying for traces that contain front and backend spans, see [Find browser span data](/docs/browser/new-relic-browser/browser-pro-features/browser-data-distributed-tracing#find-data).
+
diff --git a/src/content/docs/distributed-tracing/infinite-tracing/set-trace-observer.mdx b/src/content/docs/distributed-tracing/infinite-tracing/set-trace-observer.mdx
index eb1eba1dee0..57752eefd3f 100644
--- a/src/content/docs/distributed-tracing/infinite-tracing/set-trace-observer.mdx
+++ b/src/content/docs/distributed-tracing/infinite-tracing/set-trace-observer.mdx
@@ -17,7 +17,7 @@ freshnessValidatedDate: never
import distributedtracingMobileLambdaMenu from 'images/distributed-tracing_screenshot-crop_mobile-lambda-menu-.webp'
-If you are following the [steps to set up distributed tracing](/docs/distributed-tracing/enable-configure/quick-start) and are continuing with the steps for the advanced option called Infinite Tracing, you need to set up a trace observer. The trace observer is an AWS-based service for Infinite Tracing that provides you with a low-latency and low-cost way to send your telemetry data to New Relic. As it receives your tracing data, the trace observer uses [tail-based sampling](/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works/#tail-based) to decide what to keep and send to New Relic.
+If you're following the [steps to set up distributed tracing](/docs/distributed-tracing/enable-configure/quick-start) and are continuing with the steps for the advanced option called Infinite Tracing, you need to set up a trace observer. The trace observer is an AWS-based service for Infinite Tracing that provides you with a low-latency and low-cost way to send your telemetry data to New Relic. As it receives your tracing data, the trace observer uses [tail-based sampling](/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works/#tail-based) to decide what to keep and send to New Relic.
Complete the trace observer setup up that fits your types of data sources (services, apps, or entities). You may need to do steps in more than one section if you have a variety of types:
diff --git a/src/content/docs/distributed-tracing/troubleshooting/infinite-tracing-trace-configuration-conflicts.mdx b/src/content/docs/distributed-tracing/troubleshooting/infinite-tracing-trace-configuration-conflicts.mdx
index 78af383d06e..5174b0a30d1 100644
--- a/src/content/docs/distributed-tracing/troubleshooting/infinite-tracing-trace-configuration-conflicts.mdx
+++ b/src/content/docs/distributed-tracing/troubleshooting/infinite-tracing-trace-configuration-conflicts.mdx
@@ -22,7 +22,8 @@ A tracing configuration conflict can cause issues like:
* Incomplete Infinite Tracing metrics due to not taking standard trace sampling into account.
* Discrepancies for metrics like span count, service count, durations, and error count.
* Confusing search results. For example, for standard tracing spans that send headers to Infinite Tracing-instrumented services, those spans may show in the trace list but not in the trace waterfall view.
-* Missing traces for monitored browser apps and mobile apps. Because Infinite Tracing isn't yet available for mobile or , spans from these services won't show up in the trace waterfall when they make requests to Infinite Tracing-enabled services.
+* Missing traces for monitored browser apps and mobile apps. Because Infinite Tracing isn't yet available for or , spans from these services won't show up in the trace waterfall when they make requests to Infinite Tracing-enabled services.
+
For traces with a configuration conflict, we'll display only the Infinite Tracing data in the UI because that data is of higher quality. (All tracing data is queryable via NRQL.)
diff --git a/src/content/docs/errors-inbox/errors-inbox.mdx b/src/content/docs/errors-inbox/errors-inbox.mdx
index a5f49c3dcf5..976b6d5bfac 100644
--- a/src/content/docs/errors-inbox/errors-inbox.mdx
+++ b/src/content/docs/errors-inbox/errors-inbox.mdx
@@ -53,7 +53,7 @@ Errors inbox provides a unified error tracking experience to detect and triage e
* Proactive notifications with detailed error information in Slack.
* Error profiles to show similarities between error events and surface the root cause by analyzing attributes.
* Analyze errors in context of the full stack and resolve errors with precision.
-* Errors for APM, , mobile, and AWS Lambda functions are all captured in the same inbox.
+* Errors for , , , and AWS Lambda functions are all captured in the same inbox.
Ready to get started? See our docs about [creating your first workload](/docs/errors-inbox/getting-started).
@@ -200,7 +200,7 @@ You can set one of three statuses, and filter your inbox by status.
### Expected errors [#expected]
-Errors inbox enables you to filter out expected errors for entities. You can [mark errors as expected](/docs/apm/agents/manage-apm-agents/agent-data/manage-errors-apm-collect-ignore-or-mark-expected#expected), and filter them out of your inbox to remove noise.
+Errors inbox enables you to filter out expected errors for APM entities. You can [mark errors as expected](/docs/apm/agents/manage-apm-agents/agent-data/manage-errors-apm-collect-ignore-or-mark-expected#expected), and filter them out of your inbox to remove noise.
* **error.expected != true**: This is the default. It hides all error groups that have only expected errors and it marks error groups that have a mix of expected and unexpected errors with the "Contains expected" tag.
* **error.expected = true**: This filter will show error groups where some or all errors in the group are expected. This can be useful for identifying which errors are marked as expected.
diff --git a/src/content/docs/licenses/product-or-service-licenses/new-relic-mobile/android-sdk-new-relic-mobile-licenses.mdx b/src/content/docs/licenses/product-or-service-licenses/new-relic-mobile/android-sdk-new-relic-mobile-licenses.mdx
index 05bda4e29a8..4b76a04eaab 100644
--- a/src/content/docs/licenses/product-or-service-licenses/new-relic-mobile/android-sdk-new-relic-mobile-licenses.mdx
+++ b/src/content/docs/licenses/product-or-service-licenses/new-relic-mobile/android-sdk-new-relic-mobile-licenses.mdx
@@ -12,7 +12,7 @@ redirects:
freshnessValidatedDate: never
---
-We love open-source software, and use the following in the Android SDK for mobile monitoring. Thank you, open-source community, for making these fine tools! Some of these are listed under multiple software licenses, and in that case we have listed the license we've chosen to use.
+We love open-source software, and use the following in the Android SDK for . Thank you, open-source community, for making these fine tools! Some of these are listed under multiple software licenses, and in that case we have listed the license we've chosen to use.
diff --git a/src/content/docs/licenses/product-or-service-licenses/new-relic-mobile/ios-sdk-new-relic-mobile-licenses.mdx b/src/content/docs/licenses/product-or-service-licenses/new-relic-mobile/ios-sdk-new-relic-mobile-licenses.mdx
index c1e2de9857c..a7e4f66cc68 100644
--- a/src/content/docs/licenses/product-or-service-licenses/new-relic-mobile/ios-sdk-new-relic-mobile-licenses.mdx
+++ b/src/content/docs/licenses/product-or-service-licenses/new-relic-mobile/ios-sdk-new-relic-mobile-licenses.mdx
@@ -14,7 +14,7 @@ redirects:
freshnessValidatedDate: never
---
-We love open-source software, and use the following in the iOS SDK for mobile monitoring. Thank you, open-source community, for making these fine tools! Some of these are listed under multiple software licenses, and in that case we have listed the license we've chosen to use.
+We love open-source software, and use the following in the iOS SDK for . Thank you, open-source community, for making these fine tools! Some of these are listed under multiple software licenses, and in that case we have listed the license we've chosen to use.
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/crash-analysis-group-filter-your-crashes.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/crash-analysis-group-filter-your-crashes.mdx
index be3cc5232d1..38b4f886b14 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/crash-analysis-group-filter-your-crashes.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/crash-analysis-group-filter-your-crashes.mdx
@@ -180,7 +180,7 @@ Resolved crashes include a banner identifying who resolved the crash and when. B
id="event-trail"
title="Crash event trail: See all the events leading up to a crash."
>
- The mobile monitoring crash event trail shows you the events leading up to a crash of a mobile app. These can be events monitored by default, or custom events you've created. For more information, see [Crash event trail](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail).
+ The crash event trail shows you the events leading up to a crash of a mobile app. These can be events monitored by default, or custom events you've created. For more information, see [Crash event trail](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail).
.
## Create custom attributes and events
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/investigate-mobile-app-crash-report.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/investigate-mobile-app-crash-report.mdx
index 283c15ff1ef..04657afa10e 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/investigate-mobile-app-crash-report.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/investigate-mobile-app-crash-report.mdx
@@ -16,7 +16,7 @@ freshnessValidatedDate: never
import mobileCrashEventTrail from 'images/mobile_screenshot-full_crash-event-trail.webp'
-Mobile monitoring's **Crash report** provides a summary and in-depth details on crashes, including:
+The **Crash report** of provides a summary and in-depth details on crashes, including:
* Device and OS breakdown
* App version
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail.mdx
index 07285fe45ca..84bf943d04d 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail.mdx
@@ -13,7 +13,7 @@ freshnessValidatedDate: never
import mobileCrashEventTrail from 'images/mobile_screenshot-full_crash-event-trail.webp'
-The mobile monitoring **crash event trail** shows you the events leading up to a crash of a mobile app, based on your subscription level's [data retention policy](/docs/accounts-partnerships/accounts/account-billing-usage/data-retention). These can be events New Relic monitors by default, or custom events. This document explains [what the crash event trail is](#what-is) and [how to use it](#use).
+The **crash event trail** shows you the events leading up to a crash of a mobile app, based on your subscription level's [data retention policy](/docs/accounts-partnerships/accounts/account-billing-usage/data-retention). These can be events New Relic monitors by default, or custom events. This document explains [what the crash event trail is](#what-is) and [how to use it](#use).
## View events before mobile app crashes [#what-is]
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/alerts-page-mobile-apps.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/alerts-page-mobile-apps.mdx
index 1ba8ba9ed98..19ff1a736fc 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/alerts-page-mobile-apps.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/alerts-page-mobile-apps.mdx
@@ -13,7 +13,7 @@ redirects:
freshnessValidatedDate: never
---
-When the [alert conditions](/docs/mobile-apps/alert-settings) you set for your mobile app's error rates and response times cross a threshold for an extended period, the mobile monitoring agent will create a Warning (yellow) or Critical (red) problem event. If a Critical (red) event has been open for several minutes, mobile will send an alert notification to users who have been set up to receive alert notifications. It will also send a notification when all Critical events close.
+When the [alert conditions](/docs/mobile-apps/alert-settings) you set for your mobile app's error rates and response times cross a threshold for an extended period, the agent will create a Warning (yellow) or Critical (red) problem event. If a Critical (red) event has been open for several minutes, mobile will send an alert notification to users who have been set up to receive alert notifications. It will also send a notification when all Critical events close.
To view the Alerts page: Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > (select an app) > App > Alerts**.
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/devices-page.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/devices-page.mdx
index 2839c96feff..9e28e12fb94 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/devices-page.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/devices-page.mdx
@@ -17,7 +17,7 @@ import mobileDevicesSummary from 'images/mobile_screenshot-full_devices-summary.
import mobileDeviceDrilldown from 'images/mobile_screenshot-full_device-drilldown.webp'
-The Devices page for mobile monitoring provides performance details about the top devices using your mobile application, such as iPad, iPhone, iPod Touch, Android Tablet, etc. Charts compare the devices by:
+The Devices page for provides performance details about the top devices using your mobile application, such as iPad, iPhone, iPod Touch, Android Tablet, etc. Charts compare the devices by:
* Interaction time
* HTTP request time
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/interactions-page.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/interactions-page.mdx
index 287fb81a8a4..1243bd77317 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/interactions-page.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/interactions-page.mdx
@@ -13,7 +13,7 @@ redirects:
freshnessValidatedDate: never
---
-Mobile monitoring provides an engine that instruments your application code for Android and iOS apps and monitors your code as it services your user interactions. This is useful for analyzing time-consuming user activities. After you set up the SDK API for your Android or iOS app, you can view detailed information from the Interactions page.
+Our provides an engine that instruments your application code for Android and iOS apps and monitors your code as it services your user interactions. This is useful for analyzing time-consuming user activities. After you set up the SDK API for your Android or iOS app, you can view detailed information from the Interactions page.
## Instrumentation
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-apps-index.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-apps-index.mdx
index 7e8b9067e7d..b430cfb900c 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-apps-index.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-apps-index.mdx
@@ -14,7 +14,7 @@ redirects:
freshnessValidatedDate: never
---
-New Relic's mobile monitoring UI includes a mobile app index that shows a list of your monitored apps and important summary information about them.
+New Relic's UI includes a mobile app index that shows a list of your monitored apps and important summary information about them.
## View your list of mobile apps [#menu]
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-apps-summary-page.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-apps-summary-page.mdx
index 8b8122003cb..ace4138d163 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-apps-summary-page.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-apps-summary-page.mdx
@@ -226,7 +226,7 @@ See the [Alert coverage gaps and condition recommendations](/docs/alerts-applied
Follow these steps to add recommended alert conditions:
-1. Open the mobile monitoring **Summary** page.
+1. Open the **Summary** page.
2. Click **Add recommended conditions**.
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-monitoring-email-notifications.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-monitoring-email-notifications.mdx
index a0287c5454a..420b285f6c8 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-monitoring-email-notifications.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-monitoring-email-notifications.mdx
@@ -11,7 +11,7 @@ redirects:
freshnessValidatedDate: never
---
-New Relic's mobile monitoring provides several emailed reports, including:
+New Relic's provides several emailed reports, including:
* [Release notifications](#version-trends) (aka version trend emails)
* [Crash report emails](#crash-reports)
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/os-versions-page.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/os-versions-page.mdx
index 86108f57925..85f268766c2 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/os-versions-page.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/os-versions-page.mdx
@@ -15,7 +15,7 @@ freshnessValidatedDate: never
import mobileOsVersionsSummary from 'images/mobile_screenshot-full_os-versions-summary.webp'
-The OS versions page for mobile monitoring provides performance details about the top operating system versions hosting your mobile application, such as iOS and Android. Charts compare the OS versions by:
+The OS versions page for provides performance details about the top operating system versions hosting your mobile application, such as iOS and Android. Charts compare the OS versions by:
* HTTP request time
* Network failures
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/version-trends-compare-user-adoption-metrics-performance.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/version-trends-compare-user-adoption-metrics-performance.mdx
index 3b434ac42a2..0f5bb1767fa 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/version-trends-compare-user-adoption-metrics-performance.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/version-trends-compare-user-adoption-metrics-performance.mdx
@@ -11,7 +11,7 @@ redirects:
- /docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/version-trends-compare-usage-metrics-performance
freshnessValidatedDate: never
---
-The Release versions page for mobile monitoring provides comprehensive overview of their mobile application's performance across different versions. It offers real-time insights into crash rates, user adoption, and an overall performance score, enabling you to make informed decisions to enhance your app's stability and user experience.
+The Release versions page for provides comprehensive overview of their mobile application's performance across different versions. It offers real-time insights into crash rates, user adoption, and an overall performance score, enabling you to make informed decisions to enhance your app's stability and user experience.
## Requirements
To collect release version information for your mobile app, make sure your agent version is:
* New Relic mobile agent for [Android agent v6.5.0](/docs/release-notes/mobile-release-notes/android-release-notes/) or higher
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/analyze-network-requests-using-mobilerequest-event-data.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/analyze-network-requests-using-mobilerequest-event-data.mdx
index b23738937e0..4678e5d86d8 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/analyze-network-requests-using-mobilerequest-event-data.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/analyze-network-requests-using-mobilerequest-event-data.mdx
@@ -11,7 +11,7 @@ redirects:
freshnessValidatedDate: never
---
-Monitoring HTTP and network requests gives you insight into how your app is performing and provides data that can help you improve your app. To find HTTP and network requests and errors, you can view them in the [mobile monitoring UI](#view-mobile) or query [`MobileRequest` and `MobileRequestError` events](#query-insights) with NRQL.
+Monitoring HTTP and network requests gives you insight into how your app is performing and provides data that can help you improve your app. To find HTTP and network requests and errors, you can view them in the [ UI](#view-mobile) or query [`MobileRequest` and `MobileRequestError` events](#query-insights) with NRQL.
## Enable MobileRequest for earlier versions of iOS and Android [#enable_mobilerequest]
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/carriers-page.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/carriers-page.mdx
index c2f514c28df..6e586da90f3 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/carriers-page.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/carriers-page.mdx
@@ -15,7 +15,7 @@ freshnessValidatedDate: never
import mobileCarriersSummary from 'images/mobile_screenshot-full_carriers-summary.webp'
-The Carriers page for mobile monitoring includes charts that show your users' wireless carriers and their response time impact, error rate, and active sessions for the selected time period. Wifi is included as a carrier. From here you can sort and drill down into detailed information about specific carriers.
+The Carriers page for includes charts that show your users' wireless carriers and their response time impact, error rate, and active sessions for the selected time period. Wifi is included as a carrier. From here you can sort and drill down into detailed information about specific carriers.
## Viewing the Carriers page [#procedures]
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/connection-types-page.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/connection-types-page.mdx
index f97cdbb7428..279d19a99d6 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/connection-types-page.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/connection-types-page.mdx
@@ -13,7 +13,14 @@ freshnessValidatedDate: never
import mobileConnectionTypesSummary from 'images/mobile_screenshot-full_connection-types-summary.webp'
-![]() includes charts that show your users' wireless network connection technologies and their response time impact, error rate, and active traffic for the selected time period. Data is grouped by technology generation: 2G, 3G, etc. Wifi and Unknown are also included in the connection types breakdown. From here you can drill down into specific wireless technologies like GPRS, HSDPA, and LTE.
+
+To view your users' mobile wireless connection types:
+
+1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > (select an app) > Network > Connection types**.
+
+  All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > (select an app) > Network > Connection types**: Use this page to view, sort, or drill down into detailed information about your users' mobile network connection type by response time impact, network failures, and active traffic.
-The **Connection Types** page for mobile monitoring includes charts that show your users' wireless network connection technologies and their response time impact, error rate, and active traffic for the selected time period. Data is grouped by technology generation: 2G, 3G, etc. Wifi and Unknown are also included in the connection types breakdown. From here you can drill down into specific wireless technologies like GPRS, HSDPA, and LTE.
-
-To view your users' mobile wireless connection types:
-1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > (select an app) > Network > Connection types**.
2. To change the information that appears (including response time, active devices, or network errors), select your choice from the **Sort by** menu.
3. To select the mobile app versions or time period, use the [**Versions**](/docs/mobile-apps/versions) menu and [time picker](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard/#dash-time-picker) below the New Relic menu bar.
4. To view details for a specific connection type, select its name.
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-errors-network-failure-analysis.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-errors-network-failure-analysis.mdx
index 5dcbcae63ff..5b52c3043c3 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-errors-network-failure-analysis.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-errors-network-failure-analysis.mdx
@@ -18,7 +18,7 @@ redirects:
freshnessValidatedDate: never
---
-Mobile monitoring's **HTTP errors** page helps you to better understand HTTP errors and network failures associated with your mobile app, to connect errors to services that are causing issues, and to share actionable data with your team.
+The **HTTP errors** page of helps you to better understand HTTP errors and network failures associated with your mobile app, to connect errors to services that are causing issues, and to share actionable data with your team.
To access the **HTTP errors** page go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > (select an app) > Errors > HTTP Errors**.
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-requests-page.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-requests-page.mdx
index 87d89bb956b..5159e54df82 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-requests-page.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-requests-page.mdx
@@ -16,7 +16,7 @@ redirects:
freshnessValidatedDate: never
---
-[Mobile monitoring](/docs/mobile-monitoring) has an **HTTP requests** UI page that helps you better understand HTTP requests associated with your mobile app and how those network calls are affecting performance.
+The **HTTP requests** UI page of [](/docs/mobile-monitoring) helps you better understand HTTP requests associated with your mobile app and how those network calls are affecting performance.
This document describes the Enterprise-level **HTTP requests** page. Non-Enterprise accounts will see the [legacy HTTP requests page](#non-enterprise-http-requests).
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/mobile-http-error-profiles-find-error-causes.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/mobile-http-error-profiles-find-error-causes.mdx
index a556ef3c299..ff71af2be03 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/mobile-http-error-profiles-find-error-causes.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/mobile-http-error-profiles-find-error-causes.mdx
@@ -18,14 +18,14 @@ On the [HTTP errors UI page](/docs/mobile-monitoring/mobile-monitoring-ui/networ
## View HTTP error profiles [#view]
-To view mobile monitoring error profiles:
+To view error profiles:
1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile >** (select an app) **> More views > HTTP errors**.
-2. To see HTTP error profile details: At the bottom of the HTTP errors UI page, select the **HTTP error profiles** tab above the table, then select an HTTP error profile to expand it.
+2. If you want to see HTTP error profile details, go at the bottom of the HTTP errors UI page. Then, select the **HTTP error profiles** tab above the table and select an HTTP error profile to expand it.
## What are HTTP error profiles? [#about]
-An **HTTP error profile** is a potentially meaningful correlation found between your HTTP error values (MobileRequestError events) when compared to successful HTTP requests (MobileRequest events). These correlations help you investigate the causes and contributing factors behind your HTTP errors.
+An **HTTP error profile** is a potentially meaningful correlation found between your HTTP error values (`MobileRequestError` events) when compared to successful HTTP requests (`MobileRequest` events). These correlations help you investigate the causes and contributing factors behind your HTTP errors.
The screenshot below shows an example of an HTTP error profile.
@@ -67,7 +67,7 @@ To help you better understand your own HTTP error profile data, this is an expla
Column explanations:
* The first column is the **Errors** column. It shows the attribute values with the most deviation when compared to successful HTTP requests. Less significant attribute values are aggregated in the **Other** category. In this example, the OS versions 6.0, 5.1, 7.0, and 7.1.1 make up 100% of the HTTP errors for Chrome users.
-* The **Errors** column shows what percentage of MobileRequestError events have the attribute values from the first column. This column adds up to 100%, representing all HTTP errors from the chosen [time range and filter set](#filter). In this example, a large percentage of HTTP errors are coming from Galaxy OS version 7.1.1. If we wanted to investigate this further, we could filter to only show OS version 7.1.1 data.
-* The **Requests** column shows what percentage of MobileRequest events (successful HTTP requests) have the attribute values from the first column. In this example, less than 14% of the requests are made by users on OS version 6, but 24% of HTTP errors are generated by users with that version.
+* The **Errors** column shows what percentage of `MobileRequestError` events have the attribute values from the first column. This column adds up to 100%, representing all HTTP errors from the chosen [time range and filter set](#filter). In this example, a large percentage of HTTP errors are coming from Galaxy OS version 7.1.1. If we wanted to investigate this further, we could filter to only show OS version 7.1.1 data.
+* The **Requests** column shows what percentage of `MobileRequest` events (successful HTTP requests) have the attribute values from the first column. In this example, less than 14% of the requests are made by users on OS version 6, but 24% of HTTP errors are generated by users with that version.
* The **Difference** column shows you the difference in percentage between the **Errors** column and the **Requests** column. In this example, the
11% indicates that attribute is 11 percentage points higher for HTTP error events than for requests.
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/usage-pages/monthly-uniques-report.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/usage-pages/monthly-uniques-report.mdx
index 45b94236a34..8f6ed191f63 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/usage-pages/monthly-uniques-report.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/usage-pages/monthly-uniques-report.mdx
@@ -14,7 +14,7 @@ freshnessValidatedDate: never
import mobileMonthlyUniques from 'images/mobile_screenshot-full_monthly-uniques.webp'
-Mobile monitoring includes a monthly report with a bar chart tracking the number of devices running your app for each month over the last year. To view the report: Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > (select an app) > Usage > Monthly uniques**.
+The capability includes a monthly report with a bar chart tracking the number of devices running your app for each month over the last year. To view the report: Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > (select an app) > Usage > Monthly uniques**.
## Monthly uniques report details [#details]
diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/usage-pages/versions-analysis.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/usage-pages/versions-analysis.mdx
index 776de0d4ea5..f85cd17ceb9 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/usage-pages/versions-analysis.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/usage-pages/versions-analysis.mdx
@@ -16,7 +16,7 @@ import mobileVersionsOverview from 'images/mobile_screenshot-full_versions-overv
import mobileVersionDetails from 'images/mobile_screenshot-full_version-details.webp'
-Mobile monitoring includes a comparative analysis of adoption and performance between versions of your application, including top versions by:
+The capability includes a comparative analysis of adoption and performance between versions of your application, including top versions by:
* Interaction time
* Active sessions
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile-android/get-started/new-relic-android-and-dt.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile-android/get-started/new-relic-android-and-dt.mdx
index 7f00118f682..de807827cd6 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile-android/get-started/new-relic-android-and-dt.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile-android/get-started/new-relic-android-and-dt.mdx
@@ -8,7 +8,7 @@ freshnessValidatedDate: never
import mobileIcon from 'images/mobile_icon_icon.webp'
-New Relic Android mobile monitoring agents support distributed tracing. This lets you see how your mobile app activity connects to related services.
+New Relic Android agents support distributed tracing. This lets you see how your mobile app activity connects to related services.
Watch this short video (approx. 2:15 minutes) to learn how to:
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile-android/get-started/new-relic-android-compatibility-requirements.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile-android/get-started/new-relic-android-compatibility-requirements.mdx
index d6b8c7dc775..716914ae68b 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile-android/get-started/new-relic-android-compatibility-requirements.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile-android/get-started/new-relic-android-compatibility-requirements.mdx
@@ -10,7 +10,7 @@ metaDescription: 'Compatible build systems, OS versions, and more for the Androi
freshnessValidatedDate: never
---
-Mobile monitoring is compliant with standard application stores, including Google Play Store, Amazon Appstore, and others. Before you [install and configure the mobile agent](/docs/mobile-monitoring/new-relic-mobile-android/install-configure) with your Android applications, follow these guidelines for compatibility and other requirements.
+The capability is compliant with standard application stores, including Google Play Store, Amazon Appstore, and others. Before you [install and configure the mobile agent](/docs/mobile-monitoring/new-relic-mobile-android/install-configure) with your Android applications, follow these guidelines for compatibility and other requirements.
## Foreground monitoring [#foreground]
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/android-agent-crash-reporting.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/android-agent-crash-reporting.mdx
index 1e1eeffc76c..82ef8807cf5 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/android-agent-crash-reporting.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/android-agent-crash-reporting.mdx
@@ -10,7 +10,7 @@ redirects:
freshnessValidatedDate: never
---
-By default, mobile monitoring enables crash reporting for your mobile applications to help track and diagnose crashes. When an Android application crashes, the agent uploads a crash report to the New Relic [collector](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#collector). The crash details will then be processed and de-obfuscated automatically if you are using ProGuard or DexGuard.
+By default, enables crash reporting for your mobile applications to help track and diagnose crashes. When an Android application crashes, the agent uploads a crash report to the New Relic [collector](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#collector). The crash details will then be processed and de-obfuscated automatically if you are using ProGuard or DexGuard.
You can view detailed information about crashes in the [**Crash analysis** UI](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/crash-analysis-group-filter-your-crashes), or receive crash notifications by [email](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/receive-crash-notifications-email). You can also [integrate with ticketing systems](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/file-tickets-mobile-app-crashes) for further investigation.
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/configure-proguard-or-dexguard-android-apps.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/configure-proguard-or-dexguard-android-apps.mdx
index c44fbb76862..ba483b762a1 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/configure-proguard-or-dexguard-android-apps.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/configure-proguard-or-dexguard-android-apps.mdx
@@ -44,7 +44,7 @@ To add support for [ProGuard](http://proguard.sourceforge.net/manual/usage.html)
```
3. Clean and rebuild your project.
4. Run your app in an emulator or device to start seeing data on your mobile app's [**Overview** page](/docs/mobile-apps/mobile-apps-dashboard).
-5. Optional: Use the mobile monitoring **Settings** page to [customize your mobile app](/docs/mobile-apps/customizing-your-mobile-app-settings).
+5. Optional: Use the **Settings** page to [customize your mobile app](/docs/mobile-apps/customizing-your-mobile-app-settings).
If no data appears, review your `logcat` output for errors.
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/install-android-agent-gradle.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/install-android-agent-gradle.mdx
index 5001c5fe17b..88c5116805c 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/install-android-agent-gradle.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/install-android-agent-gradle.mdx
@@ -106,7 +106,7 @@ These procedures appear in our guided install. Keep in mind that even if you're
import com.newrelic.agent.android.NewRelic;
```
- We don't support starting the mobile monitoring agent in other classes, as that can cause unexpected or unstable behavior.
+ We don't support starting the agent in other classes, as that can cause unexpected or unstable behavior.
4. After you've imported the `NewRelic` class, you need to add an additional snippet to the `onCreate()` method, which includes your app token, which is generated in the guided install. The snippet looks like this:
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/upgrade-new-relic-mobiles-android-sdk.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/upgrade-new-relic-mobiles-android-sdk.mdx
index 573dac2b91d..9ebeaa561f3 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/upgrade-new-relic-mobiles-android-sdk.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/upgrade-new-relic-mobiles-android-sdk.mdx
@@ -65,7 +65,7 @@ If you have previously installed version 1 of the Android SDK, follow these [one
**Stop using `nrandroid-ant`.**
- Mobile monitoring no longer requires the custom Ant wrapper script for Android applications. Once you upgrade, simply use your standard build tools.
+ The capability no longer requires the custom Ant wrapper script for Android applications. Once you upgrade, simply use your standard build tools.
If you modified an existing Maven configuration to invoke the mobile build steps, remove those modifications, and use the revised build instructions.
|
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/no-data-appears-android.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/no-data-appears-android.mdx
index 47d0698cd14..f9e9b73b725 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/no-data-appears-android.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile-android/troubleshoot/no-data-appears-android.mdx
@@ -33,6 +33,6 @@ If no data appears after you wait at least five minutes, use [New Relic Diagnost
```
* Generate a few minutes of activity in your app.
* Examine your device log and your application build logs for issues.
-5. Confirm the device can reach the mobile monitoring endpoints listed in the [Networks](/docs/using-new-relic/cross-product-functions/install-configure/networks) doc.
+5. Confirm the device can reach the endpoints listed in the [Networks](/docs/using-new-relic/cross-product-functions/install-configure/networks) doc.
If you need additional help, get support at [support.newrelic.com](https://support.newrelic.com).
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring.mdx
index 91065cb4dd4..eaa1ffe5e40 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring.mdx
@@ -61,7 +61,7 @@ import mobileCrashAnalysis from 'images/mobile_screenshot-full_crash-analysis.we
import mobileNextSteps from 'images/mobile_diagram_next-steps.webp'
-New Relic's mobile monitoring capabilities provide deeper visibility into the performance and crash troubleshooting of your [Android](/docs/mobile-monitoring/new-relic-mobile-android/get-started/introduction-new-relic-mobile-android), [iOS](/docs/mobile-monitoring/new-relic-mobile-ios/get-started/introduction-new-relic-mobile-ios), or hybrid mobile applications. You can use mobile monitoring to improve your app's user experience or examine HTTP and network performance to collaborate more effectively with your backend teams.
+New Relic's capabilities provide deeper visibility into the performance and crash troubleshooting of your [Android](/docs/mobile-monitoring/new-relic-mobile-android/get-started/introduction-new-relic-mobile-android), [iOS](/docs/mobile-monitoring/new-relic-mobile-ios/get-started/introduction-new-relic-mobile-ios), or hybrid mobile applications. You can use mobile monitoring to improve your app's user experience or examine HTTP and network performance to collaborate more effectively with your backend teams.
Once you follow our easy install flow, you'll be able to further configure mobile monitoring to suit your mobile environment.
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/mobile-agents-eol-policy.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/mobile-agents-eol-policy.mdx
index cc49b04d615..62378c1b9bc 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/mobile-agents-eol-policy.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/mobile-agents-eol-policy.mdx
@@ -4,7 +4,7 @@ metaDescription: Policies, start and end dates for support of New Relic mobile m
freshnessValidatedDate: never
---
-The following are the specific policies and dates for support of our mobile monitoring agents: iOS (previously XCFramework), Android, and React Native. See our documentation about [general EOL policies](/docs/licenses/end-of-life/notification-changes-new-relic-saas-features-distributed-software/) for information about New Relic's overall end-of-life policy.
+The following are the specific policies and dates for support of our agents: iOS (previously XCFramework), Android, and React Native. See our documentation about [general EOL policies](/docs/licenses/end-of-life/notification-changes-new-relic-saas-features-distributed-software/) for information about New Relic's overall end-of-life policy.
## iOS [#ios-eol]
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/mobile-monitoring-alert-information.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/mobile-monitoring-alert-information.mdx
index 0438511c4ed..783827209a3 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/mobile-monitoring-alert-information.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/mobile-monitoring-alert-information.mdx
@@ -19,7 +19,7 @@ freshnessValidatedDate: never
Well-defined alerts help notify individuals or teams about changes in their systems. You can use any of our [alerts and applied intelligence](/docs/alerts-applied-intelligence) capabilities across all the entities you monitor with New Relic.
-For example, you can use [alerts](/docs/alerts-applied-intelligence/new-relic-alerts/get-started/introduction-alerts) to manage alert policies and conditions that focus on the metrics for mobile apps you monitor with New Relic. After you [define alert conditions](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions) for your mobile apps, you can view that information in the alerts UI or in other UI experiences, like the mobile monitoring UI.
+For example, you can use [alerts](/docs/alerts-applied-intelligence/new-relic-alerts/get-started/introduction-alerts) to manage alert policies and conditions that focus on the metrics for mobile apps you monitor with New Relic. After you [define alert conditions](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions) for your mobile apps, you can view that information in the alerts UI or in other UI experiences, like the UI.
## Mobile alert conditions [#conditions]
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/security-mobile-apps.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/security-mobile-apps.mdx
index 04e6d0a877d..4acc659de82 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/security-mobile-apps.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/get-started/security-mobile-apps.mdx
@@ -14,7 +14,7 @@ To protect your mobile application's security and your users' data privacy, New
## Data collection [#collection]
-When you install New Relic, our mobile monitoring capabilities become part of your iOS or Android app. These capabilities live within your application's "sandbox," so they cannot access anything other than performance data from your mobile app. We do not collect performance data about the device itself, such as battery level.
+When you install New Relic, our capabilities become part of your iOS or Android app. These capabilities live within your application's "sandbox," so they cannot access anything other than performance data from your mobile app. We do not collect performance data about the device itself, such as battery level.
Our mobile SDK agent collects and sends specific data to the New Relic [collector](/docs/using-new-relic/welcome-new-relic/getting-started/glossary#collector), including:
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/maintenance/configure-settings-for-mobile-monitoring.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/maintenance/configure-settings-for-mobile-monitoring.mdx
index c3e1e31587a..cf28d9c9fbd 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/maintenance/configure-settings-for-mobile-monitoring.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/maintenance/configure-settings-for-mobile-monitoring.mdx
@@ -16,7 +16,7 @@ redirects:
freshnessValidatedDate: never
---
-In the New Relic mobile monitoring UI, under **Settings**, there are options for changing your New Relic-monitored mobile app, editing alert conditions, and editing other settings. To authenticate your app's data, [view your application token](/docs/mobile-monitoring/new-relic-mobile/maintenance/configure-settings-for-mobile-monitoring/#application-token).
+In the New Relic UI, under **Settings**, there are options for changing your New Relic-monitored mobile app, editing alert conditions, and editing other settings. To authenticate your app's data, [view your application token](/docs/mobile-monitoring/new-relic-mobile/maintenance/configure-settings-for-mobile-monitoring/#application-token).
Access to this feature depends on user permissions.
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/mobile-sdk-api-guide.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/mobile-sdk-api-guide.mdx
index 0fd514d1d90..428b9334824 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/mobile-sdk-api-guide.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/mobile-sdk-api-guide.mdx
@@ -14,7 +14,7 @@ freshnessValidatedDate: never
Use the New Relic mobile SDK API calls to customize and extend the data your mobile app reports to New Relic.
-While our mobile monitoring solution offers powerful out-of-the-box data collection, you may need to customize and extend the data your mobile app reports to New Relic. For example, you can use the public SDK API calls to:
+While our solution offers powerful out-of-the-box data collection, you may need to customize and extend the data your mobile app reports to New Relic. For example, you can use the public SDK API calls to:
* Start and stop interaction traces from events in your mobile app
* Record custom metrics
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-custom-events.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-custom-events.mdx
index 679aab9d1fe..12152bb8714 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-custom-events.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-custom-events.mdx
@@ -70,7 +70,7 @@ NewRelic.recordCustomEvent(string $eventType, [string $eventName,] map event.
Creates and records a [custom event](/docs/insights/new-relic-insights/adding-querying-data/custom-attributes-events-new-relic-mobile#What-are-events-in-New-Relic-Mobile), for use in NRQL. The event includes a list of attributes, specified as a map. Unlike using [`setAttribute`](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/create-attribute/), adding attributes to a custom event adds them only to that event; they are not session attributes.
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-custom-metrics.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-custom-metrics.mdx
index 24f65575aa0..5cb262ce958 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-custom-metrics.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-custom-metrics.mdx
@@ -295,7 +295,7 @@ NewRelic.recordMetric(withName: String!, category: String!, value: NSNumber!)
With this method, you can record arbitrary [custom metrics](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#custom-metric) to give more detail about app activity that is not tracked by New Relic automatically. The call accepts several sets of parameters for optional levels of detail.
-This method will record a metric of the form `Custom/[Category]/[Name]`, with a count of 1 and a total value equal to the value passed in. Multiple calls will aggregate the count and value according to standard [metric aggregation rules for mobile monitoring](/docs/mobile-monitoring/new-relic-mobile/getting-started/mobile-data-retention).
+This method will record a metric of the form `Custom/[Category]/[Name]`, with a count of 1 and a total value equal to the value passed in. Multiple calls will aggregate the count and value according to standard [metric aggregation rules for ](/docs/mobile-monitoring/new-relic-mobile/getting-started/mobile-data-retention).
To get the most out of your metrics, follow these guidelines to create clear, concise metric names:
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-errors.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-errors.mdx
index 0f54d328e17..239c8487c78 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-errors.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-errors.mdx
@@ -51,7 +51,7 @@ NewRelic.recordError(error: $Error, map $eventAttributes);
You can use the `recordError` API call for crash analysis. Review the captured events to help you understand how often your app is throwing errors and under what conditions. In addition to any [custom attributes](/docs/mobile-monitoring/new-relic-mobile/maintenance/add-custom-data-new-relic-mobile) that you added, the events will also have associated [session attributes](/docs/insights/insights-data-sources/default-attributes/mobile-default-attributes-insights).
-This API takes an instance of an error and an optional attribute dictionary, then creates a `recordHandledException` event. You can view event data in the mobile monitoring UI in places like the [**Handled exceptions** page](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/handled-exceptions-analyze-trends-prevent-crashes) and the [**Crash events** trail](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail). You can also query this data with NRQL, and chart it in New Relic dashboards.
+This API takes an instance of an error and an optional attribute dictionary, then creates a `recordHandledException` event. You can view event data in the UI in places like the [**Handled exceptions** page](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/handled-exceptions-analyze-trends-prevent-crashes) and the [**Crash events** trail](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail). You can also query this data with NRQL, and chart it in New Relic dashboards.
## Parameters [#parameters]
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/set-max-event-pool-size.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/set-max-event-pool-size.mdx
index 0f15a157bb9..c8561982b83 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/set-max-event-pool-size.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/set-max-event-pool-size.mdx
@@ -69,7 +69,7 @@ NewRelic.setMaxEventPoolSize(maxSize: Int)
Sets the maximum size of the event pool.
-By default, mobile monitoring collects a maximum of 1,000 events per event harvest cycle, which is 600 seconds long by default.
+By default, collects a maximum of 1,000 events per event harvest cycle, which is 600 seconds long by default.
This method controls the maximum size of the event pool stored in the memory until the next harvest cycle. When the pool size limit is reached, the New Relic Android agent will begin [sampling events](/docs/agents/manage-apm-agents/agent-data/new-relic-events-limits-sampling), discarding some old and some new events, until the pool of events are transmitted with the next harvest cycle. This method lets you override the maximum size of that event pool.
The default value for the event harvest cycle is 600 seconds. See [Set max event buffer time](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/set-max-event-buffer-time) to change the length of the event harvest cycle.
diff --git a/src/content/docs/new-relic-solutions/solve-common-issues/troubleshooting/metric-grouping-issues.mdx b/src/content/docs/new-relic-solutions/solve-common-issues/troubleshooting/metric-grouping-issues.mdx
index e6ba0090c1e..8e911a88ba7 100644
--- a/src/content/docs/new-relic-solutions/solve-common-issues/troubleshooting/metric-grouping-issues.mdx
+++ b/src/content/docs/new-relic-solutions/solve-common-issues/troubleshooting/metric-grouping-issues.mdx
@@ -23,7 +23,7 @@ import solutionsMetricGrouping from 'images/solutions_screenshot-crop_metric-gro
## Problem
-For our , , and mobile monitoring features, there can be cases when an account or application is sending many individual [metric timeslice data points](/docs/data-analysis/metrics/analyze-your-metrics/data-collection-metric-timeslice-event-data#timeslice-data) that could be better managed by grouping them together. We use the term **metric grouping issue** or **MGI** to describe this situation. When this occurs, the agent is sending unnecessarily large amounts of data to New Relic, which reduces the effectiveness of New Relic charts, tables, and reports.
+For our , , and features, there can be cases when an account or application is sending many individual [metric timeslice data points](/docs/data-analysis/metrics/analyze-your-metrics/data-collection-metric-timeslice-event-data#timeslice-data) that could be better managed by grouping them together. We use the term **metric grouping issue** or **MGI** to describe this situation. When this occurs, the agent is sending unnecessarily large amounts of data to New Relic, which reduces the effectiveness of New Relic charts, tables, and reports.
Metric grouping issues occur most commonly with web transactions, especially if the name is based on URLs. They can also happen with other metrics reported by your application. For example:
diff --git a/src/content/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/nrql-query-examples-mobile-monitoring.mdx b/src/content/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/nrql-query-examples-mobile-monitoring.mdx
index 4be3d1183b4..4bb72631a7b 100644
--- a/src/content/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/nrql-query-examples-mobile-monitoring.mdx
+++ b/src/content/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/nrql-query-examples-mobile-monitoring.mdx
@@ -16,7 +16,7 @@ redirects:
freshnessValidatedDate: never
---
-There are several ways to [query your data](/docs/using-new-relic/data/understand-data/query-new-relic-data). This document will show you some example [NRQL](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql) queries from mobile monitoring data. To see descriptions of the mobile-reported events and attributes available, see [Mobile events](/docs/insights/insights-data-sources/default-data/mobile-default-event-attributes-insights).
+There are several ways to [query your data](/docs/using-new-relic/data/understand-data/query-new-relic-data). This document will show you some example [NRQL](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql) queries from data. To see descriptions of the mobile-reported events and attributes available, see [Mobile events](/docs/insights/insights-data-sources/default-data/mobile-default-event-attributes-insights).
## Mobile, MobileSession, and MobileCrash event query examples [#mobile-examples]
diff --git a/src/content/docs/security/security-privacy/data-privacy/data-privacy-new-relic.mdx b/src/content/docs/security/security-privacy/data-privacy/data-privacy-new-relic.mdx
index 0e77ad48be4..1f6ff381ca3 100644
--- a/src/content/docs/security/security-privacy/data-privacy/data-privacy-new-relic.mdx
+++ b/src/content/docs/security/security-privacy/data-privacy/data-privacy-new-relic.mdx
@@ -241,7 +241,7 @@ The following summarizes how individual New Relic products and components ensure
id="mobile-security"
title="Mobile monitoring"
>
- By default, our mobile monitoring service collects two pieces of personal data:
+ By default, our service collects two pieces of personal data:
* The IP address is used to derive high-level geographical data, and then is discarded.
* A device ID is generated by New Relic and is used for billing purposes.
diff --git a/src/content/docs/tutorial-optimize-telemetry/develop-optimize-plan.mdx b/src/content/docs/tutorial-optimize-telemetry/develop-optimize-plan.mdx
index 7b0b6d19941..12aa824f72c 100644
--- a/src/content/docs/tutorial-optimize-telemetry/develop-optimize-plan.mdx
+++ b/src/content/docs/tutorial-optimize-telemetry/develop-optimize-plan.mdx
@@ -78,7 +78,7 @@ We have three examples below of how you can assess your own telemetry ingest and
id="case-study-2"
title="Example 2: Focus on customer experience"
>
- A team responsible for a new user-facing platform with an emphasis on mobile monitoring and browser monitoring is running 50% over budget. They'll need to right-size their ingest, but they're adamant about not sacrificing any **Customer experience** observability.
+ A team responsible for a new user-facing platform with an emphasis on and browser monitoring is running 50% over budget. They'll need to right-size their ingest, but they're adamant about not sacrificing any **Customer experience** observability.
Their estate includes:
* Mobile
| |