Merge pull request #997 from wavefrontHQ/mariela-bug-fixes

rebranding + intelligent sampling is turned off by request

pages/doc/trace_data_sampling.md

@@ -74,7 +74,7 @@ You can [monitor](wavefront-internal-metrics.html) your span storage by checking
 
 ## Sampling Policies
 
-If you can’t find traces because Intelligent Sampling discarded them, create a sampling policy to let the Operations for Applications service know that you want to keep specific spans. Sampling policies impact the volume of spans that are ingested and can affect your costs. See your Service Agreement for cost details.
+If you can’t find traces because Intelligent Sampling discarded them, create a sampling policy to let the Operations for Applications service know that you want to keep specific spans. Sampling policies impact the volume of spans that are ingested and can affect your [costs](wavefront_pricing.html#pricing-structure). See your Service Agreement for cost details.
 
 See [Managing Sampling Policies](trace_sampling_policies.html) for details.
 

pages/doc/wavefront_pricing.md

@@ -1,18 +1,18 @@
 ---
-title: Tanzu Observability Pricing
+title: Operations for Applications Pricing
 tags: [administration]
 sidebar: doc_sidebar
 permalink: wavefront_pricing.html
 summary: Summary of pricing information.
 ---
-Tanzu Observability by Wavefront pricing depends on the contract that your company has with VMware, on the types on data you're ingesting, and on some other factors. This page gives an overview of pricing for the different types of data you can send to Wavefront.
+VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront) pricing depends on the contract that your company has with VMware, on the types on data you're ingesting, and on some other factors. This page gives an overview of pricing for the different types of data you can send to Operations for Applications.
 
 {% include note.html content="Some customers have special rates, for example, because they're helping us to test a new feature. The information on this page covers the most common case. "%}
 
 ## Pricing Structure
 
 At the core of the model is the idea of consumption-based pricing. What you pay is based on data throughput, primarily:
-* **Data ingestion**. When the Wavefront service ingests data, the data is consumed and count toward your allocation.
+* **Data ingestion**. When the Operations for Applications service ingests data, the data is consumed and count toward your allocation.
 * **Data scanning**. When you run a query, either as part of an alert or when you look at a dashboard, the backend has to scan the data. Scanning counts toward your allocation.
 
 The model has this basic pricing structure:
@@ -21,7 +21,7 @@ The model has this basic pricing structure:
 
 For spans, the pricing structure is as follows:
 * If [intelligent sampling](trace_data_sampling.html#intelligent-sampling) is turned on, the trace data is counted as derived metrics (1 PPS) or derived histograms (7 PPS).
-* If you turn off intelligent sampling, or if you specify trace sampling policies to specifically include certain traces, each tracing span counts as 22 PPS.
+* If you request our Technical Support team to turn off the intelligent sampling on your service instance, or if you specify [sampling policies](trace_data_sampling.html#sampling-policies) to specifically include certain traces, each tracing span counts as 22 PPS.
 * [Span logs](trace_data_details.html#span-logs) are free.
 
 ![Metrics 1pps and Histograms 7pps are the basis, distributed tracing is 22 PPS if intelligent sampling is turned off](images/pricing_model_1.png)