Merge remote-tracking branch 'origin/main' into remote_clusters_h1_headings

Author: eedugon

.github/CODEOWNERS

@@ -35,7 +35,7 @@
 /release-notes/                             @elastic/docs
 
 /release-notes/apm-agents/                  @elastic/ingest-docs
-/release-notes/elastic-cloud-serverless/    @elastic/admin-docs
+/release-notes/elastic-cloud-serverless/    @elastic/admin-docs @elastic/docs-serverless-release-team
 /release-notes/elastic-observability/       @elastic/ski-docs
 /release-notes/elastic-security/            @elastic/ski-docs
 /release-notes/elasticsearch-clients/       @elastic/developer-docs

deploy-manage/api-keys.md

@@ -6,9 +6,10 @@ applies_to:
     ece: ga
     self: ga
   serverless: ga
+navigation_title: API keys
 ---
 
-# API keys
+# Elastic API keys
 
 API keys are security mechanisms used to authenticate and authorize access to your deployments and {{es}} resources. 
 

deploy-manage/deploy/cloud-enterprise.md

@@ -44,7 +44,7 @@ In ECE, a deployment is a managed {{stack}} environment that provides users with
 
 The section covers the following tasks:
 
-* [Deploy ECE orchestrator](./cloud-enterprise/deploy-an-orchestrator.md)
+* [Deploy an ECE orchestrator](./cloud-enterprise/deploy-an-orchestrator.md)
     - [Prepare the environment](./cloud-enterprise/prepare-environment.md)
     - [Install ECE](./cloud-enterprise/install.md)
     - [Air gapped installations](./cloud-enterprise/air-gapped-install.md)

deploy-manage/deploy/cloud-enterprise/deploy-an-orchestrator.md

@@ -2,8 +2,9 @@
 applies_to:
   deployment:
     ece: all
+navigation_title: Deploy an orchestrator
 ---
-# Deploy an orchestrator
+# Deploy an {{ece}} orchestrator
 
 {{ece}} (ECE) provides a centralized platform that allows organizations to run {{es}}, {{kib}}, and other {{stack}} components across multiple machines, whether in a private or public cloud, virtual machines, or your own premises.
 

deploy-manage/deploy/cloud-enterprise/ece-regional-deployment-aliases.md

@@ -6,9 +6,10 @@ applies_to:
     ece: all
 products:
   - id: cloud-enterprise
+navigation_title: Custom endpoint aliases
 ---
 
-# Custom endpoint aliases [ece-regional-deployment-aliases]
+# Configure custom endpoint aliases on {{ece}} [ece-regional-deployment-aliases]
 
 Custom aliases for your deployment endpoints on {{ece}} allow you to have predictable, human-readable URLs that can be shared easily.
 

deploy-manage/deploy/cloud-enterprise/switch-from-apm-to-integrations-server-payload.md

@@ -6,9 +6,10 @@ applies_to:
     ece: all
 products:
   - id: cloud-enterprise
+navigation_title: Switch from APM to Integrations Server
 ---
 
-# Switch from APM to Integrations Server payload [ece-integrations-server-apm-switch]
+# Switch from APM to Integrations Server payload on {{ece}} [ece-integrations-server-apm-switch]
 
 This example shows how to use the {{ece}} RESTful API to switch from using the legacy [APM & Fleet Server](https://www.elastic.co/guide/en/cloud-enterprise/3.8/ece-manage-apm-and-fleet.html) to [Integrations Server](manage-integrations-server.md).
 

deploy-manage/deploy/cloud-on-k8s/configuration-beats.md

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration
 ---
 
-# Configuration [k8s-beat-configuration]
+# Configuration for Beats on {{eck}} [k8s-beat-configuration]
 
 ## Upgrade the Beat specification [k8s-beat-upgrade-specification]
 

deploy-manage/deploy/cloud-on-k8s/configuration-examples-beats.md

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration examples
 ---
 
-# Configuration Examples [k8s-beat-configuration-examples]
+# Beats configuration examples on {{eck}} [k8s-beat-configuration-examples]
 
 In this section you can find manifests that address a number of common use cases and can be your starting point in exploring Beats deployed with ECK. These manifests are self-contained and work out-of-the-box on any non-secured Kubernetes cluster. They all contain three-node {{es}} cluster and single {{kib}} instance. All Beat configurations set up {{kib}} dashboards if they are available for a given Beat and all required RBAC resources.
 

deploy-manage/deploy/cloud-on-k8s/configuration-examples-fleet.md

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration examples
 ---
 
-# Configuration Examples [k8s-elastic-agent-fleet-configuration-examples]
+# Fleet managed agents configuration examples on {{eck}} [k8s-elastic-agent-fleet-configuration-examples]
 
 This section contains manifests that illustrate common use cases, and can be your starting point in exploring {{agent}} deployed with ECK. These manifests are self-contained and work out-of-the-box on any non-secured {{k8s}} cluster. They all contain a three-node {{es}} cluster, a single {{kib}} instance and a single {{fleet-server}} instance.
 

deploy-manage/deploy/cloud-on-k8s/configuration-examples-logstash.md

@@ -6,9 +6,10 @@ applies_to:
     eck: all
 products:
   - id: cloud-kubernetes
+navigation_title: Configuration examples
 ---
 
-# Configuration examples [k8s-logstash-configuration-examples]
+# Logstash configuration examples on {{eck}} [k8s-logstash-configuration-examples]
 
 This section contains manifests that illustrate common use cases, and can be your starting point in exploring Logstash deployed with ECK. These manifests are self-contained and work out-of-the-box on any non-secured Kubernetes cluster. They all contain a three-node {{es}} cluster and a single {{kib}} instance.