diff --git a/deploy-manage/api-keys/elastic-cloud-api-keys.md b/deploy-manage/api-keys/elastic-cloud-api-keys.md
index 998b47e192..7fee56d0b4 100644
--- a/deploy-manage/api-keys/elastic-cloud-api-keys.md
+++ b/deploy-manage/api-keys/elastic-cloud-api-keys.md
@@ -27,8 +27,8 @@ These keys provides access to the API that enables you to manage your deployment
 
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
 2. Go to your avatar in the upper right corner and choose **Organization**.
-3. On the API keys tab of the **Organization** page, click **Create API Key**.
-4. From the **Create API Key** page, you can configure your new key by adding a name, set expiration, or assign [roles](../users-roles/cloud-organization/user-roles.md).
+3. On the **API keys** tab of the **Organization** page, click **Create API key**.
+4. On the **Create API key** flyout, you can configure your new key by adding a name, set expiration, or assign [roles](../users-roles/cloud-organization/user-roles.md).
 
     By default, API keys expire after three months. You can set the expiration to a different preset value or to a specific date, up to one year. If you need the key to work indefinitely, you can also set its expiration to Never. In this case, the key won’t expire.
 
diff --git a/deploy-manage/cloud-organization/billing/add-billing-details.md b/deploy-manage/cloud-organization/billing/add-billing-details.md
index c81d9bae98..1cefe5a536 100644
--- a/deploy-manage/cloud-organization/billing/add-billing-details.md
+++ b/deploy-manage/cloud-organization/billing/add-billing-details.md
@@ -24,7 +24,7 @@ Trials get converted to paid subscriptions and billing starts when you add a cre
 To add your billing details:
 
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. Select the user icon on the header bar and select **Billing** from the menu.
+2. Select **Billing and Subscription** from the lower navigation menu or click the user icon on the header bar and select **Billing**.
 3. On the **Overview** page, select **Add billing information**.
 4. If prompted, complete the multifactor authentication (MFA) required by your bank.
 
diff --git a/deploy-manage/cloud-organization/billing/manage-subscription.md b/deploy-manage/cloud-organization/billing/manage-subscription.md
index 3dc1fb2d15..c615f28bb5 100644
--- a/deploy-manage/cloud-organization/billing/manage-subscription.md
+++ b/deploy-manage/cloud-organization/billing/manage-subscription.md
@@ -33,7 +33,7 @@ If, at any time during your monthly subscription with {{ecloud}}, you decide you
 To change your subscription level:
 
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. Select the user icon on the header bar and select **Billing** from the menu.
+2. Select **Billing and Subscription** from the lower navigation menu or click the user icon on the header bar and select **Billing**.
 3. On the **Overview** page, select **Update subscription**.
 4. Choose a new subscription level.
 5. Save your changes.
diff --git a/deploy-manage/cloud-organization/billing/monitor-analyze-usage.md b/deploy-manage/cloud-organization/billing/monitor-analyze-usage.md
index e8db7517c4..00785aaa98 100644
--- a/deploy-manage/cloud-organization/billing/monitor-analyze-usage.md
+++ b/deploy-manage/cloud-organization/billing/monitor-analyze-usage.md
@@ -26,8 +26,7 @@ You can check the detailed usage for a selected time range grouped either by pro
 To access your account usage:
 
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. Open the user menu in the header bar.
-3. Select **Billing** under the user menu.
+2. Select **Billing and Subscription** from the lower navigation menu or click the user icon on the header bar and select **Billing**.
 4. Go to the **Usage** page.
 
 ::::{important}
diff --git a/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md b/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md
index abc4e94f37..45b1574a4f 100644
--- a/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md
+++ b/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md
@@ -23,7 +23,7 @@ Operational contacts can only receive operational notifications, such as out-of-
 To update billing and operational contacts, or set an email address for monitoring alerts:
 
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. Select the user icon on the header bar and choose **Organization** from the menu.
+2. Select **Organization** from the lower navigation menu or click the user icon on the header bar and select **Organization**.
 3. On the **Contacts** page, specify your new contacts.
   
 You can specify multiple email addresses for each category. They become effective immediately and no further confirmation of the email addresses is required.
