Merge pull request #1130 from splunk/aurbiztondo-collector-sizing

Update sizing.rst
splunk · Jan 12, 2024 · 7cf2c86 · 7cf2c86
2 parents 2172e72 + 8d0d92b
commit 7cf2c86
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/gdi/opentelemetry/sizing.rst b/gdi/opentelemetry/sizing.rst
@@ -9,7 +9,7 @@ Sizing and scaling
 
 By default, the Collector is configured to use 512 MB (500 x 2^20 bytes) of memory. 
 
-With a single CPU core, the Collector can receive, process, or export the following: 
+With a single CPU core, the Collector can ingest the following: 
 
 * If handling traces, 15,000 spans per second.
 * If handling metrics, 20,000 data points per second.
@@ -112,4 +112,4 @@ The solution is to shard the endpoints by Collector instances so that if we add
 Learn more
 ------------------------------------------------------------
 
-To learn more and see scaling examples, read the OpenTelemetry documentation at :new-page:`https://opentelemetry.io/docs/collector/scaling/ <https://opentelemetry.io/docs/collector/scaling/>`.
+To learn more and see scaling examples, read the OpenTelemetry documentation at :new-page:`https://opentelemetry.io/docs/collector/scaling/ <https://opentelemetry.io/docs/collector/scaling/>`.