Skip to content

Resolve docs style sweep findings across EDOT reference pages#623

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/fix-docs-style-issues
Draft

Resolve docs style sweep findings across EDOT reference pages#623
Copilot wants to merge 2 commits into
mainfrom
copilot/fix-docs-style-issues

Conversation

Copilot AI commented Jun 19, 2026

Copy link
Copy Markdown

This updates the EDOT reference docs to address the style sweep findings in the scoped 27-page shard. The changes are limited to wording, UI label formatting, and generated doc text needed to satisfy the cited Elastic style rules.

  • Scope

    • Updates 10 reference docs plus the EDOT SDK feature source used to generate one affected page.
    • Resolves the flagged issues for menu breadcrumb formatting, directional language, version phrasing, and word choice.
  • UI writing and accessibility

    • Replaced menu separators like > with in UI paths.
    • Removed directional phrasing such as “listed above” in favor of context-stable wording.
    • Rephrased the ingest pipeline dotted-field sentence to avoid the flagged negative construction.
  • Wording normalization

    • Replaced flagged may usages with can or might where appropriate.
    • Changed version language from or higher / and higher to or later / and later.
  • Generated EDOT SDK content

    • Updated the runtime-metrics note in docs/reference/edot-sdks/features.yml.
    • Regenerated the corresponding note in docs/reference/edot-sdks/index.md to keep generated content in sync.
Before:
**AutoOps Monitoring > Nodes**
Elastic Stack versions 8.18 or higher
OTel SDK distributions other than the ones listed above

After:
**AutoOps Monitoring → Nodes**
Elastic Stack versions 8.18 or later
OTel SDK distributions other than the ones listed in the preceding section

Copilot AI changed the title [WIP] Fix documentation style issues in multiple pages Resolve docs style sweep findings across EDOT reference pages Jun 19, 2026
Copilot AI requested a review from theletterf June 19, 2026 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants