fix(data-and-apis): Implement peer review changes.

src/content/docs/data-apis/ingest-apis/metric-api/cardinality-management.mdx

@@ -10,7 +10,7 @@ freshnessValidatedDate: 2024-09-24
   This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy).
 </Callout>
 
-As an administrator at New Relic, one of your tasks is to make sure you don't go beyond your limit of GB Ingested. One tool for tracking your ingest is the Cardinality Management UI. You'll find helpful graphs and tables explaining your ingest so you can take action if you're approaching limits.
+As an administrator at New Relic, one of your tasks is to make sure you don't go beyond your limit of [GB Ingested](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#gb-ingested). One tool for tracking your ingest is the Cardinality Management UI. You'll find helpful graphs and tables explaining your ingest so you can take action if you're approaching limits.
 
 ## Where can you manage cardinality? [#where-manage]
 
@@ -33,12 +33,12 @@ On the opening page of **Cardinality Management**, you can view the **Usage over
 
 This shows following:
 
-* The limit currently at 5 million account cardinality.
+* The limit that is currently at 5 million account cardinality.
 * The current cardinality usage for the account, which is in the 2 to 4 million range. If there's no change in the value, then a new data point isn't reported. This can appear as an empty data point, but it's not data loss. This behavior may change as the feature is finalized.
 
 
 <Callout variant="tip">
-  You can modify this timeseries by changing the timepicker in the top right corner. Also, the timepicker only affects the timeseries and does not affect the **Metrics** table under the timeseries.
+  You can modify this timeseries by changing the time-picker in the top right corner. Also, the time-picker only affects the timeseries and does not affect the **Metrics** table under the timeseries.
 </Callout>
 
 ### Metrics table [#metrics-table]
@@ -79,7 +79,7 @@ In this metric-specific view, you can see the current cardinality usage as two b
 
 ## Usage over time (for metrics) [#usage-over-time-metrics]
 
-Below the bar charts is a chart of a timeseries query showing the metric cardinality usage versus the limit of that metric. Again, you can change the timepicker to view different time periods of this individual metric's cardinality data. 
+Below the bar charts is a chart of a timeseries query showing the metric cardinality usage versus the limit of that metric. Again, you can change the time-picker to view different time periods of this individual metric's cardinality data. 
 
 <Callout variant="tip">
   For any metric that has exceeded its cardinality limit (usually 100,000) New Relic will still attempt to populate information on the metric, but it will be slightly slower since it uses RAW data instead of using aggregated data.