Apply suggestions from code review

Awesome suggestions by Shaina :)

Co-authored-by: shainaraskas <[email protected]>

Author: eedugon

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

@@ -25,7 +25,7 @@ Before you start, you must:
 When you are ready to install ECE, you can proceed:
 
 * [With your private Docker registry](./ece-install-offline-with-registry.md)
-* [Without your private Docker registry](./ece-install-offline-no-registry.md)
+* [Without a private Docker registry](./ece-install-offline-no-registry.md)
 
 ::::{note}
 Deployment End-of-life (EOL) information relies on the connection to [https://www.elastic.co/support/eol.json](https://www.elastic.co/support/eol.json). If EOL information is updated, Elastic may require you to reconnect to [https://www.elastic.co/support/eol.json](https://www.elastic.co/support/eol.json) over the internet to get this information reflected.

deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md

@@ -5,28 +5,28 @@ applies_to:
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-hosts-rhel-centos-cloud.html
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-hosts-rhel-centos-onprem.html
+navigation_title: RHEL
 ---
 
 # Configure a RHEL host [ece-configure-hosts-rhel-centos]
 
 
-## Red Hat Enterprise Linux 8 (RHEL 8), 9 (RHEL 9), and Rocky Linux 8 and 9 [ece-setup-rhel8-podman]
 
 The following instructions show you how to prepare your hosts on Red Hat Enterprise Linux 8 (RHEL 8), 9 (RHEL 9), and Rocky Linux 8 and 9.
 
 * [Prerequisites](#ece-prerequisites-rhel8)
 * [Configure the host](#ece-configure-hosts-rhel8-podman)
 
 
-### Prerequisites [ece-prerequisites-rhel8]
+## Prerequisites [ece-prerequisites-rhel8]
 
 Follow your internal guidelines to create a RHEL 8 (the version must be >= 8.5), RHEL 9, Rocky Linux 8, or Rocky Linux 9 server or VM in your environment.
 
 Verify that required traffic is allowed. Check the [Networking prerequisites](ece-networking-prereq.md) for a list of ports that need to be open. The technical configuration depends on the underlying infrastructure.
 
 **Example:** For AWS, allowing traffic between hosts is implemented using security groups.
 
-### Configure the host [ece-configure-hosts-rhel8-podman]
+## Configure the host [ece-configure-hosts-rhel8-podman]
 
 1. Install the OS packages `lvm2`, `iptables`, `sysstat`, and `net-tools` by executing:
 

deploy-manage/deploy/cloud-enterprise/configure-host-suse.md

@@ -5,9 +5,10 @@ applies_to:
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-hosts-sles12-cloud.html
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-hosts-sles12-onprem.html
+navigation_title: SUSE
 ---
 
-# Configure host SUSE cloud [ece-configure-hosts-sles12]
+# Configure a SUSE host [ece-configure-hosts-sles12]
 
 The following instructions show you how to prepare your hosts on SLES 12 SP5 or 15.
 

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

@@ -13,7 +13,7 @@ Now that you have {{ece}} up and running, take a look at some of the additional
 
 ## Common ECE tasks
 
-* [Assign Roles to Hosts](../../../deploy-manage/deploy/cloud-enterprise/assign-roles-to-hosts.md) - Make sure new hosts can be used for their intended purpose after you install ECE on them.
+* [Assign roles to hosts](../../../deploy-manage/deploy/cloud-enterprise/assign-roles-to-hosts.md) - Make sure new hosts can be used for their intended purpose after you install ECE on them.
 * [System deployments configuration](system-deployments-configuration.md) - Best practices for ECE system deployments to ensure a highly available and resilient setup.
 * [Configure deployment templates](configure-deployment-templates.md) - Make the most out of deployment templates by configuring ECE for your hardware and creating custom deployment templates.
 * [Manage Elastic Stack versions](./manage-elastic-stack-versions.md) - Upload or remove Elastic Stack packs.

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

@@ -7,7 +7,7 @@ applies_to:
 
 # ECE installation procedures
 
-Choose the Elastic Cloud Enterprise deployment scenario that best fits your business needs:
+Choose the guide for the Elastic Cloud Enterprise [deployment scenario](/deploy-manage/deploy/cloud-enterprise/identify-deployment-scenario.md) that best fits your business needs:
 
 * [Deploy a small installation](deploy-small-installation.md): For development, test, and small-scale use cases.
 * [Deploy a medium installation](deploy-medium-installation.md): For many production setups.

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

@@ -44,7 +44,7 @@ ECE supports a [wide range of OS versions](https://www.elastic.co/support/matrix
 * [SUSE Linux Enterprise Server (SLES) 12 SP5 and 15](configure-host-suse.md)
 
 ::::{important} 
-Cloud providers default provide automatic operating system patching for their virtual machines. We strongly recommend disabling this feature to avoid potential data loss and installation failure. All patching should be done through [Perform host maintenance](../../maintenance/ece/perform-ece-hosts-maintenance.md) instructions.
+Cloud providers default provide automatic operating system patching for their virtual machines. We strongly recommend disabling this feature to avoid potential data loss and installation failure. All patching should be done using the [Perform host maintenance](../../maintenance/ece/perform-ece-hosts-maintenance.md) instructions.
 ::::
 
 ## Install ECE [install-ece]

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.
@@ -33,6 +33,10 @@ After your Elastic Cloud Enterprise installation is up, some additional steps mi
 * [Add a snapshot repository](../../tools/snapshot-and-restore/cloud-enterprise.md) to enable regular backups of your Elasticsearch clusters.
 
 * Consider enabling encryption-at-rest (EAR) on your hosts.
+  
+  :::{{tip}}
+  Encryption-at-rest is not implemented out of the box in {{{ece}}. [Learn more](/deploy-manage/security/secure-your-elastic-cloud-enterprise-installation.md#ece_encryption).
+  :::
 
 * To start creating {{es}} deployments, refer to [](./working-with-deployments.md).