diff --git a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/application-not-responding.mdx b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/application-not-responding.mdx
index 9a4e5892b1b..825ab7686bb 100644
--- a/src/content/docs/mobile-monitoring/mobile-monitoring-ui/application-not-responding.mdx
+++ b/src/content/docs/mobile-monitoring/mobile-monitoring-ui/application-not-responding.mdx
@@ -25,7 +25,7 @@ In Android mobile apps, [Application Not Responding (ANR) errors](https://develo
 
 ## How ANR errors are reported to New Relic [#anr-reporting]
 
-Our Android agent reports ANR errors as [`MobileApplicationExit`](/attribute-dictionary/?event=MobileApplicationExit) events, which leverage Android’s [`ApplicationExitInfo` API](https://developer.android.com/reference/android/app/ApplicationExitInfo) to monitor and report on the different causes for app termination. The agent reads the `ApplicationExitInfo` API on the next app launch and asynchronously sends `MobileApplicationExit` events to New Relic for each app exit in the history.
+By default, the Android agent reports ANR errors as [`MobileApplicationExit`](/attribute-dictionary/?event=MobileApplicationExit) events, which leverage Android’s [`ApplicationExitInfo` API](https://developer.android.com/reference/android/app/ApplicationExitInfo) to monitor and report on the different causes for app termination. The agent reads the `ApplicationExitInfo` API on the next app launch and asynchronously sends `MobileApplicationExit` events to New Relic for each app exit in the history.
 
 ### Understanding ANR discrepancies between New Relic and Google Play Console [#new-relic-vs-google-play]
 
@@ -118,7 +118,7 @@ ANR profiles shows the distribution of attributes across all your ANR occurrence
 
 <Callout variant="important">
 Server-side configuration always take precedence over local agent configuration.
-For changes to be applied on end-user devices, it may take up to 10 minutes for mobile apps with 100,000 or fewer concurrently active devices. For applications with very large number of concurrently active devices, it may take several hours.
+For mobile apps with <100,000 concurrently active devices, it may take up to 10 minutes to apply changes to end-user devices. For apps with >100,000 active devices, it may take several hours.
 </Callout>
 
 If you need to disable ANR monitoring:
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 2d61104cd65..3d8903db70a 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
@@ -132,7 +132,7 @@ The following setting can be currently modified remotely on the **Application**
  * Application Not Responding (ANR) error tracking (Android only): Enables tracking and reporting of the reasons behind ANR errors. This functionality is enabled by default and requires Android agent 7.4.1 or higher.
     <Callout variant="important">
     Server-side configuration always take precedence over local agent configuration.
-    For changes to be applied on end-user devices, it may take up to 10 minutes for mobile apps with 100,000 or fewer concurrently active devices. For applications with very large number of concurrently active devices, it may take several hours.
+    For mobile apps with <100,000 concurrently active devices, it may take up to 10 minutes to apply changes to end-user devices. For apps with >100,000 active devices, it may take several hours.
     </Callout>
 
 ### Configure from UI [#ui-configuration]