Changed 'for' to 'before'

newrelic · Apr 5, 2022 · e391526 · e391526
1 parent fc479ca
commit e391526
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/...relic-solutions/observability-maturity/operational-efficiency/dg-optimizing.mdx b/...relic-solutions/observability-maturity/operational-efficiency/dg-optimizing.mdx
@@ -648,7 +648,7 @@ The different approaches:
           * Logs generated per cluster
         </Callout>
 
-        It's not surprising that a complex and decentralized system like Kubernetes has the potential to generate a lot of telemetry fast.  There are a few good approaches to managing data ingest in Kubernetes.  These will be very straightforward if you are using observability as code in your K8s deployments. We highly recommend you install this `Kubernetes Data Ingest Analysis` dashboard for making any decisions about reducing K8s ingest.  The dashbaord is available in this [quickstart](https://newrelic.com/instant-observability/infrastructure-integrations-data-analysis/8e31a0ae-81c0-4df0-a119-a0ada9ec16fa).
+        It's not surprising that a complex and decentralized system like Kubernetes has the potential to generate a lot of telemetry fast.  There are a few good approaches to managing data ingest in Kubernetes.  These will be very straightforward if you are using observability as code in your K8s deployments. We highly recommend you install this `Kubernetes Data Ingest Analysis` dashboard before making any decisions about reducing K8s ingest.  The dashbaord is available in this [quickstart](https://newrelic.com/instant-observability/infrastructure-integrations-data-analysis/8e31a0ae-81c0-4df0-a119-a0ada9ec16fa).
 
         ### Scrape interval