diff --git a/gdi/opentelemetry/components/memory-limiter-processor.rst b/gdi/opentelemetry/components/memory-limiter-processor.rst
index d1573998c..cec550c6b 100644
--- a/gdi/opentelemetry/components/memory-limiter-processor.rst
+++ b/gdi/opentelemetry/components/memory-limiter-processor.rst
@@ -36,13 +36,10 @@ To activate the resource processor, add ``memory_limiter`` to the ``processors``
 
 Define the ``memory_limiter`` as the first processor in the pipeline, immediately after the receivers, to ensure that backpressure can be sent to applicable receivers, and to minimize the likelihood of dropped data when ``memory_limiter`` gets triggered.
 
-Along with the ``memory_limiter`` processor, it's highly recommended to configure the Ballast extension as well on every Collector. The ballast should be configured to be 1/3 to 1/2 of the memory allocated to the Collector. 
-
 See the following example:
 
 .. code-block:: yaml
 
-
   processors:
     memory_limiter:
       check_interval: 1s
@@ -53,7 +50,6 @@ To complete the configuration, include the processor in any pipeline of the ``se
 
 .. code-block:: yaml
 
-
   service:
     pipelines:
       metrics: