Revert changes related to Elastic Stack

Author: lcawl

deploy-manage/deploy.md

@@ -89,9 +89,6 @@ Consider this when choosing your deployment type:
 - Choose {{serverless-full}} if you want automatic access to the latest features and don't want to manage version compatibility
 - Choose other deployment types if you need more control over version management
 
-:::{include} /deploy-manage/deploy/_snippets/stack-version-compatibility.md
-:::
-
 :::{tip}
 Learn more about [versioning and availability](/get-started/versioning-availability.md).
 :::

deploy-manage/deploy/cloud-on-k8s/kibana-instance-quickstart.md

@@ -11,7 +11,7 @@ products:
 
 # Deploy a {{kib}} instance [k8s-deploy-kibana]
 
-To deploy a simple {{kib}} specification, with one {{kib}} instance:
+To deploy a simple [{{kib}}](/get-started/the-stack.md#stack-components-kibana) specification, with one {{kib}} instance:
 
 1. Specify a {{kib}} instance and associate it with your {{es}} `quickstart` cluster created previously under [Deploying an {{es}} cluster](elasticsearch-deployment-quickstart.md):
 

deploy-manage/deploy/self-managed.md

@@ -29,11 +29,6 @@ Self-hosted options:
 For a comparison of these deployment options, refer to [Choosing your deployment type](/deploy-manage/deploy.md#choosing-your-deployment-type) and [](/deploy-manage/deploy/deployment-comparison.md).
 :::
 
-## Installation order
-
-:::{include} /deploy-manage/deploy/_snippets/installation-order.md
-:::
-
 ## Section overview
 
 This section focuses on deploying {{es}} and {{kib}} without an orchestrator.

deploy-manage/deploy/self-managed/_snippets/install-next-steps.md

@@ -6,7 +6,7 @@ You now have a test {{es}} environment set up. Before you start serious developm
 
 You can also do the following:
 
-* Consider installing [additional {{stack}} components](/get-started/search-ai-platform.md).
+* Consider installing [additional {{stack}} components](/get-started/the-stack.md).
 * Learn how to [ingest data into {{es}}](/manage-data/index.md).
 * Learn about [production considerations](/deploy-manage/production-guidance.md).
 * Explore [other topics](/deploy-manage/deploy/self-managed.md#other-important-sections) to learn how to secure and manage your cluster.

deploy-manage/deploy/self-managed/_snippets/ports.md

@@ -10,4 +10,4 @@ These settings can be overridden in the relevant configuration file.
 | 9300 and onwards | TCP |	Transport API. Used for intra-cluster communications and client access via the transport API (Java client). | Elasticsearch [`transport.port`](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md#common-network-settings) |
 | 5601 | HTTP |	{{kib}} default access port. | Kibana [`server.port`](kibana://reference/configuration-reference/general-settings.md#server-port) |
 
-Additional ports might be required for [optional {{stack}} components](/get-started/search-ai-platform.md). Refer to the installation guide for the component that you want to install.
+Additional ports might be required for [optional {{stack}} components](/get-started/the-stack.md). Refer to the installation guide for the component that you want to install.

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

@@ -109,7 +109,7 @@ The alert cleanup task permanently deletes alerts in your `.alert-*` indices. Ma
 
 Remove old or rarely-accessed alerts in your space by running an alert cleanup task, which deletes alerts according to the criteria that you define. Alerts that are attached to cases are not deleted. 
 
-1. Open the **Rules** page by going to **Stack Management > Alerts and Insights > Rules** in the main menu or using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+1. Open the **Rules** page by going to **Stack Management > Alerts and Insights > Rules** in the main menu or using the global search field.
 2. Click **Settings** to open the settings for all rules in the space.
 3. In the **Clean up alert history** section, click **Clean up**.
 4. Define criteria for the alert cleanup task. You can choose to delete alerts that are active or inactive and meet a certain age.

explore-analyze/query-filter/aggregations/tutorial-analyze-ecommerce-data-with-aggregations-using-query-dsl.md

@@ -34,7 +34,7 @@ You’ll need:
 
 2. The [sample eCommerce data](../../index.md#gs-get-data-into-kibana) loaded into {{es}}. To load sample data follow these steps in your UI:
 
-    * Open the **Integrations** pages by searching in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+    * Open the **Integrations** pages by searching in the global search field.
     * Search for `sample data` in the **Integrations** search field.
     * Open the **Sample data** page.
     * Select the **Other sample data sets** collapsible.

get-started/howto-use-the-docs.md

@@ -27,7 +27,7 @@ Because Elastic products can be deployed in different ways (like on {{ecloud}} o
 These badges appear at the top of a page or section and tell you which products, deployment models, and versions the content applies to. They also indicate the maturity level of a feature, such as **beta**, **technical preview**, or **generally available (GA)**. This system ensures that you can identify content specific to your environment and version.
 
 :::{tip}
-An {{stack}} badge indicates that a page applies to [{{search-platform}}](/get-started/search-ai-platform.md) components across all deployment options except {{serverless-full}}. If a page applies to all deployment options, it will have both {{serverless-short}} and Stack badges.
+An {{stack}} badge indicates that a page applies to [{{stack}}](/get-started/the-stack.md) components across all deployment options except {{serverless-full}}. If a page applies to all deployment options, it will have both {{serverless-short}} and Stack badges.
 :::
 
 ## Page options
@@ -56,7 +56,7 @@ We clearly mark content added or changed in a specific version using availabilit
 
 This means the feature is:
 
-* Generally Available (GA) in the [{{search-platform}}](/get-started/search-ai-platform.md) across all deployment options except {{serverless-full}}
+* Generally Available (GA) in the [{{stack}}](/get-started/the-stack.md) across all deployment options except {{serverless-full}}
 * Introduced in version 9.1.0
 
 :::{tip}