also stack"

Author: shainaraskas

deploy-manage/_snippets/deployment-options-overview.md

@@ -1,7 +1,7 @@
 **Quick start options**
 
 * [**{{ecloud}}**](/deploy-manage/deploy/elastic-cloud.md): Get a hosted solution up and running in minutes.
-   * [**{{ech}}**](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md): Our hosted Elastic Stack offering, deployed in the cloud with your provider of choice. Sign up for a [14-day free trial](https://cloud.elastic.co/registration).
+   * [**{{ech}}**](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md): Our hosted {{stack}} offering, deployed in the cloud with your provider of choice. Sign up for a [14-day free trial](https://cloud.elastic.co/registration).
    * [**{{serverless-full}}**](/deploy-manage/deploy/elastic-cloud/serverless.md): Create serverless projects for autoscaled and fully managed Elastic deployments. Sign up for a [14-day free trial](https://cloud.elastic.co/serverless-registration).
 * [**Local development**](/solutions/search/run-elasticsearch-locally.md): Get started quickly with {{es}} and {{kib}} in Docker for local development and testing.
 

deploy-manage/api-keys/elasticsearch-api-keys.md

@@ -9,7 +9,7 @@ mapped_pages:
 
 Several types of {{es}} API keys exist:
 
-* **Personal/User** API key: allows external services to access the Elastic Stack on behalf of a user.
+* **Personal/User** API key: allows external services to access the {{stack}} on behalf of a user.
 * **Cross-cluster** API key: allows other clusters to connect to this cluster.
 * **Managed** API key: created and managed by {{kib}} to run background tasks.
 

deploy-manage/deploy/cloud-enterprise/ce-add-support-for-node-roles-autoscaling.md

@@ -17,7 +17,7 @@ System owned deployment templates are automatically updated during the ECE upgra
 
 ## Adding support for node_roles [ece_adding_support_for_node_roles]
 
-The `node_roles` field defines the roles that an {{es}} topology element can have, which is used in place of `node_type` when a new feature such as autoscaling is enabled, or when a new data tier is added. This field is supported on [Elastic stack versions 7.10 and above](cloud://reference/cloud-enterprise/changes-to-index-allocation-api.md).
+The `node_roles` field defines the roles that an {{es}} topology element can have, which is used in place of `node_type` when a new feature such as autoscaling is enabled, or when a new data tier is added. This field is supported on [{{stack}} versions 7.10 and above](cloud://reference/cloud-enterprise/changes-to-index-allocation-api.md).
 
 There are a number of fields that need to be added to each {{es}} node in order to support `node_roles`:
 
@@ -757,7 +757,7 @@ After adding support for `node_roles`, the resulting deployment template should
 
 ## Adding support for autoscaling [ece_adding_support_for_autoscaling]
 
-After adding support for `node_roles` we can then update the template to support autoscaling. Autoscaling is used to automatically adjust the available resources in the deployments. Currently, this feature is available for {{es}} data tiers and machine learning node in [Elastic stack versions 7.11 and above](../../autoscaling.md).
+After adding support for `node_roles` we can then update the template to support autoscaling. Autoscaling is used to automatically adjust the available resources in the deployments. Currently, this feature is available for {{es}} data tiers and machine learning node in [{{stack}} versions 7.11 and above](../../autoscaling.md).
 
 There are a number of autoscaling fields that need to be added in order to support autoscaling:
 
@@ -1736,7 +1736,7 @@ Having added support for `node_roles` and autoscaling to your custom template, i
 
 After the template is updated, you can start [creating new deployments](create-deployment.md) or [migrating existing ones to `node_roles`](#ece-migrating-a-deployment-to-node-roles).
 
-Although `node_roles` and autoscaling are only available in more recent Elastic stack versions, an updated template can still be used with deployments that have versions below 7.10. In these cases, the data tiers and autoscaling features will only take effect once the deployment is upgraded to versions 7.10 and 7.11, respectively.
+Although `node_roles` and autoscaling are only available in more recent {{stack}} versions, an updated template can still be used with deployments that have versions below 7.10. In these cases, the data tiers and autoscaling features will only take effect once the deployment is upgraded to versions 7.10 and 7.11, respectively.
 
 
 ## Migrating a deployment to `node_roles` [ece-migrating-a-deployment-to-node-roles]

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

@@ -8,7 +8,7 @@ mapped_pages:
 
 # Configure allocator affinity [ece-configuring-allocator-affinity]
 
-One of the benefits of the ECE platform is its robust deployment instance distribution logic that maximizes the utilization of the underlying resources you deploy the Elastic Stack on. In ECE 2.4 and later, you can customize how Elastic Stack deployments get distributed across the available set of allocators in your ECE installation, which is known as *allocator affinity*.
+One of the benefits of the ECE platform is its robust deployment instance distribution logic that maximizes the utilization of the underlying resources you deploy the {{stack}} on. In ECE 2.4 and later, you can customize how {{stack}} deployments get distributed across the available set of allocators in your ECE installation, which is known as *allocator affinity*.
 
 
 ## Before you begin [ece_before_you_begin_6] 

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

@@ -8,18 +8,18 @@ mapped_pages:
 
 # Manage deployment templates [ece-configuring-ece-templates]
 
-Deployment templates combine components of the Elastic Stack, such as {{es}} nodes and {{kib}} instances, for different use cases. Compared to a one-size-fits-all approach to deploying the Elastic Stack, templates provide much greater flexibility and ensure that your deployments have the resources they need to support your use cases. To make the most of deployment templates, you must configure ECE for them.
+Deployment templates combine components of the {{stack}}, such as {{es}} nodes and {{kib}} instances, for different use cases. Compared to a one-size-fits-all approach to deploying the {{stack}}, templates provide much greater flexibility and ensure that your deployments have the resources they need to support your use cases. To make the most of deployment templates, you must configure ECE for them.
 
 After installing or upgrading to ECE version 2.0 or later:
 
-1. [Tag your allocators](ece-configuring-ece-tag-allocators.md) to tell ECE what kind of hardware you have available for Elastic Stack deployments.
-2. [Edit the default instance configurations](ece-configuring-ece-instance-configurations-edit.md) to match components of the Elastic Stack to your tagged allocators.
+1. [Tag your allocators](ece-configuring-ece-tag-allocators.md) to tell ECE what kind of hardware you have available for {{stack}} deployments.
+2. [Edit the default instance configurations](ece-configuring-ece-instance-configurations-edit.md) to match components of the {{stack}} to your tagged allocators.
 
-If you do not perform these steps, {{ece}} will behave just as it did in versions before 2.0 and deploy the Elastic Stack wherever there is space on allocators.
+If you do not perform these steps, {{ece}} will behave just as it did in versions before 2.0 and deploy the {{stack}} wherever there is space on allocators.
 
 Have a use case that isn’t addressed by the ECE default templates? You can also:
 
-* [Create your own instance configurations](ece-configuring-ece-instance-configurations-create.md) to match components of the Elastic Stack to allocators, tailoring what resources they get and what sizes they support.
+* [Create your own instance configurations](ece-configuring-ece-instance-configurations-create.md) to match components of the {{stack}} to allocators, tailoring what resources they get and what sizes they support.
 * [Create your own deployment templates](ece-configuring-ece-create-templates.md) to solve your own use cases better.
 
 
@@ -31,10 +31,10 @@ Allocator tag
 :   Indicates what kind of hardware resources you have available. Used by instance configurations to find suitable allocators.
 
 Instance configuration
-:   Matches components of the Elastic Stack to allocators for deployment and tailors how memory and storage resources get sized relative to each other, and what sizes are available. Used as a building block for deployment templates.
+:   Matches components of the {{stack}} to allocators for deployment and tailors how memory and storage resources get sized relative to each other, and what sizes are available. Used as a building block for deployment templates.
 
 Deployment template
-:   Solves a specific use case with the Elastic Stack, such as a search or a logging use case. ECE provides some deployment templates out of the box to get you started, or you can create your own.
+:   Solves a specific use case with the {{stack}}, such as a search or a logging use case. ECE provides some deployment templates out of the box to get you started, or you can create your own.
 
 
 

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

@@ -16,7 +16,7 @@ Now that you have {{ece}} up and running, take a look at some of the additional
 * [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) – Define the resources, topology, hardware, and configurations that will be applied to your deployments.
-* [Manage Elastic Stack versions](./manage-elastic-stack-versions.md) - Upload or remove Elastic Stack packs.
+* [Manage {{stack}} versions](./manage-elastic-stack-versions.md) - Upload or remove {{stack}} packs.
 * [Change the ECE API URL](./change-ece-api-url.md) - Configure the HTTPS URL used to access the ECE API.
 * [Change endpoint URLs](change-endpoint-urls.md) - Configure the URLs to access {{es}} and {{kib}} deployments to match your [domain name](./ece-wildcard-dns.md) and [proxy certificate](../../security/secure-your-elastic-cloud-enterprise-installation/manage-security-certificates.md).
 * [Enable custom endpoint aliases](./enable-custom-endpoint-aliases.md) - This feature allows to use aliases in the endpoint URLs instead of cluster UUIDs.
@@ -30,7 +30,7 @@ Other sections of the documentation describe important ECE features to consider:
 
 ## Advanced configuration procedures
 
-* [Configure allocator affinity](configure-allocator-affinity.md) - Determine how ECE distributes your Elastic Stack deployments across allocators.
+* [Configure allocator affinity](configure-allocator-affinity.md) - Determine how ECE distributes your {{stack}} deployments across allocators.
 * [Change allocator disconnect timeout](change-allocator-disconnect-timeout.md) - Configure how long ECE waits before considering allocators to be disconnected.
 * [Migrate ECE to Podman hosts](./migrate-ece-to-podman-hosts.md) - If you are running a Docker based installation and you need to migrate to Podman.
 * [Migrate ECE on Podman hosts to SELinux in enforcing mode](../../security/secure-your-elastic-cloud-enterprise-installation/migrate-ece-on-podman-hosts-to-selinux-enforce.md) - Migrate ECE to SELinux in `enforcing` mode using Podman.

deploy-manage/deploy/cloud-enterprise/create-deployment.md

@@ -8,7 +8,7 @@ mapped_pages:
 
 # Create a deployment
 
-An ECE deployment is a fully managed Elastic Stack environment running on {{ece}}. It includes {{es}}, {{kib}}, and optional features like Machine Learning or an Integrations (Fleet & APM) Server.
+An ECE deployment is a fully managed {{stack}} environment running on {{ece}}. It includes {{es}}, {{kib}}, and optional features like Machine Learning or an Integrations (Fleet & APM) Server.
 
 Each deployment is based on a [deployment template](./deployment-templates.md), which defines its resources, default topology, scaling policies, and available features. Deployments can be customized based on workload requirements, snapshot settings, and security configurations.
 

deploy-manage/deploy/cloud-enterprise/default-system-deployment-versions.md

@@ -8,7 +8,7 @@ mapped_pages:
 
 # Default system deployment versions [ece-system-deployment-versions]
 
-When installing or upgrading {{ece}}, its associated system deployments run by default on the Elastic Stack versions listed in the following table.
+When installing or upgrading {{ece}}, its associated system deployments run by default on the {{stack}} versions listed in the following table.
 
 Note that since version 2.7.0, system deployments are automatically upgraded when upgrading {{ece}}. Don’t attempt to upgrade system deployments manually. Instead, follow the [ECE upgrade instructions](../../upgrade/orchestrator/upgrade-cloud-enterprise.md).
 

deploy-manage/deploy/cloud-enterprise/deploy-an-orchestrator.md

@@ -5,7 +5,7 @@ applies_to:
 ---
 # Deploy an orchestrator
 
-{{ece}} (ECE) provides a centralized platform that allows organizations to run {{es}}, {{kib}}, and other Elastic Stack components across multiple machines, whether in a private or public cloud, virtual machines, or your own premises.
+{{ece}} (ECE) provides a centralized platform that allows organizations to run {{es}}, {{kib}}, and other {{stack}} components across multiple machines, whether in a private or public cloud, virtual machines, or your own premises.
 
 ::::{note}
 This section focuses on deploying the ECE orchestrator. If you want to deploy {{es}}, {{kib}} or other {{stack}} applications on ECE, refer to [](./working-with-deployments.md).

deploy-manage/deploy/cloud-enterprise/ece-configure-templates-index-management.md

@@ -28,7 +28,7 @@ To configure index management when you create a deployment template:
 1. On the **Index Management** page, configure the index curation methods that you want to be available when your users create deployments:
 
     Index lifecycle management
-    :   Uses the ILM feature of the Elastic Stack that provides an integrated and streamlined way to manage time-based data, making it easier to follow best practices for managing your indices. Compared to index curation, ILM gives you more fine-grained control over the lifecycle of each index.
+    :   Uses the ILM feature of the {{stack}} that provides an integrated and streamlined way to manage time-based data, making it easier to follow best practices for managing your indices. Compared to index curation, ILM gives you more fine-grained control over the lifecycle of each index.
 
         To configure index lifecycle management: