case consistency for console

Author: florent-leborgne

explore-analyze/alerts-cases/alerts/notifications-domain-allowlist.md

@@ -24,7 +24,7 @@ Changes to the allowlist do not take effect immediately. After saving your chang
 
 ### Using the UI [using-the-ui]
 
-1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
+1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
 2. Select a deployment.
 3. From your deployment menu, go to the **Edit** page.
 4. Select **Save**.

explore-analyze/alerts-cases/watcher/enable-watcher.md

@@ -28,7 +28,7 @@ You can configure notifications similar to the [operational emails](../../../dep
 
 Watcher in Elastic Cloud is preconfigured with an email service and can be used without any additional configuration. Alternatively, a custom mail server can be configured as described in [Configuring a custom mail server](#watcher-custom-mail-server)
 
-You can optionally add [HTML sanitization](../../../explore-analyze/alerts-cases/watcher/actions-email.md#email-html-sanitization) settings under [Elasticsearch User settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) in the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body) so that HTML elements are sanitized in the email notification.
+You can optionally add [HTML sanitization](../../../explore-analyze/alerts-cases/watcher/actions-email.md#email-html-sanitization) settings under [Elasticsearch User settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) so that HTML elements are sanitized in the email notification.
 
 For more information on sending alerts by email, check [Email action](../../../explore-analyze/alerts-cases/watcher/actions-email.md).
 

explore-analyze/query-filter/languages/sql-odbc-setup.md

@@ -108,7 +108,7 @@ This tab allows configuration for the following items:
 
 * Cloud ID
 
-  The *Cloud ID* is a string that simplifies the configuration when connecting to {{ecloud}}. It encodes the connection parameters to that cluster. You can obtain it from from your deployment's details in the {{ecloud}} console.
+  The *Cloud ID* is a string that simplifies the configuration when connecting to {{ecloud}}. It encodes the connection parameters to that cluster. You can obtain it from from your deployment's details in the {{ecloud}} Console.
 
   ::::{note}
   When this field is provisioned, the *Hostname*, *Port* and the security settings are provisioned as well and their respective inputs disabled.

solutions/observability/apps/secret-token.md

@@ -27,7 +27,7 @@ Secret tokens are not applicable for the RUM Agent, as there is no way to preven
 ## Create a secret token [apm-create-secret-token]
 
 ::::{note}
-{{ech}} and {{ece}} deployments provision a secret token when the deployment is created. The secret token can be found and reset in the {{ecloud}} console under **Deployments** — **APM & Fleet**.
+{{ech}} and {{ece}} deployments provision a secret token when the deployment is created. The secret token can be found and reset in the {{ecloud}} Console under **Deployments** — **APM & Fleet**.
 ::::
 
 

solutions/observability/apps/switch-an-elastic-cloud-cluster-to-apm-integration.md

@@ -17,7 +17,7 @@ mapped_pages:
 
 ## Upgrade the {{stack}} [apm-integration-upgrade-ess-1]
 
-Use the {{ecloud}} console to upgrade the {{stack}} to version 9.0.0-beta1. See the [Upgrade guide](../../../deploy-manage/upgrade/deployment-or-cluster.md) for details.
+Use the {{ecloud}} Console to upgrade the {{stack}} to version 9.0.0-beta1. See the [Upgrade guide](../../../deploy-manage/upgrade/deployment-or-cluster.md) for details.
 
 
 ## Switch to {{agent}} [apm-integration-upgrade-ess-2]
@@ -53,7 +53,7 @@ In {{kib}}, navigate to **Management** > **Fleet***. Select the ***Elastic Cloud
 
 Certain {{es}} output configuration options are not available with the APM integration. To ensure data is not lost, you can scale APM and {{fleet}} up and out. APM’s capacity to process events increases with the instance memory size.
 
-Go to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body), select your deployment and click **Edit**. Here you can edit the number and size of each availability zone.
+Go to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), select your deployment and click **Edit**. Here you can edit the number and size of each availability zone.
 
 :::{image} ../../../images/observability-scale-apm.png
 :alt: scale APM

solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md

@@ -547,7 +547,7 @@ Think of a latency spike — APM can help you narrow the scope of your inves
 
 Application monitoring data is streamed from your applications running in Kubernetes to APM, where it is validated, processed, and transformed into {{es}} documents.
 
-There are many ways to deploy APM when working with Kubernetes, but this guide assumes that you’re using an {{ech}} deployment. If you haven’t done so already, enable APM in the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
+There are many ways to deploy APM when working with Kubernetes, but this guide assumes that you’re using an {{ech}} deployment. If you haven’t done so already, enable APM in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
 
 If you want to manage APM yourself, there are a few alternative options:
 

solutions/observability/infra-and-hosts/upgrade-universal-profiling.md

@@ -29,7 +29,7 @@ To upgrade from version 8.10 or later, you need to:
 1. Perform a stack upgrade in {{ecloud}}
 
 
-### Perform a stack upgrade in the {{ecloud}} console [profiling-upgrade-in-cloud]
+### Perform a stack upgrade in the {{ecloud}} Console [profiling-upgrade-in-cloud]
 
 To perform a stack upgrade in {{ecloud}}: