[Alerting V2][Serverless & 9.5][M2] Apply naming guidelines to Kibana alerting pages (#6526)

## Summary

Contributes to
elastic/docs-content-internal#919.

Updates five existing Kibana alerting pages in `alerting/alerts/` to
consistently use "Kibana alerting" as the primary term, per the alerting
naming guidelines:

- `alerts.md`: rename H1 to "Kibana alerting", add opening paragraph
establishing the system identity, add cross-reference to experimental
alerting features
- `alerting-getting-started.md`: rename H1 to "Getting started with
Kibana alerting", update first sentence
- `alerting-setup.md`: rename H1 to "Set up Kibana alerting", add anchor
sentence
- `create-manage-rules.md`: rename H1 to include "Kibana alerting"
- `view-alerts.md`: rename H1 to include "Kibana alerting", update intro
sentence

**Why**: The naming guidelines establish "Kibana alerting" as the
primary term for the existing alerting system to distinguish it from the
experimental alerting features. Every page should identify its system in
the first paragraph so search engines and AI retrieval can surface the
right content.

This PR is independent and can be merged on its own. It is part of the
broader series replacing [PR
#5528](#5528).


## Test plan

- [ ] Confirm no "Kibana alerting v1" in modified files
- [ ] Verify the cross-reference in `alerts.md` to
`kibana-alerting-experimental.md` is correct (resolves once PR #6521 is
merged)
- [ ] Check H1 changes don't break any existing anchor links (H1 anchors
not changed)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: nastasha-solomon

docset.yml

@@ -124,6 +124,8 @@ subs:
   ls-pipelines-app:   "Logstash Pipelines"
   maint-windows-app:   "Maintenance Windows"
   maint-windows-cap:   "Maintenance windows"
+  alerting-v2:   "experimental alerting features"
+  alerting-v2-cap:   "Experimental alerting features"
   custom-roles-app:   "Custom Roles"
   data-source:   "data view"
   data-sources:   "data views"

explore-analyze/alerting/alerts.md

@@ -10,9 +10,15 @@ products:
   - id: kibana
   - id: cloud-serverless
   - id: cloud-hosted
+description: "Overview of Kibana alerting: rules, alerts, actions, connectors, and how they work together."
 ---
 
-# Alerts
+# {{kib}} alerting [alerts]
+
+{{kib}} alerting is the built-in alerting system in {{kib}}. It lets you define rules that check your data on a schedule, create alerts when conditions are met, and trigger actions through connectors (email, Slack, webhooks, and more). It is available on all deployments.
+<!-- TODO: Uncomment when PR #6521 (experimental overview) is merged:
+For the {{alerting-v2}} built on {{esql}}, refer to [{{alerting-v2-cap}}](kibana-alerting-experimental.md).
+-->
 
 ## {{rules-ui}} [rules]
 

explore-analyze/alerting/alerts/alerting-getting-started.md

@@ -14,9 +14,9 @@ products:
   - id: elastic-stack
 ---
 
-# Getting started with alerting [alerting-getting-started]
+# Getting started with {{kib}} alerting [alerting-getting-started]
 
-Alerting enables you to define *rules*, which detect complex conditions within different {{kib}} apps and trigger actions when those conditions are met. Alerting is integrated with [**{{observability}}**](../../../solutions/observability/incident-management/alerting.md), [**Security**](detection-rules://index.md), [**Maps**](geo-alerting.md) and [**{{ml-app}}**](../../../explore-analyze/machine-learning/anomaly-detection/ml-configuring-alerts.md). It can be centrally managed from **{{stack-manage-app}}** and provides a set of built-in [connectors](../../../deploy-manage/manage-connectors.md) and [rules](rule-types.md#stack-rules) for you to use.
+{{kib}} alerting is the built-in alerting system in {{kib}}. It enables you to define *rules*, which detect complex conditions within different {{kib}} apps and trigger actions when those conditions are met. Alerting is integrated with [**{{observability}}**](../../../solutions/observability/incident-management/alerting.md), [**Security**](detection-rules://index.md), [**Maps**](geo-alerting.md) and [**{{ml-app}}**](../../../explore-analyze/machine-learning/anomaly-detection/ml-configuring-alerts.md). It can be centrally managed from **{{stack-manage-app}}** and provides a set of built-in [connectors](../../../deploy-manage/manage-connectors.md) and [rules](rule-types.md#stack-rules) for you to use.
 
 :::{image} /explore-analyze/images/kibana-alerting-overview.png
 :alt: {{rules-ui}} UI

explore-analyze/alerting/alerts/alerting-setup.md

@@ -9,9 +9,9 @@ products:
   - id: kibana
 ---
 
-# Set up [alerting-setup]
+# Set up {{kib}} alerting [alerting-setup]
 
-{{kib}} {{alert-features}} are automatically enabled, but might require some additional configuration.
+{{kib}} alerting is the built-in alerting system in {{kib}}. {{alert-features}} are automatically enabled, but might require some additional configuration.
 
 ## Prerequisites [alerting-prerequisites]
 

explore-analyze/alerting/alerts/create-manage-rules.md

@@ -9,9 +9,9 @@ products:
   - id: kibana
 ---
 
-# Create and manage alerting rules with {{kib}} [create-and-manage-rules]
+# Create and manage {{kib}} alerting rules [create-and-manage-rules]
 
-The **{{stack-manage-app}}** > **{{rules-ui}}** UI provides a cross-app view of alerting. Different {{kib}} apps like [**{{observability}}**](../../../solutions/observability/incident-management/alerting.md), [**Security**](detection-rules://index.md), [**Maps**](geo-alerting.md) and [**{{ml-app}}**](../../machine-learning/machine-learning-in-kibana.md) can offer their own rules.
+The **{{stack-manage-app}}** > **{{rules-ui}}** UI provides a cross-app view of {{kib}} alerting. Different {{kib}} apps like [**{{observability}}**](../../../solutions/observability/incident-management/alerting.md), [**Security**](detection-rules://index.md), [**Maps**](geo-alerting.md) and [**{{ml-app}}**](../../machine-learning/machine-learning-in-kibana.md) can offer their own rules.
 
 You can find **Rules** in **Stack Management** > **Alerts and insights** > **Rules** in {{kib}} or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 

explore-analyze/alerting/alerts/view-alerts.md

@@ -9,9 +9,9 @@ products:
   - id: kibana
 ---
 
-# View and manage alerts in {{kib}} [view-alerts]
+# View and manage alerts from {{kib}} alerting rules [view-alerts]
 
-When the conditions of a rule are met, it creates an alert. If the rule has actions, they run at the defined frequency. For example, the rule can send email notifications for each alert at a custom interval. For an introduction to the concepts of rules, alerts, and actions, refer to [Alerting](../alerts.md).
+{{kib}} alerting creates an alert when the conditions of a rule are met. If the rule has actions, they run at the defined frequency. For example, the rule can send email notifications for each alert at a custom interval. For an introduction to the concepts of rules, alerts, and actions, refer to [{{kib}} alerting](../alerts.md).
 
 Manage alerts from the following places:
 

explore-analyze/alerting/watcher/enable-watcher.md

@@ -10,7 +10,7 @@ products:
 # Enable Watcher [enable-watcher]
 
 ::::{note}
-If you are looking for Kibana alerting, check [Alerting](../../../explore-analyze/alerting.md).
+If you are looking for {{kib}} alerting, check [Alerting](../../../explore-analyze/alerting.md).
 ::::
 
 Watcher can be enabled when configuring your cluster. You can run Alerting on a separate cluster from the cluster whose data you are actually watching.
@@ -23,7 +23,7 @@ To enable Watcher on a cluster, you may first need to perform one or several of
 
 * To receive default Elasticsearch Watcher alerts (cluster status, nodes changed, version mismatch), you need to have monitoring enabled to send to the Admin email address specified in Kibana. To enable this, go to **Advanced Settings > Admin email**.
 
-To learn more about Kibana alerting and how to use it, check [Alerting and Actions](../../../explore-analyze/alerting.md).
+To learn more about {{kib}} alerting and how to use it, check [Alerting and Actions](../../../explore-analyze/alerting.md).
 
 ## Send alerts by email [watcher-allowlist]