diff --git a/deploy-manage/cloud-organization/billing/view-billing-history.md b/deploy-manage/cloud-organization/billing/view-billing-history.md
index baaef39141..dd8692a91a 100644
--- a/deploy-manage/cloud-organization/billing/view-billing-history.md
+++ b/deploy-manage/cloud-organization/billing/view-billing-history.md
@@ -18,5 +18,5 @@ Information about outstanding payments and billing receipts is available from th
 To check your billing history:
 
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. Select the user icon on the header bar and choose **Billing** from the menu.
+2. Select **Billing and Subscription** from the lower navigation menu or click the user icon on the header bar and select **Billing**.
 3. On the **History** page, select the invoice number for a detailed PDF.
\ No newline at end of file
diff --git a/deploy-manage/deploy/elastic-cloud/aws-marketplace.md b/deploy-manage/deploy/elastic-cloud/aws-marketplace.md
index 4330a8fa79..fb5e4ee83e 100644
--- a/deploy-manage/deploy/elastic-cloud/aws-marketplace.md
+++ b/deploy-manage/deploy/elastic-cloud/aws-marketplace.md
@@ -27,7 +27,7 @@ Some differences exist when you subscribe to {{ecloud}} through the AWS Marketpl
 * Pricing is based on the AWS region, the size of your deployment, as well as some other parameters such as data transfer out, data transfer internode, snapshot storage, and snapshot APIs. For more details, check [Billing Dimensions](../../cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md).
 * The consolidated charges for your {{ecloud}} subscription display in the AWS Marketplace billing console. It can take a day or two before new charges show up.
 * Regardless of where your deployment is hosted (visible in the {{ecloud}} console), the AWS Marketplace charges for all AWS regions are metered in US East (Northern Virginia). As a result, US East (Northern Virginia) is listed as the region in the AWS Marketplace console.
