Rewrote the note to make it easier to understand.

Author: jcatera-splunk

gdi/monitors-monitoring/cadvisor.rst

@@ -16,8 +16,9 @@ If you are using Kubernetes, consider the
 expose cAdvisor on a network port, even though they are running it
 within Kubelet.
 
-.. :note:: The Splunk Distribution of OpenTelemetry Collector cannot collect specific cgroup metrics exposed by cAdvisor, such as ``container_cpu_cfs_*`` 
-   in managed environments such as Amazon EKS, and the supported `kubeletstats` receiver does not expose these metrics by default.
+.. :note:: The Splunk Distribution of OpenTelemetry Collector has limitations in managed environments like Amazon EKS. 
+   For example, the collector cannot collect specific cgroup metrics exposed by cAdvisor, such as ``container_cpu_cfs_*``. 
+   The ``kubeletstats`` receiver also does not expose these metrics by default. 
 
 If you are running containers with Docker, retrieved metrics might
 overlap with ``docker-container-stats``. Consider not enabling the