Improve Discover page starts based on best practices per content type and include technical summary when appropriate

Author: florent-leborgne

explore-analyze/discover/background-search.md

@@ -12,18 +12,16 @@ description: Execute long-running searches with background search in Discover an
 
 # Run Discover and Dashboards queries in the background
 
+When searching through years of historical data or running complex queries on large datasets, you can send long-running queries to run in the background. This lets you continue your work in other applications, explore different data, or even close your browser while the search runs. Return anytime to check progress or view completed results.
+
+**Technical summary**: Start a query, click **Send to background** once it begins running, and manage background searches from the {icon}`background_task` toolbar icon. Searches expire after 7 days (configurable through `data.search.sessions.defaultExpiration`). Requires the Background search subfeature permission.
+
 ::::{important} - Background search replaces Search sessions
 
 Background search is a feature introduced in version 9.2. It replaces the deprecated **Search sessions** feature.
 If you have been using search sessions and upgrade to 9.2, your search sessions aren't lost and become background searches.
 ::::
 
-Sometimes you might need to search through large amounts of data, no matter how long the search takes. Consider a threat hunting scenario, where you need to search through years of data. 
-
-You can send your long-running searches to the background from **Discover** or **Dashboards** and let them run while you continue your work. 
-
-You can access your list of background searches at any time to check their status and manage them from the {icon}`background_task` **Background searches** button in the toolbar.
-
 ![Send search to background](https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltee31dcf0d3917c75/68ecf412e5bae49d65a286ff/background-search.gif " =75%")
 
 

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

@@ -9,18 +9,14 @@ products:
 description: Explore Elasticsearch data with Kibana Discover. Select data views, filter and search documents, analyze field values, add runtime fields, and visualize findings to understand patterns.
 ---
 
-# Explore fields and data with Discover [discover-get-started]
+# Get started with Discover [discover-get-started]
 
-Learn how to use **Discover** to:
-
-* **Select** and **filter** your {{es}} data.
-* **Explore** the fields and content of your data in depth.
-* **Present** your findings in a visualization.
+Discover is your starting point for exploring data in {{es}}. Whether you're investigating an issue, learning about your data's structure, or building insights, Discover provides an interactive environment to search, filter, and analyze documents. This tutorial helps you learn the essential workflows and features that make data exploration effective.
 
 **Prerequisites:**
 