-* To get a detailed breakdown of your charges by deployment or by product, open the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and go to **Account & Billing** > **Usage**.
+* To get a detailed breakdown of your charges by deployment or by product, open the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and from the user icon on the header bar, select **Billing** > **Usage**.
 * To end your trial or unsubscribe from the service, delete your deployment(s).
 * Elastic provides different [subscription levels](https://www.elastic.co/subscriptions/cloud). During your 7-day trial you will automatically have an Enterprise level subscription. After the trial you can choose the subscription level.
 
diff --git a/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md b/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md
index 65e9b32f80..aa31f2e4b0 100644
--- a/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md
+++ b/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md
@@ -107,8 +107,8 @@ Bundles
 You must upload your files before you can apply them to your cluster configuration:
 
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus.
-3. Under **Features**, select **Extensions**.
+2. Find your deployment on the home page and select **Manage**, or select your deployment from the **Hosted deployments** page.
+3. From the lower navigation menu, select **Extensions**.
 4. Select **Upload extension**.
 5. Complete the extension fields, including the {{es}} version.
 
diff --git a/deploy-manage/images/cloud-autoops-how-to-access.png b/deploy-manage/images/cloud-autoops-how-to-access.png
index f629a121fa..de58f68e86 100644
Binary files a/deploy-manage/images/cloud-autoops-how-to-access.png and b/deploy-manage/images/cloud-autoops-how-to-access.png differ
diff --git a/deploy-manage/images/cloud-ec-account-trust-management.png b/deploy-manage/images/cloud-ec-account-trust-management.png
deleted file mode 100644
index 7447a1e201..0000000000
Binary files a/deploy-manage/images/cloud-ec-account-trust-management.png and /dev/null differ
diff --git a/deploy-manage/images/cloud-es-health-page-table.png b/deploy-manage/images/cloud-es-health-page-table.png
deleted file mode 100644
index dacc627160..0000000000
Binary files a/deploy-manage/images/cloud-es-health-page-table.png and /dev/null differ
diff --git a/deploy-manage/images/cloud-es-health-page.png b/deploy-manage/images/cloud-es-health-page.png
deleted file mode 100644
index 27a219eecf..0000000000
Binary files a/deploy-manage/images/cloud-es-health-page.png and /dev/null differ
diff --git a/deploy-manage/images/cloud-es-monitoring-page-table.png b/deploy-manage/images/cloud-es-monitoring-page-table.png
new file mode 100644
index 0000000000..02b4a75c1b
Binary files /dev/null and b/deploy-manage/images/cloud-es-monitoring-page-table.png differ
diff --git a/deploy-manage/images/cloud-es-monitoring-page.png b/deploy-manage/images/cloud-es-monitoring-page.png
new file mode 100644
index 0000000000..8deb77f3ce
Binary files /dev/null and b/deploy-manage/images/cloud-es-monitoring-page.png differ
diff --git a/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md b/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md
index bf96c6daab..4fd9214024 100644
--- a/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md
+++ b/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md
@@ -17,10 +17,9 @@ AutoOps supports {{es}} versions according to the [supported {{stack}} versions]
 
 To access AutoOps from your {{ecloud}} console, follow these steps:
 
-1. Log in to your {{ech}} account. Use your credentials to access your {{ecloud}} dashboard.
-2. Navigate through your list of deployments and locate the one you want to manage.
-3. Click **Manage** on the right side of the selected deployment.
-4. On the deployment details page, click **Open AutoOps**.
+1. Log in to your {{ech}} account.
+2. Locate the deployment you want to work on and select **Manage**.
+4. On the deployment overview page, select **Open AutoOps**.
 
 :::{image} /deploy-manage/images/cloud-autoops-how-to-access.png
 :alt: How to access AutoOps
diff --git a/deploy-manage/monitor/cloud-health-perf.md b/deploy-manage/monitor/cloud-health-perf.md
index e8e7cdddb6..207f8775fe 100644
--- a/deploy-manage/monitor/cloud-health-perf.md
+++ b/deploy-manage/monitor/cloud-health-perf.md
@@ -20,22 +20,22 @@ These features augment [AutoOps](/deploy-manage/monitor/autoops.md) and [stack m
 
 Health is reported based on the following areas: Shard availability, master node health, Snapshot Lifecycle Management (SLM), Index Lifecycle Management (ILM), and repository integrity.
 
-The deployment **Health** page provides detailed information on health issues, impacted areas, and troubleshooting support.
+The deployment **Monitoring** page provides detailed information on health issues, impacted areas, and troubleshooting support.
 
 To view the health for a deployment:
 
 :::{include} ../_snippets/find-manage-deployment-ech-and-ece.md
 :::
 
-3. Under the deployment's name in the navigation menu, select **Health**.
+4. From the navigation menu, select **Monitoring**.
 
-The **Health** page provides the following information:
+The **Monitoring** page provides the following information:
 
 * Health issues for {{kib}}, Enterprise Search, APM, and plan changes are reported in the health banner.
-* Health issues for {{es}} clusters are broken down into a table with more details on Severity, Description and Affected capabilities.
+* Health issues for {{es}} clusters are broken down into a table with more details.
 
-:::{image} /deploy-manage/images/cloud-es-health-page.png
-:alt: {{es}} Health page
+:::{image} /deploy-manage/images/cloud-es-monitoring-page.png
+:alt: {{es}} Monitoring page
 :::
 
 * **Severity**: A critical issue impacts operations such as search and ingest and should be addressed as soon as possible. Warnings don’t impact the cluster immediately but might lead to more critical issues over time such as a corrupted repository might lead to no backups being available in the future. |
@@ -44,8 +44,8 @@ The **Health** page provides the following information:
 
 You can also search and filter the table based on affected resources, such as indices, repositories, nodes, or SLM policies. Individual issues can be further expanded to get more details and guided troubleshooting.
 
-:::{image} /deploy-manage/images/cloud-es-health-page-table.png
-:alt: {{es}} Health page with details and troubleshooting
+:::{image} /deploy-manage/images/cloud-es-monitoring-page-table.png
+:alt: {{es}} Expanded health issue with details and troubleshooting
 :::
 
 For more information about specific errors, refer to [](/troubleshoot/elasticsearch.md). You can also [contact us](/troubleshoot/index.md#contact-us) if you need more help.
@@ -79,7 +79,7 @@ deployment:
 
 {{ech}} deployments offer an additional **Performance** page to get further information about your cluster performance.
 
-If you observe issues on search and ingest operations in terms of increased latency or throughput for queries, these might not be directly reported on the **Health** page, unless they are related to shard health or master node availability.
+If you observe issues on search and ingest operations in terms of increased latency or throughput for queries, these might not be directly reported on the **Monitoring** page, unless they are related to shard health or master node availability.
 
 The **Performance** page and the out-of-the-box logs allow you to monitor your cluster performance, but for production applications we strongly recommend setting up a dedicated monitoring cluster. Refer to [Understanding deployment health](#ec-health-best-practices), for more guidelines on how to monitor you cluster performance.
 
diff --git a/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md b/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md
index c79f6ccb06..246dcb1275 100644
--- a/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md
+++ b/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md
@@ -67,9 +67,9 @@ If you need to update the permissions granted by a cross-cluster API key for a r
 
 1. On the deployment you will use as remote, use the [{{es}} API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-cross-cluster-api-key) or [{{kib}}](../api-keys/elasticsearch-api-keys.md) to create a cross-cluster API key with the appropriate permissions. Configure it with access to the indices you want to use for {{ccs}} or {{ccr}}.
 2. Copy the encoded key (`encoded` in the response) to a safe location. You will need it in the next steps.
-3. Go to the **Security** page of the local deployment and locate the **Remote connections** section.
+3. From the navigation menu, select **Security** and locate the **Remote connections** section.
 4. Locate the API key currently used for connecting to the remote cluster, copy its current alias, and delete it.
-5. Add the new API key by selecting **Add an API key**.
+5. Add the new API key by selecting **Add API key**.
 
     * For the **Setting name**, enter the same alias that was used for the previous key.
 
diff --git a/deploy-manage/remote-clusters/ec-enable-ccs.md b/deploy-manage/remote-clusters/ec-enable-ccs.md
index 66e2724a8e..5d0d5be6f1 100644
--- a/deploy-manage/remote-clusters/ec-enable-ccs.md
+++ b/deploy-manage/remote-clusters/ec-enable-ccs.md
@@ -65,7 +65,7 @@ For remote clusters configured using TLS certificate authentication, [traffic fi
 Traffic filtering for remote clusters supports 2 methods:
 
 * [Filtering by IP addresses and Classless Inter-Domain Routing (CIDR) masks](../security/ip-traffic-filtering.md)
-* Filtering by Organization or {{es}} cluster ID with a Remote cluster type filter. You can configure this type of filter from the **Features** > **Traffic filters** page of your organization or using the [{{ecloud}} RESTful API](https://www.elastic.co/docs/api/doc/cloud) and apply it from each deployment’s **Security** page.
+* Filtering by Organization or {{es}} cluster ID with a Remote cluster type filter. You can configure this type of filter from the **Security** > **Traffic filters** page of your organization or using the [{{ecloud}} RESTful API](https://www.elastic.co/docs/api/doc/cloud) and apply it from each deployment’s **Security** page.
 
 ::::{note}
 When setting up traffic filters for a remote connection to an {{ece}} environment, you also need to upload the region’s TLS certificate of the local cluster to the {{ece}} environment’s proxy. You can find that region’s TLS certificate in the **Security** page of any deployment of the environment initiating the remote connection.
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md
index e4bcc47851..0a8e981876 100644
--- a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md
+++ b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md
@@ -61,8 +61,8 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo
 
     On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
 
-3. From the deployment menu, select **Security**.
-4. Locate **Remote connections** and select **Add an API key**.
+3. From the navigation menu, select **Security**.
+4. Locate **Remote connections** and select **Add API key**.
 
     1. Add a setting:
 
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md
index 0f3998ff7d..4a4ee95798 100644
--- a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md
+++ b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md
@@ -61,8 +61,8 @@ The API key created previously will be used by the local deployment to authentic
 
     On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
 
-3. From the deployment menu, select **Security**.
-4. Locate **Remote connections** and select **Add an API key**.
+3. From the navigation menu, select **Security**.
+4. Locate **Remote connections** and select **Add API key**.
 
     1. Fill both fields.
 
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md
index e23b837848..9c99322932 100644
--- a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md
+++ b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md
@@ -61,8 +61,8 @@ The API key created previously will be used by the local deployment to authentic
 
     On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
 
-3. From the deployment menu, select **Security**.
-4. Locate **Remote connections** and select **Add an API key**.
+3. From the navigation menu, select **Security**.
+4. Locate **Remote connections** and select **Add API key**.
 
     1. Fill both fields.
 
@@ -84,16 +84,11 @@ If you later need to update the remote connection with different permissions, yo
 ::::::{tab-item} TLS certificate (deprecated)
 ### Set the default trust with other clusters in the same {{ecloud}} organization [ec_set_the_default_trust_with_other_clusters_in_the_same_elasticsearch_service_organization]
 
-By default, any deployment that you create trusts all other deployments in the same organization. You can change this behavior in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) under **Features** > **Trust**, so that when a new deployment is created it does not automatically trust any other deployment. You can choose one of the following options:
+By default, any deployment that you create trusts all other deployments in the same organization. To manage this behavior in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), go to **Trust management** from the lower navigation menu. You can choose one of the following options:
 
 * Trust all my deployments - All of your organization’s deployments created while this option is selected already trust each other. If you keep this option, that includes any deployments you’ll create in the future. You can directly jump to [Connect to the remote cluster](/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md#ec_connect_to_the_remote_cluster) to finalize the CCS or CCR configuration.
 * Trust no deployment - New deployments won’t trust any other deployment when they are created. You can instead configure trust individually for each of them in their security settings, as described in the next section.
 
-:::{image} /deploy-manage/images/cloud-ec-account-trust-management.png
-:alt: Trust management at the account Level
-:screenshot:
-:::
-
 ::::{note}
 * The level of trust of existing deployments is not modified when you change this setting. You must instead update the trust settings individually for each deployment you wish to change.
 * Deployments created before the {{ecloud}} February 2021 release trust only themselves. You have to update the trust setting for each deployment that you want to either use as a remote cluster or configure to work with a remote cluster.
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md
index 75ae3b3e8c..a6172ca5f3 100644
--- a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md
+++ b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md
@@ -61,8 +61,8 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo
 
     On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
 
-3. From the deployment menu, select **Security**.
-4. Locate **Remote connections** and select **Add an API key**.
+3. From the navigation menu, select **Security**.
+4. Locate **Remote connections** and select **Add API key**.
 
     1. Add a setting:
 
diff --git a/deploy-manage/security/_snippets/associate-filter.md b/deploy-manage/security/_snippets/associate-filter.md
index 79acbdaede..a5c5fc6719 100644
--- a/deploy-manage/security/_snippets/associate-filter.md
+++ b/deploy-manage/security/_snippets/associate-filter.md
@@ -1,3 +1,3 @@
 1. Go to the deployment.
-2. On the **Security** page, under **Traffic filters** select **Apply filter**.
+2. On the **Security** page, in the **Traffic filters** section, select **Apply filter**.
 3. Choose the filter you want to apply and select **Apply filter**.
\ No newline at end of file
diff --git a/deploy-manage/security/_snippets/create-filter.md b/deploy-manage/security/_snippets/create-filter.md
index 72cfe87c62..2554bf936f 100644
--- a/deploy-manage/security/_snippets/create-filter.md
+++ b/deploy-manage/security/_snippets/create-filter.md
@@ -1,4 +1,4 @@
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus.
-3. Under the **Features** tab, open the **Traffic filters** page.
+2. Find your deployment on the home page and select **Manage**, or select your deployment from the **Hosted deployments** page.
+3. From the lower navigation menu, select **Traffic filters**.
 4. Select **Create filter**.
\ No newline at end of file
diff --git a/deploy-manage/security/_snippets/delete-ruleset.md b/deploy-manage/security/_snippets/delete-ruleset.md
index 3cf7899c99..b6e16d99ce 100644
--- a/deploy-manage/security/_snippets/delete-ruleset.md
+++ b/deploy-manage/security/_snippets/delete-ruleset.md
@@ -3,6 +3,6 @@ If you need to remove a rule set, you must first remove any associations with de
 To delete a rule set with all its rules:
 
 1. [Remove any deployment associations](/deploy-manage/security/gcp-private-service-connect-traffic-filters.md#remove-filter-deployment).
-2. From the **Account** menu, select **Traffic filters**.
+2. From the lower navigation menu, select **Traffic filters**.
 3. Find the rule set you want to edit.
 4. Select the **Remove** icon. The icon is inactive if there are deployments assigned to the rule set.
\ No newline at end of file
diff --git a/deploy-manage/security/_snippets/edit-ruleset.md b/deploy-manage/security/_snippets/edit-ruleset.md
index fe7fc21024..c438fe9665 100644
--- a/deploy-manage/security/_snippets/edit-ruleset.md
+++ b/deploy-manage/security/_snippets/edit-ruleset.md
@@ -1,3 +1,3 @@
-1. From the **Account** menu, select **Traffic filters**.
+1. From the lower navigation menu, select **Traffic filters**.
 2. Find the rule set you want to edit.
 3. Select the **Edit** icon.
\ No newline at end of file
diff --git a/deploy-manage/security/_snippets/remove-filter.md b/deploy-manage/security/_snippets/remove-filter.md
index 5ee5f0b29b..fe84fc7a0a 100644
--- a/deploy-manage/security/_snippets/remove-filter.md
+++ b/deploy-manage/security/_snippets/remove-filter.md
@@ -1,4 +1,4 @@
 If you want to remove any traffic restrictions from a deployment or delete a rule set, you’ll need to remove any rule set associations first. To remove an association through the UI:
 
 1. Go to the deployment.
-2. On the **Security** page, under **Traffic filters** select **Remove**.
\ No newline at end of file
+2. On the **Security** page, in the **Traffic filters** section, select **Remove**.
\ No newline at end of file
diff --git a/deploy-manage/security/aws-privatelink-traffic-filters.md b/deploy-manage/security/aws-privatelink-traffic-filters.md
index f9fa308070..2dbd160800 100644
--- a/deploy-manage/security/aws-privatelink-traffic-filters.md
+++ b/deploy-manage/security/aws-privatelink-traffic-filters.md
@@ -230,17 +230,17 @@ Once you know your VPC endpoint ID you can create a private link traffic filter
 
 :::{include} _snippets/create-filter.md
 :::
-1. Select **Private link endpoint**.
-2. Create your rule set, providing a meaningful name and description.
-3. Select the region for the rule set.
-4. Enter your VPC endpoint ID.
-5. Select if this rule set should be automatically attached to new deployments.
+5. Under **Filter type**, select **Private link endpoint**.
+6. Create your rule set, providing a meaningful name and description.
+7. Select the region for the rule set.
+8. Enter your VPC endpoint ID.
+9. Select if this rule set should be automatically attached to new deployments.
 
     ::::{note}
     Each rule set is bound to a particular region and can be only assigned to deployments in the same region.
     ::::
 
-6.  (Optional) You can [claim your VPC endpoint ID](/deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md), so that no other organization is able to use it in a traffic filter ruleset.
+10.  (Optional) You can [claim your VPC endpoint ID](/deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md), so that no other organization is able to use it in a traffic filter ruleset.
 
 The next step is to [associate the rule set](/deploy-manage/security/aws-privatelink-traffic-filters.md#ec-associate-traffic-filter-private-link-rule-set) with your deployments.
 
@@ -291,7 +291,7 @@ The settings `xpack.fleet.agents.fleet_server.hosts` and `xpack.fleet.outputs` t
 
 ## Edit a PrivateLink connection [ec-edit-traffic-filter-private-link-rule-set]
 
-You can edit a rule set name or to change the VPC endpoint ID.
+You can edit a rule set name or change the VPC endpoint ID.
 
 :::{include} _snippets/edit-ruleset.md
 :::
diff --git a/deploy-manage/security/azure-private-link-traffic-filters.md b/deploy-manage/security/azure-private-link-traffic-filters.md
index f8331fb0b9..69dbd51a6d 100644
--- a/deploy-manage/security/azure-private-link-traffic-filters.md
+++ b/deploy-manage/security/azure-private-link-traffic-filters.md
@@ -133,7 +133,7 @@ The Private Link connection will be approved automatically after the traffic fil
 ::::
 
 
-1. From the **Account** menu, select **Traffic filters**.
+1. From the lower navigation menu, select **Traffic filters**.
 2. Select **Create filter**.
 3. Select **Private link endpoint**.
 4. Create your rule set, providing a meaningful name and description.
diff --git a/deploy-manage/security/gcp-private-service-connect-traffic-filters.md b/deploy-manage/security/gcp-private-service-connect-traffic-filters.md
index f4c9a29903..0245642e82 100644
--- a/deploy-manage/security/gcp-private-service-connect-traffic-filters.md
+++ b/deploy-manage/security/gcp-private-service-connect-traffic-filters.md
@@ -175,17 +175,17 @@ When you have your Private Service Connect endpoint connection ID, you can creat
 
 :::{include} _snippets/create-filter.md
 :::
-1. Select **Private Service Connect endpoint**.
-2. Create your rule set, providing a meaningful name and description.
-3. Select the region for the rule set.
-4. Enter your **PSC Connection ID**.
-5. Select if this rule set should be automatically attached to new deployments.
+5. Select **Private Service Connect endpoint**.
+6. Create your rule set, providing a meaningful name and description.
+7. Select the region for the rule set.
+8. Enter your **PSC Connection ID**.
+9. Select if this rule set should be automatically attached to new deployments.
 
     ::::{note}
     Each rule set is bound to a particular region and can be only assigned to deployments in the same region.
     ::::
 
-6. (Optional) You can [claim your PSC Connection ID](/deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md), so that no other organization is able to use it in a traffic filter ruleset.
+10. (Optional) You can [claim your PSC Connection ID](/deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md), so that no other organization is able to use it in a traffic filter ruleset.
 
 The next step is to [associate the rule set](/deploy-manage/security/aws-privatelink-traffic-filters.md#ec-associate-traffic-filter-private-link-rule-set) with your deployments.
 
diff --git a/deploy-manage/security/ip-filtering-cloud.md b/deploy-manage/security/ip-filtering-cloud.md
index 58c95240b6..69cec87b20 100644
--- a/deploy-manage/security/ip-filtering-cloud.md
+++ b/deploy-manage/security/ip-filtering-cloud.md
@@ -60,8 +60,8 @@ To create a rule set:
     :::{tab-item} {{ech}}
     :sync: ech
     1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-    2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus.
-    3. Under the **Features** tab, open the **Traffic filters** page.
+    2. Find your deployment on the home page and select **Manage**, or select your deployment from the **Hosted deployments** page.
+    3. From the lower navigation menu, select **Traffic filters**.
     :::
     :::{tab-item} {{ece}}
     :sync: ece
@@ -115,8 +115,8 @@ You can edit a rule set name or change the allowed traffic sources using IPv4, o
     :::{tab-item} {{ech}}
     :sync: ech
     1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-    2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus.
-    3. Under the **Features** tab, open the **Traffic filters** page.
+    2. Find your deployment on the home page and select **Manage**, or select your deployment from the **Hosted deployments** page.
+    3. From the lower navigation menu, select **Traffic filters**.
     :::
     :::{tab-item} {{ece}}
     :sync: ece
@@ -144,8 +144,8 @@ To delete a rule set with all its rules:
     :::{tab-item} {{ech}}
     :sync: ech
     1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-    2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus.
-    3. Under the **Features** tab, open the **Traffic filters** page.
+    2. Find your deployment on the home page and select **Manage**, or select your deployment from the **Hosted deployments** page.
+    3. From the lower navigation menu, select **Traffic filters**.
     :::
     :::{tab-item} {{ece}}
     :sync: ece
@@ -154,5 +154,5 @@ To delete a rule set with all its rules:
     :::
     ::::
 
-3. Find the rule set you want to edit.
+3. Find the rule set you want to delete.
 4. Select the **Delete** icon. The icon is inactive if there are deployments assigned to the rule set.
\ No newline at end of file
diff --git a/deploy-manage/security/traffic-filtering.md b/deploy-manage/security/traffic-filtering.md
index 56b3b33782..059e8b3dd6 100644
--- a/deploy-manage/security/traffic-filtering.md
+++ b/deploy-manage/security/traffic-filtering.md
@@ -81,7 +81,7 @@ This section offers suggestions on how to manage and analyze the impact of your
 
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) or [Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
 2. On the **Deployments** page, select your deployment.
-3. Select the **Security** tab on the left-hand side menu bar.
+3. Select **Security** from the navigation menu.
 
 Traffic filter rule sets are listed under **Traffic filters**.
 
@@ -98,12 +98,12 @@ To identify which rule sets are automatically applied to new deployments in your
     :::{tab-item} {{ech}}
     :sync: ech
     1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-    2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus.
-    3. Under the **Features** tab, open the **Traffic filters** page.
+    2. Find your deployment on the home page and select **Manage**, or select your deployment from the **Hosted deployments** page.
+    3. From the lower navigation menu, select **Traffic filters**.
     :::
     :::{tab-item} {{ece}}
     :sync: ece
-    4. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
+    4. [Log in to the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
     5. From the **Platform** menu, select **Security**.
     :::
     ::::
diff --git a/deploy-manage/stack-settings.md b/deploy-manage/stack-settings.md
index 9877c6fa78..9803cd0843 100644
--- a/deploy-manage/stack-settings.md
+++ b/deploy-manage/stack-settings.md
@@ -73,10 +73,10 @@ For {{ech}} and {{ece}} deployments, you edit {{stack}} settings through the {{e
 
 :::{include} /deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md
 :::
-1. Under the deployment's name in the navigation menu, select **Edit**.
-2. Look for the **Manage user settings and extensions** and **Edit user settings** links for each deployment, and select the one corresponding to the component you want to update, such as {{es}} or {{kib}}.
-3. Apply the necessary settings in the **Users Settings** tab of the editor and select **Back** when finished.
-4. Select **Save** to apply the changes to the deployment. Saving your changes initiates a configuration plan change that restarts the affected components for you.
+4. Under the deployment's name in the navigation menu, select **Edit**.
+5. Look for the **Manage user settings and extensions** and **Edit user settings** links for each deployment, and select the one corresponding to the component you want to update, such as {{es}} or {{kib}}.
+6. Apply the necessary settings in the **Users Settings** tab of the editor and select **Back** when finished.
+7. Select **Save** to apply the changes to the deployment. Saving your changes initiates a configuration plan change that restarts the affected components for you.
 
 For further details and examples, refer to the resource for your deployment type: 
 
diff --git a/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md b/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md
index 531a60307c..0bc9655ac4 100644
--- a/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md
+++ b/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md
@@ -27,13 +27,14 @@ For deployments with **{{stack}} version 7.17 and earlier**, you’ll need to en
 2. Upload the plugin to your deployment:
 
     1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-    2. Open the **Features > Extensions** page and select **Upload extension**.
-    3. Specify the plugin name (`repository-azure`) and the version.
-    4. Select **An installable plugin (Compiled, no source code)**.
-    5. Select **Create extension**.
-    6. Navigate back to the **Features > Extensions** page.
-    7. Select the extension name.
-    8. Drag and drop to upload the `repository-azure` plugin zip file.
+    2. Go to your deployment.
+    3. From the lower navigation menu, select **Extensions** and then select **Upload extension**.
+    4. Specify the plugin name (`repository-azure`) and version.
+    5. Select **An installable plugin (compiled, no source code)**.
+    6. Select **Create extension**.
+    7. Navigate back to the **Extensions** page.
+    8. Select the extension name.
+    9. Drag and drop to upload the `repository-azure` plugin zip file.
 
 
 
diff --git a/deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md b/deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md
index 9f180cb034..e00d6a8902 100644
--- a/deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md
+++ b/deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md
@@ -40,13 +40,14 @@ For deployments with **{{stack}} version 7.17 and earlier**, you’ll need to en
 2. Upload the plugin to your deployment:
 
     1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-    2. Open the **Features > Extensions** page and select **Upload extension**.
-    3. Specify the plugin name (`repository-gcs`) and the version.
-    4. Select **An installable plugin (Compiled, no source code)**.
-    5. Select **Create extension**.
-    6. Navigate back to the **Features > Extensions** page.
-    7. Select the extension name.
-    8. Drag and drop to upload the `repository-gcs` plugin zip file.
+    2. Go to your deployment.
+    3. From the lower navigation menu, select **Extensions** and then select **Upload extension**.
+    4. Specify the plugin name (`repository-gcs`) and version.
+    5. Select **An installable plugin (compiled, no source code)**.
+    6. Select **Create extension**.
+    7. Navigate back to the **Extensions** page.
+    8. Select the extension name.
+    9. Drag and drop to upload the `repository-gcs` plugin zip file.
 
 
 
diff --git a/deploy-manage/users-roles/cloud-organization/manage-users.md b/deploy-manage/users-roles/cloud-organization/manage-users.md
index 46b4853775..06c1a2e14e 100644
--- a/deploy-manage/users-roles/cloud-organization/manage-users.md
+++ b/deploy-manage/users-roles/cloud-organization/manage-users.md
@@ -32,7 +32,7 @@ If you're using {{ech}}, then you can also manage users and control access [at t
 
 To invite users to your organization:
 
-1. Go to the user icon on the header bar and select **Organization**.
+1. Select **Organization** from the lower navigation menu or click the user icon on the header bar and select **Organization**.
 2. On the **Members** page, click **Invite members**.
 3. Enter the email addresses of the users you want to invite in the textbox.
 
diff --git a/deploy-manage/users-roles/cloud-organization/user-roles.md b/deploy-manage/users-roles/cloud-organization/user-roles.md
index 01f91ee720..f803bd8545 100644
--- a/deploy-manage/users-roles/cloud-organization/user-roles.md
+++ b/deploy-manage/users-roles/cloud-organization/user-roles.md
@@ -28,7 +28,7 @@ On this page, you'll learn the following:
 
 To edit the roles assigned to a user:
 
-1. Go to the user icon on the header bar and select **Organization**.
+1. Select **Organization** from the lower navigation menu or click the user icon on the header bar and select **Organization**.
 2. Find the user on the **Members** tab of the **Organization** page. Click the member name to view their roles.
 3. Click **Edit roles** to change the user's roles.
 
diff --git a/troubleshoot/monitoring/node-bootlooping.md b/troubleshoot/monitoring/node-bootlooping.md
index cbed40c23f..a6a4dceac0 100644
--- a/troubleshoot/monitoring/node-bootlooping.md
+++ b/troubleshoot/monitoring/node-bootlooping.md
@@ -135,7 +135,7 @@ Noting in example that the bundle’s expiration `X-Amz-Date=20241016T133214Z` i
 
 To view any added plugins or bundles:
 
-1. Go to the **Features** page and open the **Extensions** tab.
+1. From your deployment's lower navigation menu, select **Extensions**.
 2. Select any extension and then choose **Update extension** to renew it. No other changes are needed, and any associated configuration change failures should now be able to succeed.