diff --git a/hive-c0re/src/stats/otel_metrics.rs b/hive-c0re/src/stats/otel_metrics.rs
index bfb28f52..d5c394a3 100644
--- a/hive-c0re/src/stats/otel_metrics.rs
+++ b/hive-c0re/src/stats/otel_metrics.rs
@@ -1,6 +1,5 @@
-//! Per-agent container-resource OTEL export. hive-c0re already samples each
-//! agent container's cgroup load for the dashboard
-//! ([`super::container_stats`]); this rides those same gauges out to the
+//! Per-agent container-resource OTEL export. This is what the cgroup load
+//! sampled in [`super::container_stats`] feeds: it rides those gauges out to the
 //! hive's own collector — the same first hop the agents use, named by the
 //! standard `OTEL_EXPORTER_OTLP_ENDPOINT` (see `nix/host-modules/hive-c0re`,
 //! which sets it from the same binding it hands agents). No toggle of
@@ -194,7 +193,7 @@ fn register_instruments(provider: &SdkMeterProvider, snapshot: Arc<Mutex<Vec<Con
         .build();
 
     // Custom (`hyperhive.`) metrics semconv doesn't standardise: memory peak,
-    // on-disk footprint, and the instantaneous cpu percent the dashboard shows.
+    // on-disk footprint, and the instantaneous cpu percent.
     let snap = snapshot.clone();
     meter
         .u64_observable_gauge("hyperhive.container.memory.peak")