Docs fix — page openings: shard 1/1 — 27 pages

Generated by `gh-aw-docs-openings-sweep` for `elastic/opentelemetry` on 2026-W25.

Shard 1/1 · 27 pages in slice · 0 recently-changed · 27 total in scope · corpus 27 pages.

## Findings (5)

```yaml
- file: docs/reference/motlp/rate-limiting.md
line: 16
category: vague-h1
severity: high
evidence: "H1 is '# Rate limiting' — no product or feature context; the title could describe
rate limiting in any system"
suggested_fix: |
# Managed OTLP Endpoint rate limiting [motlp-rate-limiting]

- file: docs/reference/architecture/hosts_vms.md
line: 16
category: weak-opening
severity: medium
evidence: "Opening is a single imperative sentence that gives a deployment instruction
('On host or virtual machine environments, deploy local, per-host OpenTelemetry
Collector instances...') instead of stating what the page covers or why it matters"
suggested_fix: |
This page describes the recommended EDOT architecture for host and virtual machine (VM)
environments. In this setup, you deploy a local OpenTelemetry Collector on each host or VM
to collect logs and infrastructure metrics, enrich application telemetry, and forward
everything to your Elastic backend.

- file: docs/reference/compatibility/limitations.md
line: 17
category: weak-opening
severity: medium
evidence: "First sentence introduces EDOT's OTel-native approach generically; second sentence
is a forward-looking statement about Elastic's ongoing work — neither conveys that this is
a limitations page. The actual page purpose appears only in the third sentence, in a
separate paragraph."
suggested_fix: |
EDOT provides an OTel-native ingestion path that covers most core observability use cases,
but some capabilities available with classic Elastic components are not yet supported.
This page documents the known limitations so you can determine whether EDOT meets your
requirements or whether to supplement it with classic Elastic components.

- file: docs/reference/compatibility/nomenclature.md
line: 17
category: weak-opening
severity: medium
evidence: "First two sentences describe OpenTelemetry's general architecture and EDOT's broad
OTel compatibility — neither sentence conveys that this page defines the specific
nomenclature terms (Incompatible / Compatible / Not supported / Supported) used across
EDOT documentation"
suggested_fix: |
This page defines the compatibility and support states used throughout EDOT documentation
to describe how well a component or ingestion path works with Elastic, and the level of
support Elastic provides. Understanding these states helps you select components with
confidence and know when to contact Elastic support.

- file: docs/reference/data-streams.md
line: 16
category: weak-opening
severity: medium
evidence: "Opening paragraph is one sentence ending in a colon ('{{edot}} writes telemetry
data to two types of data stream schemas in {{es}}:') followed immediately by a two-item
bullet list. The page-scope sentence ('This page provides a practical reference...') is
deferred to paragraph 2."
suggested_fix: |
{{edot}} writes telemetry signals to {{es}} using either OTel-native data streams (the
default) or ECS-compatible data streams for backwards compatibility with {{product.apm}}.
This page is a practical reference for which data streams EDOT uses, how exporter behavior
controls the destination, which storage engines back each stream type, and how to configure
data retention.
```

## Done when
- All listed pages have a specific, contextual H1; an opening paragraph that conveys purpose within the first two sentences; and (where applicable) a prerequisites section.
- A PR addressing this issue is merged.

## Notes
- The 6 `_snippets/` files in scope were excluded: they are partial include files with no standalone H1 or opening paragraph.

> Generated by [Docs page-openings sweep agent](https://github.com/elastic/opentelemetry/actions/runs/27820349394) · 254.8 AIC · ⌖ 13.4 AIC · ⊞ 34K · [◷](https://github.com/search?q=repo%3Aelastic%2Fopentelemetry+is%3Aissue+%22gh-aw-workflow-call-id%3A+elastic%2Fopentelemetry%2Fgh-aw-docs-openings-sweep%22&type=issues)