Merge pull request #7256 from newrelic/Remove-estimatedCost-from-data…

…-dict

fix(estimated cost removal): some more

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/user-count-billing.mdx

@@ -48,7 +48,7 @@ If you're planning on adding billable users or changing your users' user type, y
 
 The count of your unique users is determined by email address. If there are multiple user records in an organization that have the same email address, for billing purposes those user records would count as a single user, and that user's billable user type would be their highest user type assigned during that month.
 
-The cost of your billable users depends on an organization’s [pricing edition](https://newrelic.com/pricing) (Standard, Pro, or Enterprise) or on any custom deals you have with New Relic.
+The cost of your billable users depends on an organization's [pricing edition](https://newrelic.com/pricing) (Standard, Pro, or Enterprise) or on any custom deals you have with New Relic.
 
 When a New Relic organization first starts being billed, their billable user count is pro-rated based on when during the month they started. If an organization cancels their subscription, prorating is also applied for their last month.
 
@@ -101,6 +101,6 @@ For user downgrade rules, see below:
   >
     The following user downgrade rules apply for organizations on the [version of New Relic One pricing without core users](#pricing-versions):
 
-    User type is meant to be a fairly long-term setting based on a user’s expected New Relic duties and responsibilities. For that reason, a full platform user may only be downgraded a maximum of two times in a 12-month period. If a user’s user type has changed more than this allowed number of changes, New Relic can charge that user as a full platform user.
+    User type is meant to be a fairly long-term setting based on a user's expected New Relic duties and responsibilities. For that reason, a full platform user may only be downgraded a maximum of two times in a 12-month period. If a user’s user type has changed more than this allowed number of changes, New Relic can charge that user as a full platform user.
   </Collapser>
 </CollapserGroup>

src/content/docs/alerts-applied-intelligence/applied-intelligence/proactive-detection/proactive-detection-applied-intelligence.mdx

@@ -33,7 +33,7 @@ For more on data limits, see [Data limits](#data-limits).
 
 ## Why it matters
 
-With proactive detection, applied intelligence delivers insights about anomalies in your production system, along with an automatic analysis of the anomaly. It’s enabled automatically, at no additional cost. When an anomaly is detected, you can view it in the applied intelligence anomalies feed, or we'll send notifications directly to your Slack channel or a webhook.
+With proactive detection, applied intelligence delivers insights about anomalies in your production system, along with an automatic analysis of the anomaly. It's enabled automatically, at no additional cost. When an anomaly is detected, you can view it in the applied intelligence anomalies feed, or we'll send notifications directly to your Slack channel or a webhook.
 
 ## How it works
 

src/content/docs/apm/new-relic-apm/getting-started/get-started-logs-context.mdx

@@ -92,7 +92,7 @@ To avoid any surprises, we recommend that you use [NRQL queries](/docs/accounts/
     id="limits-ui"
     title="View data limits and usage in UI"
   >
-    To [review your data limits in the UI](/docs/data-apis/manage-data/view-system-limits): From the [account dropdown](/docs/glossary/glossary/#account-dropdown) in the New Relic UI, click **Manage your data > Limits**. Or, to view your usage and estimated cost to date, click **View your usage**.
+    To [review your data limits in the UI](/docs/data-apis/manage-data/view-system-limits): From the [account dropdown](/docs/glossary/glossary/#account-dropdown) in the New Relic UI, click **Manage your data > Limits**. Or, to view your usage, click **View your usage**.
 
     <img
       title="View data and usage from UI"
@@ -106,11 +106,7 @@ To avoid any surprises, we recommend that you use [NRQL queries](/docs/accounts/
     id="query-estimate"
     title="NRQL query: Estimated cost example"
   >
-    To query your [month-to-date estimated cost of your ingested data](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts/#month-cost), run this NRQL query:
-
-    ```
-    FROM NrMTDConsumption SELECT latest(estimatedCost) WHERE productLine = 'DataPlatform' SINCE this month
-    ```
+    See [cost-related queries](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts#estimated-cost).
   </Collapser>
 
   <Collapser

src/content/docs/data-apis/manage-data/calculate-data-ingest.mdx

@@ -20,8 +20,8 @@ Data ingest rates can vary from one New Relic organization to the next, based on
 
 Here are some tips for extrapolating usage from a New Relic account:
 
-* If you’re just signing up to New Relic, consider creating a test installation with an environment similar to what you’ll need moving forward. Then use the baseline ingest from the trial to extrapolate what your full environment would require. To do this, [create a new free account](https://newrelic.com/signup), and use our [instant observability options](https://newrelic.com/instant-observability/) to get started reporting data. Note that APM, infrastructure monitoring, and logs tend to produce the bulk of most customer's data, but that can vary.
-* If you’re an existing customer, use consumption info from the [data management hub](/docs/data-apis/manage-data/manage-your-data/#where-to-find-the-data-management-hub) or by [querying your data ingest](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) to estimate new or added ingest.
+* If you're just signing up to New Relic, consider creating a test installation with an environment similar to what you'll need moving forward. Then use the baseline ingest from the trial to extrapolate what your full environment would require. To do this, [create a new free account](https://newrelic.com/signup), and use our [instant observability options](https://newrelic.com/instant-observability/) to get started reporting data. Note that APM, infrastructure monitoring, and logs tend to produce the bulk of most customer's data, but that can vary.
+* If you're an existing customer, use consumption info from the [data management hub](/docs/data-apis/manage-data/manage-your-data/#where-to-find-the-data-management-hub) or by [querying your data ingest](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) to estimate new or added ingest.
 
 ## Use the cost estimator spreadsheet [#cost-estimator]
 

src/data-dictionary/events/NrConsumption/estimatedCost.md

@@ -7,4 +7,4 @@ events:
   - NrMTDConsumption
 ---
 
-A cost estimate based on consumption and metric cost. This is an estimate of costs, not your invoice amount.
+A cost estimate based on your usage. This is an estimate, not an actual invoiced amount. To be deprecated in May of 2022.