ECE links to current updated and fixed (#1988)

Relates to elastic/docs-projects#494

I'm researching all links to ECE `current` doc set while finding URLs
that haven't been redirected or they are incorrectly redirected.

I have fixed all `cloud-enterprise/current` URLs in this repo, replacing
`current` with `3.8` when appropriate (only twice while referring to a
legacy feature), or replacing them by a proper doc in `docs-content`
directly.

I also found some little inconsisencies and I gave some extra love to
some paragraphs.

Missing redirects:
-
https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-index-management.html
(fixed at `mapped_pages` level).

-
https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-apm-and-fleet.html
(this one makes sense as it's a legacy feature, I've changed the links
to `3.8` instead of current). No redirect should be needed (IMO),
otherwise it should redirect to ECE manage Integrations Server doc.

Adding comments in the code for reviewing purposes.

Author: eedugon

deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md

@@ -43,7 +43,7 @@ Currently, autoscaling behavior is as follows:
 * **Data tiers**
 
     * Each {{es}} [data tier](../../manage-data/lifecycle/data-tiers.md) scales upward based on the amount of available storage. When we detect more storage is needed, autoscaling will scale up each data tier independently to ensure you can continue and ingest more data to your hot and content tier, or move data to the warm, cold, or frozen data tiers.
-    * In addition to scaling up existing data tiers, a new data tier will be automatically added when necessary, based on your [index lifecycle management policies](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-index-management.html).
+    * In addition to scaling up existing data tiers, a new data tier will be automatically added when necessary, based on your [index lifecycle management policies](/manage-data/lifecycle/index-lifecycle-management.md).
     * To control the maximum size of each data tier and ensure it will not scale above a certain size, you can use the maximum size per zone field.
     * Autoscaling based on memory or CPU, as well as autoscaling downward, is not currently supported. In case you want to adjust the size of your data tier to add more memory or CPU, or in case you deleted data and want to scale it down, you can set the current size per zone of each data tier manually.
 

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

@@ -20,8 +20,11 @@ In a template that creates a hot-warm architecture, you can use index curation t
 
 Configuring index management is part of the larger task of [creating deployment templates](ece-configuring-ece-create-templates.md) or editing them. The choices you make here determine which index management methods are available to your users when they create deployments.
 
-You should configure all index management methods that you want your users to be able to choose from when they create their deployments from your template. You can configure index curation, index lifecycle management, or both. If you are not sure which index management methods to configure, take a look at how your users are asked to [configure index management](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-index-management.html) when they customize their deployments.
+You should configure all index management methods that you want your users to be able to choose from when they create their deployments from your template. You can configure index curation, index lifecycle management, or both.
 
+::::{note}
+Index curation has been deprecated in favor of [index lifecycle management](/manage-data/lifecycle/index-lifecycle-management.md). For {{stack}} version 6.7 and later, any deployments using index curation will be prompted to [migrate to ILM](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md).
+::::
 
 ## Steps [ece_steps_2]
 

deploy-manage/deploy/cloud-enterprise/ece-integrations-server-api-example.md

@@ -19,7 +19,7 @@ For more information on how to manage Integrations Server from the UI, check [Ma
 
 Integrations Server can be enabled only on new deployments, starting with {{stack}} version 8.0.
 
-It’s possible to enable Integrations Server on an existing deployment with version 8.0 only if [APM & Fleet Server](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-apm-and-fleet.html) hasn’t been previously enabled on the deployment.
+It’s possible to enable Integrations Server on an existing deployment with version 8.0 only if the legacy [APM & Fleet Server](https://www.elastic.co/guide/en/cloud-enterprise/3.8/ece-manage-apm-and-fleet.html) hasn’t been previously enabled on the deployment.
 
 
 ## API request example [ece_api_request_example_2]

deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md

@@ -20,7 +20,7 @@ products:
 New or updated versions of the {{stack}} must be prepared to work with {{ece}} and are provided as packs that you can download.
 
 ::::{important}
-{{es}} 7.8 and later comes with Index Lifecycle Management (ILM) always enabled. Before upgrading to 7.8 or later, to avoid any unpredictable behavior it is important to configure hot-warm clusters on {{ece}} with ILM rather than index curation. Check [migrate to index lifecycle management](../../../manage-data/lifecycle/index-lifecycle-management.md) for existing clusters, and [configure index management](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-index-management.html) for new clusters.
+{{es}} 7.8 and later comes with Index Lifecycle Management (ILM) always enabled. Before upgrading to 7.8 or later, to avoid any unpredictable behavior it is important to configure hot-warm clusters on {{ece}} with ILM rather than index curation. Check [migrate to index lifecycle management](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md) for existing clusters, and [configure index management](/manage-data/lifecycle/index-lifecycle-management.md) for new clusters.
 ::::
 
 

deploy-manage/deploy/cloud-enterprise/switch-from-apm-to-integrations-server-payload.md

@@ -10,7 +10,7 @@ products:
 
 # Switch from APM to Integrations Server payload [ece-integrations-server-apm-switch]
 
-This example shows how to use the {{ece}} RESTful API to switch from using [APM & Fleet Server](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-apm-and-fleet.html) to [Integrations Server](manage-integrations-server.md).
+This example shows how to use the {{ece}} RESTful API to switch from using the legacy [APM & Fleet Server](https://www.elastic.co/guide/en/cloud-enterprise/3.8/ece-manage-apm-and-fleet.html) to [Integrations Server](manage-integrations-server.md).
 
 
 ## Requirements [ece_requirements_5]

manage-data/lifecycle/index-lifecycle-management.md

@@ -3,6 +3,8 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/overview-index-lifecycle-management.html
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-concepts.html
+  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-index-management.html
+  - https://www.elastic.co/guide/en/cloud/current/ec-configure-index-management.html
 applies_to:
   stack: ga
 products:

manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md

@@ -1,7 +1,6 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-migrate-index-management.html
-  - https://www.elastic.co/guide/en/cloud/current/ec-configure-index-management.html
   - https://www.elastic.co/guide/en/cloud/current/ec-migrate-index-management.html
 applies_to:
   stack: ga