docs: retire EDOT brand across all reference docs (9.5)

[alexandra5000]

What does this PR do?

Renames all user-facing prose across the opentelemetry docs hub per the 9.5 product-naming decision (elastic/docs-content-internal#1242):

Old	New
EDOT Collector	{{agent}} → Elastic Agent
EDOT SDKs / EDOT {Language}	Elastic OTel SDKs / Elastic OTel {Language}
EDOT Cloud Forwarder	{{edot-cf}} → Elastic Cloud Forwarder
EDOT (generic brand)	{{edot}} → Elastic OpenTelemetry

Also updates docs/docset.yml: flips edot and edot-cf sub values, adds agent sub, renames the project title.

22 files changed: compatibility/, architecture/, edot-cloud-forwarder/, managed-inputs/, and the hub pages (index.md, central-configuration.md, data-streams.md, edot-sdks/index.md).

Why is it important?

This is the hub repo for all EDOT/OTel reference content. It needs to consistently reflect the new names before the 9.5 GA cutover.

How to test

Build docs locally with docs-builder and verify:

• No "EDOT" prose in rendered output (excluding the image filename EDOT-SDKs-Collector.png)
• {{edot}} renders as "Elastic OpenTelemetry", {{agent}} as "Elastic Agent", {{edot-cf}} as "Elastic Cloud Forwarder"

Notes

• Held as draft — merges in coordinated window with elastic-agent, docs-content, and docs-builder PRs on 9.5 GA (July 28, 2026)
• Related: docs: rename EDOT Collector → Elastic Agent across reference docs (9.5) elastic-agent#15639
• Part of: elastic/docs-content-internal#1242

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• CONTRIBUTE.md
• docs/reference/architecture/hosts_vms.md
• docs/reference/architecture/index.md
• docs/reference/architecture/k8s.md
• docs/reference/architecture/kafka.md
• docs/reference/central-configuration.md
• docs/reference/compatibility/collectors.md
• docs/reference/compatibility/data-streams.md
• docs/reference/compatibility/edot-vs-upstream.md
• docs/reference/compatibility/features.md

More links …

• docs/reference/compatibility/index.md
• docs/reference/compatibility/limitations.md
• docs/reference/compatibility/nomenclature.md
• docs/reference/compatibility/sdks.md
• docs/reference/data-streams.md
• docs/reference/edot-cloud-forwarder/gcp/index.md
• docs/reference/edot-cloud-forwarder/index.md
• docs/reference/edot-sdks/index.md
• docs/reference/index.md
• docs/reference/managed-inputs/index.md
• docs/reference/managed-inputs/managed-otlp-endpoint.md
• docs/reference/managed-inputs/troubleshooting.md

[github-actions]

Elastic Docs Style Checker (Vale)

Summary: 1 warning, 5 suggestions found

⚠️ Warnings (1): Fix when the suggestion improves clarity or correctness.

File	Line	Rule	Message
docs/reference/compatibility/collectors.md	88	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'versus' instead of 'vs'.

💡 Suggestions (5): Optional style improvements. Apply when helpful.

File	Line	Rule	Message
docs/reference/compatibility/limitations.md	38	Elastic.Negations	Consider rephrasing to avoid negative constructions like 'can't access fields that have a dot in their name without'. Try stating what something IS rather than what it is NOT.
docs/reference/compatibility/limitations.md	52	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
docs/reference/compatibility/limitations.md	52	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
docs/reference/compatibility/limitations.md	55	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
docs/reference/compatibility/sdks.md	38	Elastic.Versions	Use 'or later' instead of 'or higher' when referring to versions.

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.