Address review comments

Author: felixbarny

manage-data/data-store/data-streams/set-up-tsds.md

@@ -13,8 +13,10 @@ products:
 
 This page shows you how to manually set up a [time series data stream](/manage-data/data-store/data-streams/time-series-data-stream-tsds.md) (TSDS).
 
+::::{note}
 For a simplified setup that doesn't require manually mapping dimension and metric fields via index templates,
 have a look at the [OpenTelemetry Protocol (OTLP)-based data ingestion](tsds-ingest-otlp.md).
+::::
 
 ## Before you begin [tsds-prereqs]
 

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

@@ -13,11 +13,16 @@ In addition to the ingestion of metrics data through the bulk API,
 
 The endpoint is available under `/_otlp/v1/metrics`.
 
+:::{note}
+{{es}} only supports [OTLP/HTTP](https://opentelemetry.io/docs/specs/otlp/#otlphttp),
+not [OTLP/gRPC](https://opentelemetry.io/docs/specs/otlp/#otlpgrpc).
+:::
+
 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.
+  there's no need to manually create data streams, index templates, or define dimensions and metrics.
   Metrics are dynamically mapped using the metadata included in the OTLP requests.
 
 :::{important}
@@ -62,12 +67,10 @@ The supported options for `compression` are `gzip` (default value of the `OTLP/H
 To track metrics in your custom application,
 use the [OpenTelemetry language SDK](https://opentelemetry.io/docs/getting-started/dev/) of your choice.
 
-## When not to use the {{es}} OTLP endpoint
+## Best practices
 
 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 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:
@@ -80,5 +83,8 @@ The target data stream name is constructed as `metrics-${data_stream.dataset}.ot
 
 ## Limitations
 
+* Only the OTLP metrics endpoint (`/_otlp/v1/metrics`) is supported.
+  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),
+  such as the [Elastic Distribution of OpenTelemetry (EDOT) Collector](opentelemetry:/reference/edot-collector/index.md).
 * 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.