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

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

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

## Findings (5)

```yaml
- file: explore-analyze/alerting/alerts/maintenance-windows.md
line: 13
category: missing-h1-anchor
severity: high
evidence: "H1 reads '# Maintenance windows' with no anchor suffix; every other file in
this directory uses an H1 anchor (e.g. [alerting-common-issues], [alerting-getting-started],
[alerting-setup], [alerting-troubleshooting])."
suggested_fix: |
# Maintenance windows [maintenance-windows]

- file: explore-analyze/alerting/alerts/alerting-troubleshooting.md
line: 14
category: weak-opening
severity: medium
evidence: "Single sentence 'Alerting provides many options for diagnosing problems with
rules and connectors.' omits 'limitations' (which appears in the H1), uses 'Alerting'
without a product substitution, and does not convey the page's scope in two sentences."
suggested_fix: |
{{kib}} alerting provides tools for diagnosing problems with rules and connectors,
including log inspection, debugging endpoints, and REST APIs. This page also
describes known limitations that affect rule execution and scheduling.

- file: explore-analyze/alerting/alerts/event-log-index.md
line: 17
category: weak-opening
severity: medium
evidence: "After the technical-preview warning admonition, the page has no prose
introduction paragraph — it jumps directly to a task fragment 'Use the event log
index to determine:' followed by a bullet list. There is no sentence explaining what
the event log index is or why you would query it."
suggested_fix: |
The event log index (`.kibana-event-log*`) records the execution history of {{kib}}
alerting rules and their actions. Query this index to audit rule runs, diagnose
action failures, and measure execution durations. Use the event log index to
determine:

- file: explore-analyze/alerting/alerts/testing-connectors.md
line: 13
category: weak-opening
severity: medium
evidence: "Opening jumps directly into navigation instructions ('In Stack Management >
Connectors, you can test a newly created connector by navigating to the Test tab...')
without explaining what connector testing verifies, when to use it, or why. The page
purpose is buried behind UI steps."
suggested_fix: |
Testing a connector in {{kib}} verifies that it can reach its target service and
deliver a payload successfully. Run a test before attaching a connector to an
alerting rule to confirm credentials and network connectivity are correct.

- file: explore-analyze/alerting/alerts/alerting-setup.md
line: 2
category: inadequate-navigation-title
severity: low
evidence: "navigation_title is 'Set up' — a bare verb with no subject or feature
context. Sibling pages use self-contained labels ('Getting started with alerts',
'Create and manage rules', 'View and manage alerts'), making 'Set up' ambiguous
in the navigation tree."
suggested_fix: |
navigation_title: Set up alerting
```

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

## Notes
- Rule-type how-to pages (es-query, index-threshold, geo-alerting) share a pattern of minimal single-sentence openings; those were not flagged as local convention appears consistent across the sub-tree.

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

Start with the five files named in the findings and compare their headings and openings with the cited sibling pages in the alerting directory. Update the missing anchor, contextual introductions, and navigation title as specified, then verify that all listed pages have specific H1s, purpose-focused openings, and prerequisites where applicable.

Written by the indexing model from the issue text.