-* If you don’t already have {{kib}}, [start a free trial](https://www.elastic.co/cloud/elasticsearch-service/signup?baymax=docs-body&elektra=docs) on Elastic Cloud.
-* You must have data in {{es}}. Examples on this page use the [ecommerce sample data set](../index.md#gs-get-data-into-kibana), but you can use your own data.
+* If you don't already have {{kib}}, [start a free trial](https://www.elastic.co/cloud/elasticsearch-service/signup?baymax=docs-body&elektra=docs) on {{ecloud}}.
+* You must have data in {{es}}. The examples on this page use the [ecommerce sample data set](../index.md#gs-get-data-into-kibana), but you can use your own data.
 * You should have an understanding of [{{es}} documents and indices](../../manage-data/data-store/index-basics.md).
 
 ## Context-aware data exploration [context-aware-discover]

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

@@ -9,15 +9,21 @@ products:
 description: Sort Discover results with relevance scoring to surface documents that best match search queries. Focus exploration on the most pertinent results for faster data insights.
 ---
 
-# Search for relevance [discover-search-for-relevance]
+# Sort Discover results by relevance score [discover-search-for-relevance]
 
-{{es}} assigns a relevancy, or score to each document, so you can can narrow your search to the documents with the most relevant results. The higher the score, the better it matches your query.
+When searching large datasets, you want the most relevant documents to appear first. {{es}} assigns a relevance score to each document based on how well it matches your query. This guide shows you how to sort results by relevance score in Discover to surface the most pertinent matches.
 
-This example shows how to use **Discover** to list your documents from most relevant to least relevant. This example uses the [sample flights data set](../index.md#gs-get-data-into-kibana), or you can use your own data.
+**Technical summary**: Add the `_score` meta field to your document table, clear the default time-based sort, and sort by `_score` in descending order to show most relevant results first.
+
+**Prerequisites:**
+
+* You need a {{data-source}} with searchable text fields
+* Works best with text search queries (not filters or time range queries alone)
+* This example uses the [sample flights data set](../index.md#gs-get-data-into-kibana), or you can use your own data
 
 1. In **Discover**, open the {{data-source}} dropdown, and select the data that you want to work with.
 
-    For the sample flights data, set the {{data-source}} to **Kibana Sample Data Flights**.
+    For the sample flights data, set the {{data-source}} to **{{kib}} Sample Data Flights**.
 
 2. Run your search.  For the sample data, try:
 

explore-analyze/discover/document-explorer.md

@@ -11,10 +11,17 @@ description: Customize data exploration with Discover's table controls. Arrange
 
 # Customize the Discover view [document-explorer]
 
-Fine tune your explorations by customizing **Discover** to bring out the the best view of your documents.
+Discover provides extensive customization options for the document table and interface layout. You can adjust table density, row height, column layout, sample size, and sorting to optimize your data exploration workflow. These settings persist across sessions and carry over when you create dashboard panels.
+
+This page covers:
+- Hiding and resizing interface areas (chart, fields list, document table)
+- Customizing the document table (columns, density, row height, sample size)
+- Sorting by single or multiple fields
+- Filtering documents and comparing field values
+- Editing field display formats
 
 :::{tip}
-Discover provides default [context-aware experiences](/explore-analyze/discover/discover-get-started.md#context-aware-discover) tailored to the type of data that you're exploring, and you can further customize your Discover view on top of them.
+Discover provides default [context-aware experiences](/explore-analyze/discover/discover-get-started.md#context-aware-discover) tailored to the type of data you're exploring. You can further customize your Discover view on top of these experiences.
 :::
 
 :::{image} /explore-analyze/images/kibana-hello-field.png
@@ -93,7 +100,7 @@ To sort by multiple fields:
 
 Change how {{kib}} displays a field.
 
-1. Click the column header for the field, and then select **Edit data view field.**
+1. Click the column header for the field, and then select **Edit {{data-source}} field.**
 2. In the **Edit field** form, change the field name and format.
    For detailed information on formatting options, refer to [Format data fields](../find-and-organize/data-views.md#managing-fields).
 

explore-analyze/discover/run-pattern-analysis-discover.md

@@ -1,4 +1,5 @@
 ---
+navigation_title: "Pattern analysis"
 mapped_pages:
   - https://www.elastic.co/guide/en/kibana/current/run-pattern-analysis-discover.html
 applies_to:
@@ -9,16 +10,20 @@ products:
 description: Detect patterns in unstructured logs with Discover's pattern analysis. Categorize log messages, identify common structures, and filter out noise during troubleshooting.
 ---
 
-# Run a pattern analysis on your log data [run-pattern-analysis-discover]
+# Analyze log patterns in Discover [run-pattern-analysis-discover]
 
-Log pattern analysis helps you to find patterns in unstructured log messages and makes it easier to examine your data. It performs categorization analysis on a selected field of a {{data-source}}, creates categories based on the data and displays them together with a chart that shows the distribution of each category and an example document that matches the category.
+When troubleshooting with unstructured log data, manually identifying patterns is time-consuming. Pattern analysis automatically categorizes log messages to help you find common structures and filter out noise during investigation. This guide shows you how to run pattern analysis in Discover.
 
-Log pattern analysis works on every text field.
+**Technical summary**: Open the **Patterns** tab in Discover, select a text field for analysis, adjust the minimum time range if needed, and filter or exclude patterns to focus on actionable data.
 
-This example uses the [sample web logs data](../index.md#gs-get-data-into-kibana), or you can use your own data.
+**Prerequisites:**
+
+* You need a {{data-source}} with text fields containing log data
+* Pattern analysis works on any text field in your data
+* This example uses the [sample web logs data](../index.md#gs-get-data-into-kibana), or you can use your own data
 
 1. Go to **Discover**.
-2. Expand the {{data-source}} dropdown, and select **Kibana Sample Data Logs**.
+2. Expand the {{data-source}} dropdown, and select **{{kib}} Sample Data Logs**.
 3. If you don’t see any results, expand the time range, for example, to **Last 15 days**.
 4. Click the **Patterns** tab next to **Documents** and **Field statistics**. The pattern analysis starts. The results are displayed under the chart. You can change the analyzed field by using the field selector. In the **Pattern analysis menu**, you can change the **Minimum time range**. This option enables you to widen the time range for calculating patterns which improves accuracy. The patterns, however, are still displayed by the time range you selected in step 3.
 

explore-analyze/discover/save-open-search.md

@@ -10,14 +10,20 @@ products:
 description: Preserve exploration work with saved Discover sessions that store queries, filters, column selections, and data views. Reuse explorations, share with teams, or add to dashboards.
 ---
 
-# Discover sessions: Save a search for reuse [save-open-search]
+# Save and reuse Discover searches [save-open-search]
 
-A saved Discover session is a convenient way to reuse a search that you’ve created in **Discover**. Discover sessions are good for saving a configured view of Discover to use later or adding search results to a dashboard, and can also serve as a foundation for building visualizations.
+After configuring a search with specific queries, filters, and column selections, you can save your work as a Discover session. This lets you reopen the exact view later, share it with team members, or add the results to a dashboard. Saved sessions preserve all aspects of your exploration for future use.
 
+**Technical summary**: Click **Save** in the toolbar, name your session, and optionally store time range and tags. Saved sessions preserve query text, filters, selected {{data-source}}, columns, sort order, and document table configuration.
+
+**Prerequisites:**
+
+* You need privileges to save Discover sessions (refer to [Granting access to {{kib}}](elasticsearch://reference/elasticsearch/roles.md))
+* If a read-only indicator appears, you can view but not save sessions
 
 ## Read-only access [discover-read-only-access]
 
-If you don’t have sufficient privileges to save Discover sessions, the following indicator is displayed and the **Save** button is not visible. For more information, refer to [Granting access to {{kib}}](elasticsearch://reference/elasticsearch/roles.md).
+If you don't have sufficient privileges to save Discover sessions, the following indicator is displayed and the **Save** button is not visible.
 
 :::{image} /explore-analyze/images/kibana-read-only-badge.png
 :alt: Example of Discover's read only access indicator in Kibana's header

explore-analyze/discover/show-field-statistics.md

@@ -9,22 +9,25 @@ products:
 description: Examine field distributions and value ranges with Discover's Field statistics view. Identify data quality issues, understand cardinality, and create visualizations from field data.
 ---
 
-# View field statistics [show-field-statistics]
+# View field statistics in Discover [show-field-statistics]
 
-Explore the fields in your data with the **Field statistics** view in **Discover** and answer such questions as:
+Field statistics view in Discover shows distribution patterns, cardinality, and value ranges for fields in your data. Use this view to assess data quality, understand field usage, identify outliers, and create quick visualizations from field distributions. Statistics vary by field type. Numeric fields show ranges and distributions, while geo fields display coordinate maps.
 
-* What does the latency look like when one of the containers is down on a Sunday?
-* Is the field type and format in the data view appropriate for the data and its cardinality?
+Field statistics help you answer questions like:
+* What's the distribution of values across a field?
+* Are there unexpected patterns or outliers in the data?
+* Is the field format appropriate for its cardinality?
+* What does latency look like when one of the containers is down on a specific day?
 
-:::{note}
-Field statistics aren't available when **Discover** is in {{esql}} mode.
-:::
+**Prerequisites:**
 
-This example explores the fields in the [sample web logs data](../index.md#gs-get-data-into-kibana), or you can use your own data.
+* You need a {{data-source}} with data to explore
+* Field statistics aren't available when Discover is in {{esql}} mode
+* This example uses [sample web logs data](../index.md#gs-get-data-into-kibana), or you can use your own data
 
 1. Go to **Discover**.
-2. Expand the {{data-source}} dropdown, and select **Kibana Sample Data Logs**.
-3. If you don’t see any results, expand the time range, for example, to **Last 7 days**.
+2. Expand the {{data-source}} dropdown, and select **{{kib}} Sample Data Logs**.
+3. If you don't see any results, expand the time range, for example, to **Last 7 days**.
 4. Click **Field statistics**.
    The table summarizes how many documents in the sample contain each field for the selected time period the number of distinct values, and the distribution.
 

explore-analyze/discover/try-esql.md

@@ -9,24 +9,21 @@ products:
 description: Query Elasticsearch data with ES|QL in Discover to explore any indices without predefining data views. Filter, aggregate, sort results, and build dynamic visualizations.
 ---
 
-# Using ES|QL [try-esql]
+# Get started with {{esql}} in Discover [try-esql]
 
-The Elasticsearch Query Language, {{esql}}, makes it easier to explore your data without leaving Discover.
+{{esql}} brings a powerful piped query language directly into Discover, letting you work with your data more flexibly. Unlike traditional searches that require predefined {{data-sources}}, {{esql}} queries can target any index and reshape results on the fly. This tutorial helps you learn {{esql}} syntax fundamentals by progressively building queries that filter, sort, and aggregate data.
 
-The examples on this page use the {{kib}} sample web logs in Discover and Lens to explore the data and create visualizations. You can also install it by following [Add sample data](../index.md#gs-get-data-into-kibana).
+**Prerequisites:**
 
-::::{tip}
-For the complete {{esql}} documentation, including all supported commands, functions, and operators, refer to the [{{esql}} reference](elasticsearch://reference/query-languages/esql/esql-syntax-reference.md). For a more detailed overview of {{esql}} in {{kib}}, refer to [Use {{esql}} in Kibana](../query-filter/languages/esql-kibana.md).
+* You need access to {{kib}} (version 8.11 or later for {{esql}} support)
+* The `enableESQL` setting must be enabled from {{kib}}'s **Advanced Settings**. It is enabled by default.
+* The examples use the [sample web logs data](../index.md#gs-get-data-into-kibana). Install it or use your own data.
 
+::::{tip}
+For the complete {{esql}} documentation, including all supported commands, functions, and operators, refer to the [{{esql}} reference](elasticsearch://reference/query-languages/esql/esql-syntax-reference.md). For a more detailed overview of {{esql}} in {{kib}}, refer to [Use {{esql}} in {{kib}}](../query-filter/languages/esql-kibana.md).
 ::::
 
 
-
-## Prerequisite [prerequisite]
-
-To view the {{esql}} option in **Discover**, the `enableESQL` setting must be enabled from Kibana’s **Advanced Settings**. It is enabled by default.
-
-
 ## Use {{esql}} [tutorial-try-esql]
 
 To load the sample data: