fix(limits): updates to some titles

src/content/docs/data-apis/manage-data/query-limits.mdx

@@ -1,5 +1,5 @@
 ---
-title: Get more detail about hitting or approaching data limits
+title: Get more detail about your data limits
 tags:
   - Ingest data manage data
   - Manage data

src/content/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries.mdx

@@ -1,5 +1,5 @@
 ---
-title: NRQL query limits
+title: NRQL query rate limits
 metaDescription: "An explanation of rate limits for NRQL, the New Relic query language"
 redirects:
   - /docs/insights/use-insights-ui/manage-account-data/rate-limits-insights-requests
@@ -27,31 +27,23 @@ There are a few different NRQL query limits:
 * How long a query can run before erroring and stopping
 * Number of queries you can make in a given time range
 
-Next we'll go into more detail on these limits.  
+Next, we'll go into more detail on these limits.  
 
 ### Limits on inspected data points [#inspected-count-limits]
 
-When you run a NRQL query, it displays the number of data points inspected, as shown below:
+When a NRQL query is run, either due to a customer-initiative query or to a UI page load, that query inspects a certain number of data points in our NRDB data base. 
+
+For example, when you run a NRQL query, it displays the number of data points inspected, as shown below:
 
 <img
   title="New Relic inspected event count"
   alt="New Relic inspected event count"
   src={queriesnrqlEventCountinQueryBuilder}
 />
+<figcaption> In this case, `events` is used in a general sense to refer to all [NRQL-available data points](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql#what-you-can-query) inspected in a query.
+  </figcaption>
 
-In this context, the "events" term is used in a general sense to refer to all [NRQL-available data points](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql#what-you-can-query) that are inspected in a query.
-
-The following features and actions count towards the inspected count limit for your New Relic account, and are impacted when the limit is reached. When the count drops below the limit in the next time period, any restrictions are removed.
-
-These actions count toward the inspected count: 
-
-* Loads of curated views initiated by a user (for example, when you load an <InlinePopover type="apm" /> UI page, the distributed tracing UI, or any UI that returns data about your organization).
-* Custom queries run by a New Relic user, whether in the UI or via API.
-* Widgets on custom dashboards that run queries.
-
-Alert condition evaluation and notifications do **not** count towards the limit but the links to New Relic that are included in an alert notification do.
-
-Inspected count limits vary depending on which [data option](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing#data-prices) you have: 
+The inspected count limit represents how many data points you can query in a specific range of time. These limits differ depending on which [data option](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing#data-prices) you have: 
 
 <CollapserGroup>
   <Collapser
@@ -81,6 +73,21 @@ Limits on inspected data points for our [original data option](/docs/accounts/ac
 </Collapser>
 </CollapserGroup>
 
+### What counts towards inspected count? [#what-counts-inspected-count]
+
+The following actions count towards the inspected count limit for your New Relic account:
+
+* Loads of curated views initiated by a user (for example, when you load an <InlinePopover type="apm" /> UI page, the distributed tracing UI, or any UI that returns data about your organization).
+* Custom queries run by a New Relic user, whether in the UI or via API.
+* Loading widgets that run queries on custom dashboards
+
+Alert condition evaluation and notifications do **not** count towards the limit but the links to New Relic that are included in an alert notification do.
+
+When the inspected count limit is reached, the features mentioned are affected. When the count drops below the limit in the next time period, any restrictions are removed.
+
+
+
+
 ## Query duration limit [#query-duration]
 
 The query duration limit is how long a NRQL query can run before it stops running. This limit depends on your [data option](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing#data-prices): 

src/nav/telemetry-data-platform.yml

@@ -51,9 +51,9 @@ pages:
             path: /docs/data-apis/convert-to-metrics/create-metrics-other-data-types
       - title: Drop data
         path: /docs/data-apis/manage-data/drop-data-using-nerdgraph
-      - title: Understand New Relic data limits
+      - title: New Relic data limits
         path: /docs/data-apis/manage-data/view-system-limits
-      - title: Details on limits
+      - title: Get more detail on limits
         path: /docs/data-apis/manage-data/query-limits
       - title: NrIntegrationError event
         path: /docs/data-apis/manage-data/nrintegrationerror