diff --git a/content/en/blog/2024/prom-and-otel/index.md b/content/en/blog/2024/prom-and-otel/index.md
index a9d184213ca1..203bab7f6592 100644
--- a/content/en/blog/2024/prom-and-otel/index.md
+++ b/content/en/blog/2024/prom-and-otel/index.md
@@ -287,7 +287,7 @@ config section of the spec by setting the `target_allocator.endpoint`:
 
 The Target Allocator endpoint that the Prometheus receiver config is pointing to 
 is a concatenation of the OTel Collector’s name (`otelcol`, in our case) and the 
-`-targetallocator` suffix.
+`-targetallocator` suffix. [(This is now done automatically for users!)](https://github.com/open-telemetry/opentelemetry-operator/blob/main/pkg/featuregate/featuregate.go#L58-L65)
 
 Finally, if you want to enable the Prometheus CR functionality of the Target 
 Allocator, you’ll need to define your own `ServiceMonitor` and `PodMonitor`