fix instances with other patterns

Author: shainaraskas

deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md

@@ -298,7 +298,7 @@ $$$azure-integration-whats-included$$$What is included in my {{ecloud}} deployme
 :   Each {{ecloud}} deployment includes:
 
     * An {{es}} cluster
-    * A {{kib}} instance which provides data visualization and a front-end for the {stack}
+    * A {{kib}} instance which provides data visualization and a front-end for the {{stack}}
     * An APM server that allows you to easily collect application traces
     * An {{ents}} instance that allows you to easily build a search experience with an intuitive interface
 

deploy-manage/deploy/self-managed/configure-elasticsearch.md

@@ -14,7 +14,7 @@ The configuration files should contain settings which are node-specific (such as
 
 {{es}} has three configuration files:
 
-* `elasticsearch.yml` for configuring {es}
+* `elasticsearch.yml` for configuring {{es}}
 * `jvm.options` for configuring {{es}} JVM settings
 * `log4j2.properties` for configuring {{es}} logging
 

deploy-manage/monitor/monitoring-data/kibana-alerts.md

@@ -15,7 +15,7 @@ applies:
 The {{stack}} {{monitor-features}} provide [Alerting rules](../../../explore-analyze/alerts-cases/alerts.md) out-of-the box to notify you of potential issues in the {{stack}}. These rules are preconfigured based on the best practices recommended by Elastic. However, you can tailor them to meet your specific needs.
 
 :::{image} ../../../images/kibana-monitoring-kibana-alerting-notification.png
-:alt: {{kib}} alerting notifications in {stack-monitor-app}
+:alt: {{kib}} alerting notifications in {{stack-monitor-app}}
 :class: screenshot
 :::
 

deploy-manage/remote-clusters/ece-enable-ccs.md

@@ -13,7 +13,7 @@ These remote clusters could be:
 
 * Another {{es}} cluster of your ECE installation
 * An {{es}} cluster in a remote ECE installation
-* An {{es}} cluster hosted on {ecloud}
+* An {{es}} cluster hosted on {{ecloud}}
 * Any other self-managed {{es}} cluster
 
 

deploy-manage/security/set-up-basic-security-plus-https.md

@@ -219,7 +219,7 @@ Typically, you need to create the following separate roles:
 
 * **setup** role for setting up index templates and other dependencies
 * **monitoring** role for sending monitoring information
-* **writer** role for publishing events collected by {metricbeat}
+* **writer** role for publishing events collected by {{metricbeat}}
 * **reader** role for Kibana users who need to view and create visualizations that access {{metricbeat}} data
 
 ::::{note}

deploy-manage/tools/snapshot-and-restore/searchable-snapshots.md

@@ -173,7 +173,7 @@ A snapshot of a {{search-snap}} index contains only a small amount of metadata w
 
 Because {{search-snap}} indices are not regular indices, it is not possible to use a [source-only repository](source-only-repository.md) to take snapshots of {{search-snap}} indices.
 
-::::{admonition} Reliability of {search-snaps}
+::::{admonition} Reliability of {{search-snaps}}
 :class: warning
 
 :name: searchable-snapshots-reliability

deploy-manage/users-roles/cluster-or-deployment-auth/elasticsearch-privileges.md

@@ -234,7 +234,7 @@ This section lists the privileges that you can assign to a role.
 
 
 `read_ilm`
-:   All read-only {{Ilm}} operations, such as getting policies and checking the status of {Ilm}
+:   All read-only {{Ilm}} operations, such as getting policies and checking the status of {{Ilm}}
 
     This privilege is not available in {{serverless-full}}.
 

explore-analyze/alerts-cases/alerts/alerting-getting-started.md

@@ -114,7 +114,7 @@ This section will clarify some of the important differences in the function and
 
 Functionally, the {{alert-features}} differ in that:
 
-* Scheduled checks are run on {{kib}} instead of {es}
+* Scheduled checks are run on {{kib}} instead of {{es}}
 * {{kib}} [rules hide the details of detecting conditions](../../../explore-analyze/alerts-cases/alerts/alerting-getting-started.md#alerting-concepts-conditions) through rule types, whereas watches provide low-level control over inputs, conditions, and transformations.
 * {{kib}} rules track and persist the state of each detected condition through alerts. This makes it possible to mute and throttle individual alerts, and detect changes in state such as resolution.
 * Actions are linked to alerts. Actions are fired for each occurrence of a detected condition, rather than for the entire rule.

explore-analyze/alerts-cases/cases/manage-cases.md

@@ -16,7 +16,7 @@ Open a new case to keep track of issues and share their details with colleagues.
 
 1. Go to **Management > {{stack-manage-app}} > Cases**, then click **Create case**.
    :::{image} ../../../images/kibana-cases-create.png
-   :alt: Create a case in {stack-manage-app}
+   :alt: Create a case in {{stack-manage-app}}
    :class: screenshot
    :::
 

explore-analyze/find-and-organize/reports.md

@@ -15,7 +15,7 @@ For example, in **Discover**, you can create and download comma-separated values
 To view and manage reports, go to **Management** > **Reporting**.
 
 :::{image} ../../images/serverless-reports-management.png
-:alt: {reports-app}
+:alt: {{reports-app}}
 :class: screenshot
 :::