Merge branch 'main' into 2760-alert-assets-v2

Author: karenzone

deploy-manage/security/updating-certificates.md

@@ -23,7 +23,7 @@ Regardless of the scenario, {{es}} monitors the SSL resources for updates by def
 
 Because {{es}} doesn’t reload the `elasticsearch.yml` configuration, you must use **the same file names** if you want to take advantage of automatic certificate and key reloading.
 
-If you need to update the `elasticsearch.yml`](/deploy-manage/stack-settings.md) configuration or change passwords for keys or keystores that are stored in the [secure settings](secure-settings.md), then you must complete a [rolling restart](#use-rolling-restarts). {{es}} will not automatically reload changes for passwords stored in the secure settings.
+If you need to update the [`elasticsearch.yml`](/deploy-manage/stack-settings.md) configuration or change passwords for keys or keystores that are stored in the [secure settings](secure-settings.md), then you must complete a [rolling restart](#use-rolling-restarts). {{es}} will not automatically reload changes for passwords stored in the secure settings.
 
 ::::{admonition} Rolling restarts are preferred
 :name: use-rolling-restarts

deploy-manage/upgrade/deployment-or-cluster/reading-indices-from-older-elasticsearch-versions.md

@@ -9,7 +9,7 @@ products:
 
 # Reading indices from older {{es}} versions [archive-indices]
 
-{{es}} has full query and write support for indices created in the previous major version. If you have indices created in {{es}} versions 5 or 6, you can use the archive functionality to import them into newer {{es}} versions as well.
+{{es}} has full query and write support for indices created in the previous major version. If you have indices created in {{es}} versions 5, 6, or 7, you can use the archive functionality to import them into newer {{es}} versions as well.
 
 The archive functionality provides slower read-only access to older {{es}} data, for compliance or regulatory reasons, the occasional lookback or investigation, or to rehydrate parts of it. Access to the data is expected to be infrequent, and can therefore happen with limited performance and query capabilities.
 
@@ -50,7 +50,7 @@ Due to `_source` access, the data can also be [reindexed](https://www.elastic.co
 
 ## Upgrade older {{es}} clusters [_how_to_upgrade_older_es_clusters]
 
-To upgrade older {{es}} 5 or 6 clusters: 
+To upgrade older {{es}} 5, 6, or 7 clusters: 
 
 1. Take a snapshot of the indices in the old cluster. 
 2. Delete any indices created before 8.0.0. 

explore-analyze/_snippets/global-filters.md

@@ -1,7 +1,7 @@
-You can interact with filter pills to edit them, temporarily alter their behavior without having to delete them, or make them available in other contexts. The following options are available when selecting a filter pill:
+You can interact with filter pills to edit them, temporarily alter their behavior without having to remove them, or make them available in other contexts. The following options are available when selecting a filter pill:
 
 **Pin across all apps** and **Unpin**
-:    Adds this filter to available dashboards and to apps such as **Discover**, **Lens**, **Maps**, and **Visualize**. The filter is removed if you:
+:    Adds this filter to available dashboards and to apps such as **Discover**, **Lens**, **Maps**, and **Visualize**. You remove the filter if you:
      * Unpin it. In this case, the filter only remains on the currently open app, unpinned.
      * Remove it from any place while it's still pinned.
      * Refresh your session, for example by opening a dashboard in a new tab. Pinned filters are not saved along with the dashboard, visualization, or Discover session that you added them to.
@@ -17,9 +17,9 @@ You can interact with filter pills to edit them, temporarily alter their behavio
 :    Reverses the filter behavior.
 
 **Temporarily disable** and **Re-enable**
-:    Lets you temporarily disable a filter instead of requiring you to delete it. This is particularly useful for testing different filter combinations.
+:    Lets you temporarily deactivate a filter instead of requiring you to remove it. This is particularly useful for testing different filter combinations.
 
 **Delete**
-:    Deletes the filter.
+:    Removes the filter.
 
 You can perform most of these actions at once for all filters in your current view using the **Filter** icon {icon}`filter`. From the menu that opens, select **Apply to all**, then choose the action you'd like to perform.

explore-analyze/_snippets/inspect-request.md

@@ -1,4 +1,4 @@
-The request **Inspector** is available in **Discover** and for all **Dashboards** visualization panels that are built based on a query. The available information can differ based on the request.
+The request **Inspector** is available in **Discover** and for all **Dashboards** visualization panels that are built from a query. The available information can differ based on the request.
 
 1. Open the **Inspector**:
    - If you're in **Discover**, select **Inspect** from the application's toolbar.
@@ -8,7 +8,7 @@ The request **Inspector** is available in **Discover** and for all **Dashboards*
    :::{tip}
    Some visualizations rely on several requests. From the dropdown, select the request you want to inspect. 
    :::
-    * **Statistics**: Provides general information and statistics about the request. For example, you can check if the number of hits and query time match your expectations. If not, this may indicate an issue with the request used to build the visualization.
+    * **Statistics**: Provides general information and statistics about the request. For example, you can check if the number of hits and query time match your expectations. If not, this can indicate an issue with the request used to build the visualization.
     * **Clusters and shards**: Lists the {{es}} clusters and shards per cluster queried to fetch the data and shows the status of the request on each of them. With the information in this tab, you can check if the request is properly executed, especially in case of cross-cluster search.
 
       :::{note}

explore-analyze/_snippets/variable-control-procedure.md

@@ -1,21 +1,21 @@
 1. While you edit your {{esql}} query, the autocomplete menu suggests adding a control when relevant or when you type `?` in the query. Select **Create control**.
 
-   ![ESQL query prompting to add a control](/explore-analyze/images/esql-visualization-control-suggestion.png " =40%")
+   ![{{esql}} query prompting to add a control](/explore-analyze/images/esql-visualization-control-suggestion.png " =40%")
 
 2. A menu opens to let you configure the control. This is where you can specify:
 
     * The type of the control. 
       * For controls with **Static values**, enter available controls manually or select them from the dropdown list. 
       * For controls with **Values from a query**, write an {{esql}} query to populate the list of options.
-    * The name of the control. This name is used to reference the control in {{esql}} queries. 
+    * The name of the control. You use this name to reference the control in {{esql}} queries. 
       * Start the name with `?` if you want the options to be simple static values.
       * Start the name with `??` if you want the options to be fields or functions. {applies_to}`stack: ga 9.1`
     * The values users can select for this control. You can add multiple values from suggested fields, or type in custom values. If you selected **Values from a query**, you must instead write an {{esql}} query at this step.
     * The label of the control. This is the label displayed in **Discover** or in the dashboard.
     * The width of the control.
     * Whether the control should allow selecting a single value or multiple values. This [requires using the `MV_CONTAINS` function in your query](#esql-multi-values-controls). {applies_to}`stack: preview 9.3` {applies_to}`serverless: preview`
 
-    ![ESQL control settings](/explore-analyze/images/esql-visualization-control-settings.png "title =40%")
+    ![{{esql}} control settings](/explore-analyze/images/esql-visualization-control-settings.png "title =40%")
 
 3. Save the control.
 

explore-analyze/discover/discover-get-started.md

@@ -87,7 +87,7 @@ You can later filter the data that shows in the chart and in the table by specif
 
 **Discover** provides utilities designed to help you make sense of your data:
 
-1. In the sidebar, check the available fields. It’s very common to have hundreds of fields. Use the search at the top of that sidebar to look for specific terms in the field names.
+1. In the sidebar, check the available fields. It's common to have hundreds of fields. Use the search at the top of that sidebar to look for specific terms in the field names.
    In this example, we’ve entered `ma` in the search field to find the `manufacturer` field.
    ![Fields list that displays the top five search results](/explore-analyze/images/kibana-discover-sidebar-available-fields.png "title =40%")
    ::::{tip}
@@ -237,7 +237,7 @@ Dive into an individual document to view its fields and the documents that occur
    * You can pin some fields by clicking the left column to keep them displayed even if you filter the table.
 
    ::::{tip}
-   You can restrict the fields listed in the detailed view to just the fields that you explicitly added to the **Discover** table, using the **Selected only** toggle. In ES|QL mode, you also have an option to hide fields with null values. This toggle isn't available from the **View single document** page.
+   You can restrict the fields listed in the detailed view to the fields that you explicitly added to the **Discover** table, using the **Selected only** toggle. In ES|QL mode, you also have an option to hide fields with null values. This toggle isn't available from the **View single document** page.
    ::::
 
 3. To navigate to a view of the document that you can bookmark and share, select **View single document**.
@@ -297,7 +297,7 @@ You can use **Discover** with the Elasticsearch Query Language, ES|QL. When usin
 You can switch to the ES|QL mode of Discover from the application menu bar.
 If you've entered a KQL or Lucene query in the default mode of Discover, it automatically converts to ES|QL.
 
-Note that in ES|QL mode, the **Documents** tab is named **Results**.
+In ES|QL mode, the **Documents** tab is named **Results**.
 
 :::{important}
 {applies_to}`stack: ga 9.1` When an ES|QL query times out, partial results that are available are shown. The timeout is defined by the `search:timeout` advanced setting, which is set to 10 minutes (600000 ms) by default. In serverless projects, this advanced setting is not customizable and the timeout is set to 10 minutes.

explore-analyze/discover/discover-search-for-relevance.md

@@ -28,7 +28,7 @@ This example shows how to use **Discover** to list your documents from most rele
 4. From the list of **Meta fields** list in the sidebar, add `_score`.
 5. Add any other fields you want to the document table.
 
-    At this point, you’re sorting by the`timestamp` field.
+    You're sorting by the`timestamp` field.
 
 6. To turn off sorting by the `timestamp` field, click the **field sorted** option, and then click **Clear sorting.**
 7. Open the **Pick fields to sort by** menu, and then click **_score**.

explore-analyze/discover/document-explorer.md

@@ -100,7 +100,7 @@ Change how {{kib}} displays a field.
 
 ### Filter the documents [document-explorer-compare-data]
 
-Narrow your results to a subset of documents so you’re comparing just the data of interest.
+Narrow your results to a subset of documents so you're comparing the data of interest.
 
 1. Select the documents you want to compare.
 2. Click the **Selected** option, and then select **Show selected documents only**.

explore-analyze/discover/try-esql.md

@@ -47,7 +47,7 @@ To load the sample data:
     | KEEP machine.os, machine.ram <2>
     ```
 
-    1. We’re specifically looking for data from the sample web logs we just installed.
+    1. We're specifically looking for data from the sample web logs we installed.
     2. We’re only keeping the `machine.os` and `machine.ram` fields in the results table.
    
    ::::{note}

explore-analyze/elastic-inference/inference-api.md

@@ -161,11 +161,64 @@ PUT _inference/sparse_embedding/word_chunks
 stack: ga 9.1
 ```
 
-The `recursive` strategy splits the input text based on a configurable list of separator patterns (for example, newlines or Markdown headers). The chunker applies these separators in order, recursively splitting any chunk that exceeds the `max_chunk_size` word limit. If no separator produces a small enough chunk, the strategy falls back to sentence-level splitting.
+The `recursive` strategy splits the input text based on a configurable list of separator patterns, such as paragraph boundaries or Markdown structural elements like headings and horizontal rules. The chunker applies these separators in order, recursively splitting any chunk that exceeds the `max_chunk_size` word limit. If no separator produces a small enough chunk, the strategy falls back to [sentence-level splitting](#sentence).
 
-##### Markdown separator group
+You can configure the `recursive` strategy using either:
+- [Predefined separator groups](#separator-groups): [`Plaintext`](#plaintext) or [`markdown`](#markdown)
+- [Custom separators](#custom-separators): Define your own regular expression patterns
 
-The following example creates an {{infer}} endpoint with the `elasticsearch` service that deploys the ELSER model and configures chunking with the `recursive` strategy using the markdown separator group and a maximum of 200 words per chunk.
+##### Predefined separator groups [separator-groups]
+
+Predefined separator groups provide optimized patterns for common text formats: [`plaintext`](#plaintext) works for simple line-structured text without markup, and [`markdown`](#markdown) works for Markdown-formatted content.
+
+###### `plaintext`
+
+The `plaintext` separator group splits text at paragraph boundaries, first attempting to split on double newlines (paragraph breaks), then falling back to single newlines when chunks are still too large.
+
+:::{dropdown} Regular expression patterns for the `plaintext` separator group
+
+1. `(?<!\\n)\\n\\n(?!\\n)`: Splits on consecutive newlines that indicate paragraph breaks.
+2. `(?<!\\n)\\n(?!\\n)`: Splits on single newlines when double newlines don't produce small enough chunks.
+
+:::
+
+The following example configures chunking with the `recursive` strategy using the `plaintext` separator group and a maximum of 200 words per chunk.
+
+```console
+PUT _inference/sparse_embedding/recursive_plaintext_chunks
+{
+  "service": "elasticsearch",
+  "service_settings": {
+    "model_id": ".elser_model_2",
+    "num_allocations": 1,
+    "num_threads": 1
+  },
+  "chunking_settings": {
+    "strategy": "recursive",
+    "max_chunk_size": 200,
+    "separator_group": "plaintext"
+  }
+}
+```
+
+###### `markdown`
+
+The `markdown` separator group splits text based on Markdown structural elements, processing separators hierarchically from highest to lowest level: H1 through H6 headings, then horizontal rules.
+
+:::{dropdown} Regular expression patterns for the `markdown` separator group
+
+1. `\n# `: Splits on level 1 headings (H1).
+2. `\n## `: Splits on level 2 headings (H2).
+3. `\n### `: Splits on level 3 headings (H3).
+4. `\n#### `: Splits on level 4 headings (H4).
+5. `\n##### `: Splits on level 5 headings (H5).
+6. `\n###### `: Splits on level 6 headings (H6).
+7. `\n^(?!\\s*$).*\\n-{1,}\\n`: Splits on horizontal rules created with hyphens.
+8. `\n^(?!\\s*$).*\\n={1,}\\n`: Splits on horizontal rules created with equals signs.
+
+:::
+
+The following example configures chunking with the `recursive` strategy using the `markdown` separator group and a maximum of 200 words per chunk.
 
 ```console
 PUT _inference/sparse_embedding/recursive_markdown_chunks
@@ -184,10 +237,9 @@ PUT _inference/sparse_embedding/recursive_markdown_chunks
 }
 ```
 
-##### Custom separator group
-
-The following example creates an {{infer}} endpoint with the `elasticsearch` service that deploys the ELSER model and configures chunking with the `recursive` strategy. It uses a custom list of separators to split plaintext into chunks of up to 180 words.
+##### Custom separators
 
+If the [predefined separator groups](#separator-groups) don't meet your needs, you can define custom separators using regular expressions. The following example configures chunking with the `recursive` strategy using a custom list of separators to split text into chunks of up to 180 words.
 
 ```console
 PUT _inference/sparse_embedding/recursive_custom_chunks
@@ -236,3 +288,5 @@ PUT _inference/sparse_embedding/none_chunking
   }
 }
 ```
+
+