diff --git a/content/en/opentelemetry/schema_semantics/service_entry_spans.md b/content/en/opentelemetry/schema_semantics/service_entry_spans.md
index abdd9c49defa..dea76ef7b765 100644
--- a/content/en/opentelemetry/schema_semantics/service_entry_spans.md
+++ b/content/en/opentelemetry/schema_semantics/service_entry_spans.md
@@ -17,7 +17,7 @@ This feature is in beta. If you have any feedback, contact <a href="/help/">Data
 Datadog uses [service-entry spans][1] throughout the platform for features such as [Trace Metrics][2] and the [APM Trace Explorer][3]. This convention is unique to Datadog, but can be mapped from the [`SpanKind`][4] attribute in OpenTelemetry by following the opt-in guide below.
 
 ## Opting in to the feature
-To opt into the **public beta**, enable the config option depending on the ingestion path.
+This feature requires OTel Collector Contrib v0.100.0 or greater and Datadog Agent v7.53.0 or greater. To opt into the **public beta**, enable the config option depending on the ingestion path.
 
 {{< tabs >}}
 {{% tab "OTel Collector and Datadog Exporter" %}}
@@ -51,7 +51,7 @@ The new service-entry span identification logic can be enabled by adding `"enabl
 
 This new service-entry span identification logic may increase the number of spans that generate trace metrics, which may affect existing monitors that are based on trace metrics. Users who only have internal spans will see a decrease in trace metrics.
 
-If you have existing monitors based on trace metrics, you can update them after upgrading since this change introduces more consistency in trace metrics. If you only have internal span, update your instrumentation according to the above table to receive trace metrics and service-entry spans.
+If you have existing monitors based on trace metrics, you can update them after upgrading since this change introduces more consistency in trace metrics. If you only have internal spans, update your instrumentation according to the above table to receive trace metrics and service-entry spans.
 
 [`SpanKind`][4] is typically set when a span is created, but can also be updated by using the [transform processor][5] in the OpenTelemetry Collector to control the mapping above. For example, if trace metrics are desired for an internal span, the following configuration transforms an internal span with `http.path: "/health"` into a client span:
 ```yaml