Update tsds-ingest-otlp.md

Author: theletterf

manage-data/data-store/data-streams/tsds-ingest-otlp.md

@@ -2,7 +2,6 @@
 navigation_title: "Ingest OTLP metrics"
 applies_to:
   stack: preview 9.2
-  serverless: preview
 products:
   - id: elasticsearch
 ---
@@ -15,11 +14,16 @@ In addition to the ingestion of metrics data through the bulk API,
 The endpoint is available under `/_otlp/v1/metrics`.
 
 Ingesting metrics data using the OTLP endpoint has the following advantages:
+
 * Improved ingestion performance, especially if the data contains many resource attributes.
 * Simplified index mapping:
   there's no need to manually create an index template, or define dimensions and metrics.
   Using the OTLP endpoint, metrics are dynamically mapped using the metadata included in the OTLP requests.
 
+:::{important}
+On {{ecloud}} , use the [{{motlp}}](opentelemetry:/reference/motlp.md) instead of connecting directly to the {{es}} OTLP endpoint.
+:::
+
 ## How to send data to the OTLP endpoint
 
 To send data from an OpenTelemetry Collector to the {{es}} OTLP endpoint,
@@ -60,27 +64,13 @@ use the [OpenTelemetry language SDK](https://opentelemetry.io/docs/getting-start
 
 ## When not to use the {{es}} OTLP endpoint
 
-On Elastic Cloud, use the [Elastic Cloud Managed OTLP Endpoint](opentelemetry:/reference/motlp.md) instead of connecting directly to the Elasticsearch OTLP endpoint.
-
-It's not recommended to send metrics from applications directly to the Elasticsearch OTLP endpoint,
-especially if there are many individual applications that each periodically send a small amount of metrics.
-Instead, send data to an OpenTelemetry collector first.
-This helps with handling many connections,
-and with creating bigger batches to improve ingestion performance.
-For more details on the recommended way to set up OpenTelemetry-based data ingestion,
-have a look at the [EDOT reference architecture](opentelemetry:/reference/architecture/index.md).
+Do not send metrics from applications directly to the {{es}} OTLP endpoint, especially if there are many individual applications that periodically send a small amount of metrics. Instead, send data to an OpenTelemetry Collector first. This helps with handling many connections, and with creating bigger batches to improve ingestion performance. For more details on the recommended way to set up OpenTelemetry-based data ingestion, refer to the [EDOT reference architecture](opentelemetry:/reference/architecture/index.md).
 
-At this point, {{es}} only supports the OTLP metrics endpoint (`/_otlp/v1/metrics`).
-Other signals,  are not supported as a native {{es}} OTLP endpoint at the moment.
-To ingest other signals,
-such as logs, traces, and profiles,
-use a distribution of the OpenTelemetry collector that includes the [Elasticsearch exporter](opentelemetry:/reference/edot-collector/components/elasticsearchexporter.md),
-such as the [Elastic distribution of OpenTelemetry (EDOT) Collector](opentelemetry:/reference/edot-collector/index.md).
+At this point, {{es}} only supports the OTLP metrics endpoint (`/_otlp/v1/metrics`). Other signals are not supported through a native {{es}} OTLP endpoint at the moment. To ingest logs, traces, and profiles, use a distribution of the OpenTelemetry Collector that includes the [{{es}} exporter](opentelemetry:/reference/edot-collector/components/elasticsearchexporter.md), like the [Elastic Distribution of OpenTelemetry (EDOT) Collector](opentelemetry:/reference/edot-collector/index.md).
 
 ## Send data to different data streams
 
-By default, metrics are ingested into the `metrics-generic.otel-default` data stream.
-You can influence the target data stream by setting specific attributes on your data:
+By default, metrics are ingested into the `metrics-generic.otel-default` data stream. You can influence the target data stream by setting specific attributes on your data:
 
 - `data_stream.dataset` or `data_stream.namespace` in attributes, with the following order of precedence: data point attribute -> scope attribute -> resource attribute
 - Otherwise, if the scope name contains `/receiver/<somereceiver>`, `data_stream.dataset` is set to the receiver name.
@@ -92,7 +82,5 @@ The target data stream name is constructed as `metrics-${data_stream.dataset}.ot
 
 ## Limitations
 
-* Histograms are only supported in delta temporality.
-  Set the temporality preference to delta in your SDKs,
-  or use the [`cumulativetodelta` processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/cumulativetodeltaprocessor) to avoid cumulative histograms to be dropped.
+* Histograms are only supported in delta temporality. Set the temporality preference to delta in your SDKs, or use the [`cumulativetodelta` processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/cumulativetodeltaprocessor) to avoid cumulative histograms to be dropped.
 * Exemplars are not supported.