Merge branch 'main' into streams-9.2-updates

Author: mdbirnstiehl

deploy-manage/tools/snapshot-and-restore/searchable-snapshots.md

@@ -13,7 +13,7 @@ products:
 
 # Searchable snapshots [searchable-snapshots]
 ::::{important}
-Searchable snapshots is a feature that requires an Enteprise license. 
+Searchable snapshots is a feature that requires an Enterprise license. 
 ::::
 
 {{search-snaps-cap}} let you use [snapshots](../snapshot-and-restore.md) to search infrequently accessed and read-only data in a very cost-effective fashion. The [cold](../../../manage-data/lifecycle/data-tiers.md#cold-tier) and [frozen](../../../manage-data/lifecycle/data-tiers.md#frozen-tier) data tiers use {{search-snaps}} to reduce your storage and operating costs.

manage-data/data-store/mapping/dynamic-templates.md

@@ -247,7 +247,7 @@ PUT my-index-000001
   }
 }
 
-PUT my-index/_doc/1
+PUT my-index-000001/_doc/1
 {
   "one_ip":   "will not match", <1>
   "ip_two":   "will not match", <2>

manage-data/data-store/text-analysis/token-graphs.md

@@ -34,7 +34,7 @@ In the following graph, `quick` and its synonym `fast` both have a position of `
 
 ## Multi-position tokens [token-graphs-multi-position-tokens]
 
-Some token filters can add tokens that span multiple positions. These can include tokens for multi-word synonyms, such as using "atm" as a synonym for "automatic teller machine."
+Some token filters can add tokens that span multiple positions. These can include tokens for multi-word synonyms, such as using "atm" as a synonym for "automatic teller machine".
 
 However, only some token filters, known as *graph token filters*, accurately record the `positionLength` for multi-position tokens. These filters include:
 

reference/fleet/automatic-integrations-synchronization.md

@@ -26,6 +26,13 @@ This feature is available only for certain subscription levels. For more informa
 * Remote clusters must be running the same {{es}} version as the management cluster, or a newer version that supports {{ccr}}.
 * To install integrations, remote clusters require access to the [{{package-registry}}](/reference/fleet/index.md#package-registry-intro).
 
+## Limitations
+
+These limitations apply when using the automatic integrations synchronization feature:
+
+- [Index lifecycle management](/manage-data/lifecycle/index-lifecycle-management.md) (ILM) policies and enrich policies referenced in custom component templates are not automatically synchronized. Synchronizing custom assets that include references to ILM or enrich policies may cause custom component templates to break.
+- Integrations installed on the management cluster are synchronized to the remote cluster regardless of the space they are installed in. On the remote cluster, the synchronized integrations are always installed in the default space.
+
 ## Configure {{ccr}} on the remote cluster
 
 In your remote cluster:

solutions/images/security-defend-policy-device-control.png

@@ -20,6 +20,10 @@ Most options in this section are supported by all APM Server deployment methods.
 
 The [Real User Monitoring (RUM) agent](apm-agent-rum-js://reference/index.md) captures user interactions with clients such as web browsers. These interactions are sent as events to the APM Server. Because the RUM agent runs on the client side, the connection between agent and server is unauthenticated. As a security precaution, RUM is therefore disabled by default.
 
+:::{important}
+To use RUM, you need a centralized APM Server, either running as standalone binary or managed through Fleet.
+:::
+
 :::::::{tab-set}
 
 ::::::{tab-item} APM Server binary