sections moved in toc

Author: eedugon

deploy-manage/deploy/cloud-enterprise/alternative-install-ece-with-ansible.md

@@ -4,6 +4,7 @@ applies_to:
     ece: all
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-ansible.html
+navigation_title: Ansible playbook
 ---
 
 # Alternative: Install ECE with Ansible [ece-configure-ansible]

deploy-manage/deploy/cloud-enterprise/configure-operating-system.md

@@ -7,7 +7,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-os-onprem.html
 ---
 
-# Configure your operating system cloud [ece-configure-os]
+# Configure your operating system [ece-configure-os]
 
 Before installing Elastic Cloud Enterprise, you have to prepare your hosts with one of the following Linux distributions:
 

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

@@ -17,19 +17,16 @@ This section provides step-by-step guidance on:
 
 * [Prepare the environment](./prepare-environment.md): Follow the hardware, software, and networking prerequisites before the installation. 
 
-% Add here post-installation steps, configure OS, choose type of installation.
-
 * [Install ECE orchestrator](./install.md): Identify the deployment scenario that best fits your needs, choose an installation method, and complete the setup.
   * [](./configure-operating-system.md)
-  * [Install ECE on a public cloud](./install.md)
-  * [Install ECE on your own premises](./install.md)
+  * [](./install-ece-procedures.md)
   * [Alternative: install ECE with Ansible](./alternative-install-ece-with-ansible.md)
 
 * [Air-gapped installations](./air-gapped-install.md): Review the different options for air-gapped environments.
   * [With your private Docker registry](./ece-install-offline-with-registry.md)
   * [Without any Docker registry](./ece-install-offline-no-registry.md)
 
-* [Post-installation tasks](./post-installation-steps.md)
+* [](./post-installation-steps.md): Get ready for production by adding SSL certificates, configuring domain names, and completing other essential tasks.
 
 * [Configure ECE](./configure.md): Explore the most common tasks to configure your ECE platform.
   * [System deployments configuration](./system-deployments-configuration.md)

deploy-manage/deploy/cloud-enterprise/install.md

@@ -17,10 +17,15 @@ You can deploy ECE on public or private clouds, virtual machines, or on-premises
 * Google Cloud Platform (GCP)
 * Microsoft Azure
 
+::::{tip}
+If you already have an ECE platform up and running, and you want to add hosts to your installation, refer to [](./install-ece-on-additional-hosts.md).
+::::
+
 ::::{note} 
 In these pages we frequently refer to [Docker](https://www.docker.com/), as its currently the most common container engine, but these instructions are generally valid for [Podman](https://podman.io/) as well, with `podman` replacing `docker` in commands as appropriate.
 ::::
 
+
 ## Prerequisites
 
 Before you start, make sure to [identify your deployment scenario](identify-deployment-scenario.md) and follow all the referenced sections in [prepare your hosts](prepare-environment.md). Make sure that your selected infrastructure meets the requirements.

deploy-manage/deploy/cloud-enterprise/post-installation-steps.md

@@ -20,7 +20,7 @@ After your Elastic Cloud Enterprise installation is up, some additional steps mi
   If you intend to use [custom endpoint aliases](./enable-custom-endpoint-aliases.md) functionality, ensure you add the necessary Subject Alternative Name (SAN) entries to the proxy certificate.
   ::::
 
-* Optionally, if you want the deployment endpoint links and Single-sign on to work with your domain name, configure it as the **deployment domain name** in the Platform → Settings section of the [Cloud UI](./log-into-cloud-ui.md). The domain name is used to generate the endpoint URLs and must align with your Proxy certificate and DNS record.
+* Optionally, if you want the deployment endpoint links and Single-sign on to work with your domain name, configure it as the **deployment domain name** in the Platform → Settings section of the [Cloud UI](./log-into-cloud-ui.md). The domain name is used to generate the endpoint URLs and must align with your proxy certificate and DNS record.
 
   ::::{tip}
   For example, if your proxy certificate is signed for `*.elastic-cloud-enterprise.example.com` and you have a wildcard DNS register pointing `*.elastic-cloud-enterprise.example.com` to your load balancer, you should configure `elastic-cloud-enterprise.example.com` as the **deployment domain name** in Platform → Settings. Refer to [](./change-endpoint-urls.md) for more details.

deploy-manage/toc.yml

@@ -152,12 +152,12 @@ toc:
                       - file: deploy/cloud-enterprise/deploy-large-installation.md
                       - file: deploy/cloud-enterprise/fresh-installation-of-ece-using-podman-hosts.md
                       - file: deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md
-                  - file: deploy/cloud-enterprise/alternative-install-ece-with-ansible.md
                   - file: deploy/cloud-enterprise/log-into-cloud-ui.md
+                  - file: deploy/cloud-enterprise/post-installation-steps.md
                   - file: deploy/cloud-enterprise/install-ece-on-additional-hosts.md
                     children:
                       - file: deploy/cloud-enterprise/generate-roles-tokens.md
-                  - file: deploy/cloud-enterprise/post-installation-steps.md
+                  - file: deploy/cloud-enterprise/alternative-install-ece-with-ansible.md
                   - file: deploy/cloud-enterprise/statistics-collected-by-cloud-enterprise.md
               - file: deploy/cloud-enterprise/air-gapped-install.md
                 children: