diff --git a/docs/reference/datatiers.asciidoc b/docs/reference/datatiers.asciidoc index 3de1fcc8b555..6d6b1f438ae8 100644 --- a/docs/reference/datatiers.asciidoc +++ b/docs/reference/datatiers.asciidoc @@ -105,7 +105,7 @@ transitioning into the frozen tier into a shared-cache searchable snapshot. Search is typically slower on the frozen tier than the cold tier, because {es} must sometimes fetch data from the snapshot repository. -NOTE: The frozen tier is not yet available on the {ess-trial}[{ess}]. To +NOTE: The frozen tier is not yet available on {ess-trial}[{ess}]. To recreate similar functionality, see <>. diff --git a/docs/reference/indices/index-templates.asciidoc b/docs/reference/indices/index-templates.asciidoc index 8fa96498c17e..5c982b617b9d 100644 --- a/docs/reference/indices/index-templates.asciidoc +++ b/docs/reference/indices/index-templates.asciidoc @@ -46,7 +46,7 @@ following index patterns: - `synthetics-*-*` // end::built-in-index-template-patterns[] -The {fleet-guide}/fleet-overview.html[{agent}] uses these templates to create +{fleet-guide}/fleet-overview.html[{agent}] uses these templates to create data streams. Index templates created by {fleet} integrations use similar overlapping index patterns and have a priority up to `200`. diff --git a/docs/reference/indices/put-component-template.asciidoc b/docs/reference/indices/put-component-template.asciidoc index 2fe8b4cb0152..417611d8ee03 100644 --- a/docs/reference/indices/put-component-template.asciidoc +++ b/docs/reference/indices/put-component-template.asciidoc @@ -99,7 +99,7 @@ Name of the component template to create. - `synthetics-settings` // end::built-in-component-templates[] -The {fleet-guide}/fleet-overview.html[{agent}] uses these templates to configure +{fleet-guide}/fleet-overview.html[{agent}] uses these templates to configure backing indices for its data streams. If you use {agent} and want to overwrite one of these templates, set the `version` for your replacement template higher than the current version. diff --git a/docs/reference/modules/indices/index_management.asciidoc b/docs/reference/modules/indices/index_management.asciidoc index 05c1c6cf669b..cda08db2b9eb 100644 --- a/docs/reference/modules/indices/index_management.asciidoc +++ b/docs/reference/modules/indices/index_management.asciidoc @@ -38,7 +38,7 @@ Specifies the hosts that can be <>. + -- (<>) -If `true`, enables built-in index and component templates. The +If `true`, enables built-in index and component templates. {fleet-guide}/fleet-overview.html[{agent}] uses these templates to create data streams. If `false`, {es} disables these index and component templates. Defaults to `true`. diff --git a/docs/reference/searchable-snapshots/index.asciidoc b/docs/reference/searchable-snapshots/index.asciidoc index b0b86bd9c377..e3fa9a1a3897 100644 --- a/docs/reference/searchable-snapshots/index.asciidoc +++ b/docs/reference/searchable-snapshots/index.asciidoc @@ -219,9 +219,9 @@ repository storage then you are responsible for its reliability. [[searchable-snapshots-frozen-tier-on-cloud]] === Configure a frozen tier on {ess} -The frozen data tier is not yet available on the {ess-trial}[{ess}]. However, +The frozen data tier is not yet available on {ess-trial}[{ess}]. However, you can configure another tier to use <>. -This effectively recreates a frozen tier in your {ess} deployment. Follow these +This effectively recreates a frozen tier in your deployment. Follow these steps: . Choose an existing tier to use. Typically, you'll use the cold tier, but the