Merge branch 'main' into szabosteve/mark-elser-eis-ga

Author: szabosteve

explore-analyze/transforms/transform-limitations.md

@@ -128,7 +128,7 @@ If you use ILM to have time-based indices, consider using the [Date index name](
 When running a large number of SLO {{transforms}}, two types of limitations can appear:
 
 - {{transforms-cap}} may [misreport](#transforms-inaccurate-errors) their state and suggest deletion even though they are still valid
-- Point-in-time (PIT) requests may [accumulate](#transforms-pit-storms), creating extra activity on the cluster and slowing down operations
+- Point-in-time (PIT) requests may [accumulate](#transforms-pit-overloads), creating extra activity on the cluster and slowing down operations
 
 #### {{transforms-cap}} can return inaccurate errors that suggest deletion [transforms-inaccurate-errors]
 

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

@@ -150,7 +150,7 @@ To add an index template to a cluster and apply the lifecycle policy to indices
 1. On the **Component templates** page, use the search and filter tools to select any [component templates](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-component-template) to include in the index template. The index template will inherit the settings, mappings, and aliases defined in the component templates and apply them to indices when they're created.
 
 1. On the **Index settings** page:
-    1. Configure ILM by specifying the [ILM settings](https://www.elastic.co/docs/api/doc/elasticsearch/configuration-reference/index-lifecycle-management-settings#_index_level_settings_2) to apply to the indices:
+    1. Configure ILM by specifying the [ILM settings](elasticsearch://reference/elasticsearch/configuration-reference/index-lifecycle-management-settings.md) to apply to the indices:
         * `index.lifecycle.name` - The lifecycle policy to manage the created indices.
         * `index.lifecycle.rollover_alias` - The index [alias](/manage-data/data-store/aliases.md) used for querying and managing the set of indices associated with a lifecycle policy that contains a rollover action.