Updating H1 titles in the Deploy and manage section

yetanothertw · yetanothertw · commit 08e2eb61ad7f · 2025-09-16T11:44:36.000+01:00
Updates several H1 titles so that they're unique within our docs set. Also, a few references had to be updated as a result.
Related to the H1 bash initiative
diff --git a/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md b/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Manage your Integrations Server 
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-integrations-server.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: cloud-enterprise
 ---
 
-# Manage your Integrations Server [ece-manage-integrations-server]
+# Manage your Integrations Server in {{ece}} [ece-manage-integrations-server]
 
 For deployments that are version 8.0 and later, you have the option to add a combined [Application Performance Monitoring (APM) Server](/solutions/observability/apm/index.md) and [Fleet Server](/reference/fleet/index.md) to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the {{es}} cluster. Fleet allows you to centrally manage Elastic Agents on many hosts.
 
@@ -43,7 +44,7 @@ New certificates must be generated for both these endpoints. Check [Enable custo
 
 ## Using the API to manage Integrations Server [ece_using_the_api_to_manage_integrations_server]
 
-To manage Integrations Server through the API you need to include an Integrations Server payload when creating or updating a deployment. Check [Enable Integrations Server through the API](../../../deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md) for an example.
+To manage Integrations Server through the API you need to include an Integrations Server payload when creating or updating a deployment. Check [Enable Integrations Server through the API](../../../deploy-manage/deploy/cloud-enterprise/ece-integrations-server-api-example.md) for an example.
 
 Check [Switch from APM to Integrations Server payload](../../../deploy-manage/deploy/cloud-enterprise/switch-from-apm-to-integrations-server-payload.md) for an example of how to switch from APM & Fleet Server to Integrations Server.
 
diff --git a/deploy-manage/deploy/cloud-enterprise/working-with-deployments.md b/deploy-manage/deploy/cloud-enterprise/working-with-deployments.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Manage deployments
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-stack-getting-started.html
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-administering-deployments.html
@@ -13,7 +14,7 @@ products:
 % document scope: This doc focuses on everything that can be achieved from the deployment UI
 % TBD: include a link to a doc to manage deployments through ECE API. Same for Deploy an orchestrator section (ECE API links are still pending because we still haven't published the reference docs)
 
-# Manage deployments [ece-stack-getting-started]
+# Manage deployments in {{ece}} [ece-stack-getting-started]
 
 {{ece}} allows you to manage one or more instances of the {{stack}} through **deployments**.
 
diff --git a/deploy-manage/deploy/cloud-on-k8s/manage-deployments.md b/deploy-manage/deploy/cloud-on-k8s/manage-deployments.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Manage deployments
 applies_to:
   deployment:
     eck: all
 ---
-# Manage deployments
+# Manage deployments in {{eck}}
 
 This section provides detailed guidance on deploying, configuring, and managing {{es}} and {{kib}} within ECK. A **deployment** refers to an {{es}} cluster, optionally with one or more {{kib}} instances connected to it.
 
diff --git a/deploy-manage/deploy/elastic-cloud/manage-deployments.md b/deploy-manage/deploy/elastic-cloud/manage-deployments.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Manage deployments
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-manage-deployment.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: cloud-hosted
 ---
 
-# Manage deployments [ec-manage-deployment]
+# Manage deployments in {{ech}} [ec-manage-deployment]
 
 {{ech}} allows you to configure and maintain your deployments with a high level of control on every component of the {{stack}}. You can adjust the settings of any of your deployments at any time.
 
diff --git a/deploy-manage/deploy/elastic-cloud/manage-integrations-server.md b/deploy-manage/deploy/elastic-cloud/manage-integrations-server.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Manage your Integrations Server
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-manage-integrations-server.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: cloud-hosted
 ---
 
-# Manage your Integrations server [ec-manage-integrations-server]
+# Manage your Integrations server in {{ech}} [ec-manage-integrations-server]
 
 For deployments that are version 8.0 and later, you have the option to add a combined [Application Performance Monitoring (APM) Server](/solutions/observability/apm/index.md) and [Fleet Server](/reference/fleet/index.md) to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the {{es}} cluster. Fleet allows you to centrally manage Elastic Agents on many hosts.
 
diff --git a/deploy-manage/remote-clusters/ec-migrate-ccs.md b/deploy-manage/remote-clusters/ec-migrate-ccs.md
@@ -1,5 +1,5 @@
 ---
-navigation_title: Migrate the CCS deployment template
+navigation_title: Migrate from the CCS deployment template
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-migrate-ccs.html
 applies_to:
@@ -9,7 +9,7 @@ products:
   - id: cloud-hosted
 ---
 
-# Migrate the cross-cluster search deployment template [ec-migrate-ccs]
+# Migrate from the cross-cluster search deployment template in {{ech}} [ec-migrate-ccs]
 
 The cross-cluster search deployment template is now deprecated and has been removed from the {{ecloud}} Console. You no longer need to use the dedicated cross-cluster template to search across deployments. Instead, you can now use any template to [configure remote clusters](ec-enable-ccs.md) and search across them. Existing deployments created using this template are not affected, but they are required to migrate to another template before upgrading to {{stack}} 8.x.
 
diff --git a/deploy-manage/remote-clusters/ece-migrate-ccs.md b/deploy-manage/remote-clusters/ece-migrate-ccs.md
@@ -1,5 +1,5 @@
 ---
-navigation_title: Migrate the CCS deployment template
+navigation_title: Migrate from the CCS deployment template
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-migrate-ccs.html
 applies_to:
@@ -9,7 +9,7 @@ products:
   - id: cloud-enterprise
 ---
 
-# Migrate the cross-cluster search deployment template [ece-migrate-ccs]
+# Migrate from the cross-cluster search deployment template in {{ece}} [ece-migrate-ccs]
 
 The cross-cluster search deployment template is now deprecated was removed in {{ece}} 3.0. You no longer need to use the dedicated cross-cluster template to search across deployments. Instead, you can now use any template to [configure remote clusters](ece-enable-ccs.md) and search across them. Existing deployments created using this template are not affected, but they are required to migrate to another template before upgrading to {{stack}} 8.x.
 
diff --git a/reference/fleet/add-fleet-server-cloud.md b/reference/fleet/add-fleet-server-cloud.md
@@ -37,7 +37,7 @@ This approach might *not* be right for you if you have restrictions on connectiv
     * Requires additional wildcard domains and certificates (which normally only cover `*.cname`, not `*.*.cname`). This enables us to provide the URL for {{fleet-server}} of `https://.fleet.`.
     * The deployment template must contain an {{integrations-server}} node.
 
-    For more information about hosting {{fleet-server}} on {{ece}}, refer to [Manage your {{integrations-server}}](/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md).
+    For more information about hosting {{fleet-server}} on {{ece}}, refer to [](/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md).
 
 
 ::::{note}
diff --git a/reference/fleet/add-fleet-server-mixed.md b/reference/fleet/add-fleet-server-mixed.md
@@ -41,7 +41,7 @@ To deploy a self-managed {{fleet-server}} on-premises to work with an {{ech}} de
     * Requires additional wildcard domains and certificates (which normally only cover `*.cname`, not `*.*.cname`). This enables us to provide the URL for {{fleet-server}} of `https://.fleet.`.
     * The deployment template must contain an {{integrations-server}} node.
 
-    For more information about hosting {{fleet-server}} on {{ece}}, refer to [Manage your {{integrations-server}}](/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md).
+    For more information about hosting {{fleet-server}} on {{ece}}, refer to [](/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md).
 
 
 
diff --git a/reference/fleet/add-fleet-server-on-prem.md b/reference/fleet/add-fleet-server-on-prem.md
@@ -47,7 +47,7 @@ You can install only a single {{agent}} per host, which means you cannot run {{f
     * Requires additional wildcard domains and certificates (which normally only cover `*.cname`, not `*.*.cname`). This enables us to provide the URL for {{fleet-server}} of `https://.fleet.`.
     * The deployment template must contain an {{integrations-server}} node.
 
-    For more information about hosting {{fleet-server}} on {{ece}}, refer to [Manage your {{integrations-server}}](/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md).
+    For more information about hosting {{fleet-server}} on {{ece}}, refer to [](/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md).
 
 
 
