elastic · florent-leborgne · Feb 5, 2025 · Feb 5, 2025 · Feb 5, 2025
@@ -104,7 +104,7 @@ When you create a rule in {{kib}}, an API key is created that captures a snapsho
 
 When you disable a rule, it retains the associated API key which is reused when the rule is enabled. If the API key is missing when you enable the rule, a new key is generated that has your current security privileges. When you import a rule, you must enable it before you can use it and a new API key is generated at that time.
 
-You can generate a new API key at any time in **{{stack-manage-app}} > {{rules-ui}}*** or in the rule details page by selecting ***Update API key** in the actions menu.
+You can generate a new API key at any time in **{{stack-manage-app}} > {{rules-ui}}** or in the rule details page by selecting **Update API key** in the actions menu.
 
 If you manage your rules by using {{kib}} APIs, they support support both key- and token-based authentication as described in [Authentication](https://www.elastic.co/guide/en/kibana/current/api.html#api-authentication). To use key-based authentication, create API keys and use them in the header of your API calls as described in [API Keys](../../../deploy-manage/api-keys/elasticsearch-api-keys.md). To use token-based authentication, provide a username and password; an API key that matches the current privileges of the user is created automatically. In both cases, the API key is subsequently associated with the rule and used when it runs.
 

@@ -5,11 +5,11 @@ mapped_pages:
 
 # Import dashboards [_import_dashboards]
 
-You can import dashboards from the **Saved Objects*** page under ***Stack Management**. Refer to [Manage saved objects](../find-and-organize/saved-objects.md).
+You can import dashboards from the **Saved Objects** page under **Stack Management**. Refer to [Manage saved objects](../find-and-organize/saved-objects.md).
 
 When importing dashboards, you also import their related objects, such as data views and visualizations. Import options allow you to define how the import should behave with these related objects.
 
-* **Check for existing objects***: When selected, objects are not imported when another object with the same ID already exists in this space or cluster. For example, if you import a dashboard that uses a data view which already exists, the data view is not imported and the dashboard uses the existing data view instead. You can also chose to select manually which of the imported or the existing objects are kept by selecting ***Request action on conflict**.
+* **Check for existing objects**: When selected, objects are not imported when another object with the same ID already exists in this space or cluster. For example, if you import a dashboard that uses a data view which already exists, the data view is not imported and the dashboard uses the existing data view instead. You can also chose to select manually which of the imported or the existing objects are kept by selecting **Request action on conflict**.
 * **Create new objects with random IDs**: All related objects are imported and are assigned a new ID to avoid conflicts.
 
 ![Import panel](../../images/kibana-dashboard-import-saved-object.png "")
@@ -52,7 +52,7 @@ To add interactive Options list and Range slider controls, create the controls,
 
 3. On the **Create control** flyout, from the **Data view** dropdown, select the data view that contains the field you want to use for the **Control**.
 4. In the **Field** list, select the field you want to filter on.
-5. Under **Control type**, select whether the control should be an **Options list*** or a ***Range slider**.
+5. Under **Control type**, select whether the control should be an **Options list** or a **Range slider**.
 
     ::::{tip}
     Range sliders are for Number type fields only.
@@ -127,7 +127,7 @@ Several settings that apply to all controls of the same dashboard are available.
 
         * **Validate user selections** — When selected, any selected option that results in no data is ignored.
         * **Chain controls** — When selected, controls are applied sequentially from left to right, and line by line. Any selected options in one control narrows the available options in the next control.
-        * **Apply selections automatically*** — The dashboard is updated dynamically when options are selected in controls. When this option is disabled, users first need to ***Apply** their control selection before they are applied to the dashboard.
+        * **Apply selections automatically** — The dashboard is updated dynamically when options are selected in controls. When this option is disabled, users first need to **Apply** their control selection before they are applied to the dashboard.
 
     * To remove all controls from the dashboard, click **Delete all**.
 

@@ -356,7 +356,7 @@ Now that you have a complete overview of your web server data, save the dashboar
 1. In the toolbar, click **Save**.
 2. On the **Save dashboard** window, enter `Logs dashboard` in the **Title** field.
 3. Select **Store time with dashboard**.
-4. Click **Save**. You will be identified as the **creator*** of the dashboard. If you or another user edit the dashboard, you can also view the ***last editor** when checking the dashboard information.
+4. Click **Save**. You will be identified as the **creator** of the dashboard. If you or another user edit the dashboard, you can also view the **last editor** when checking the dashboard information.
 
 :::{image} ../../images/kibana-dashboard-creator-editor.png
 :alt: Information panel of a dashboard showing its creator and last editor

@@ -12,9 +12,9 @@ mapped_pages:
 
 3. Add content to the dashboard. You have several options covered in more detail in the [Visualizations section](../visualize.md#panels-editors):
 
-    * [**Create visualization***](../visualize/lens.md). This option is a shortcut to create a chart using ***Lens**, the default visualization editor in {{kib}}.
+    * [**Create visualization**](../visualize/lens.md). This option is a shortcut to create a chart using **Lens**, the default visualization editor in {{kib}}.
     * [**Add panel**](../visualize.md#panels-editors). Choose one of the available panels to add and configure content to your dashboard.
-    * **Add from library***. Select existing content that has already been configured and saved to the ***Visualize Library**.
+    * **Add from library**. Select existing content that has already been configured and saved to the **Visualize Library**.
     * [**Controls**](add-controls.md). Add controls to help filter the content of your dashboard.
 
         :::{image} images/add_content_to_dashboard_8.15.0.png

@@ -13,7 +13,7 @@ mapped_pages:
     ::::
 
 3. Click the dashboard **Title** you want to open.
-4. Make sure that you are in **Edit*** mode to be able to make changes to the dashboard. You can switch between ***Edit*** and ***View** modes from the toolbar.
+4. Make sure that you are in **Edit** mode to be able to make changes to the dashboard. You can switch between **Edit** and **View** modes from the toolbar.
 
     :::{image} https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt619b284e92c2be27/6750f3a512a5eae780936fe3/switch-to-view-mode-8.17.0.gif
     :alt: Switch between Edit and View modes

@@ -7,7 +7,7 @@

 To share a dashboard with a larger audience, click **Share** in the toolbar. For detailed information about the sharing options, refer to [Reporting](../report-and-share.md).

 :::{image} https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt9428300b184af4c6/6763173de7201118db0315a7/share-dashboard-copy-link.gif
 :alt: getting a shareable link for a dashboard
 :::

@@ -19,7 +19,7 @@
 
 ## Export dashboards [export-dashboards]
 
-You can export dashboards from **Stack Management*** > ***Saved Objects**. To configure and start the export:
+You can export dashboards from **Stack Management** > **Saved Objects**. To configure and start the export:
 
 1. Select the dashboard that you want, then click **Export**.
 2. Enable **Include related objects** if you want that objects associated to the selected dashboard, such as data views and visualizations, also get exported. This option is enabled by default and recommended if you plan to import that dashboard again in a different space or cluster.

@@ -7,7 +7,7 @@ mapped_pages:
 
 Learn how to use **Discover** to:
 
-* **Select*** and ***filter** your {{es}} data.
+* **Select** and **filter** your {{es}} data.
 * **Explore** the fields and content of your data in depth.
 * **Present** your findings in a visualization.
 
@@ -132,7 +132,7 @@ In the following example, we’re adding 2 fields: A simple "Hello world" field,
 
 ### Visualize aggregated fields [_visualize_aggregated_fields]
 
-If a field can be [aggregated](../aggregations.md), you can quickly visualize it in detail by opening it in **Lens*** from ***Discover***. ***Lens** is the default visualization editor in {{kib}}.
+If a field can be [aggregated](../aggregations.md), you can quickly visualize it in detail by opening it in **Lens** from **Discover**. **Lens** is the default visualization editor in {{kib}}.
 
 1. In the list of fields, find an aggregatable field. For example, with the sample data, you can look for `day_of_week`.
 
@@ -158,7 +158,7 @@ For geo point fields (![Geo point field icon](../../images/kibana-geoip-icon.png
 You can use **Discover** to compare and diff the field values of multiple results or documents in the table.
 
 1. Select the results you want to compare from the Documents or Results tab in Discover.
-2. From the **Selected*** menu in the table toolbar, choose ***Compare selected**. The comparison view opens and shows the selected results next to each other.
+2. From the **Selected** menu in the table toolbar, choose **Compare selected**. The comparison view opens and shows the selected results next to each other.
 3. Compare the values of each field. By default the first result selected shows as the reference for displaying differences in the other results. When the value remains the same for a given field, it’s displayed in green. When the value differs, it’s displayed in red.
 
     ::::{tip}
@@ -177,7 +177,7 @@ You can use **Discover** to compare and diff the field values of multiple result
 You can quickly copy the content currently displayed in the table for one or several results to your clipboard.
 
 1. Select the results you want to copy.
-2. Open the **Selected*** menu in the table toolbar, and select ***Copy selection as text*** or ***Copy documents as JSON**.
+2. Open the **Selected** menu in the table toolbar, and select **Copy selection as text** or **Copy documents as JSON**.
 
 The content is copied to your clipboard in the selected format. Fields that are not currently added to the table are ignored.
 
@@ -198,7 +198,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.
+        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.
         ::::
 
 3. To navigate to a view of the document that you can bookmark and share, select ** View single document**.
@@ -248,7 +248,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.
 
-Note that in ES|QL mode, the **Documents*** tab is named ***Results**.
+Note that in ES|QL mode, the **Documents** tab is named **Results**.
 
 Learn more about how to use ES|QL queries in [Using ES|QL](try-esql.md).
 

@@ -50,7 +50,7 @@ You can define different settings for the header row and body rows.
 
 ### Limit the sample size [document-explorer-sample-size]
 
-When the number of results returned by your search query (displayed at the top of the **Documents*** or ***Results*** tab) is greater than the value of [`discover:sampleSize`](https://www.elastic.co/guide/en/kibana/current/advanced-options.html#kibana-discover-settings), the number of results displayed in the table is limited to the configured value by default. You can adjust the initial sample size for searches to any number between 10 and `discover:sampleSize` from the ***Display options** located in the table toolbar.
+When the number of results returned by your search query (displayed at the top of the **Documents** or **Results** tab) is greater than the value of [`discover:sampleSize`](https://www.elastic.co/guide/en/kibana/current/advanced-options.html#kibana-discover-settings), the number of results displayed in the table is limited to the configured value by default. You can adjust the initial sample size for searches to any number between 10 and `discover:sampleSize` from the **Display options** located in the table toolbar.
 
 On the last page of the table, a message indicates that you’ve reached the end of the loaded search results. From that message, you can choose to load more results to continue exploring.
 

@@ -18,7 +18,7 @@
 
 ## 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.
+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]
@@ -34,7 +34,7 @@
 1. Set the time range to **Last 7 days**.
 2. Copy the query below:

    ```esql
    FROM kibana_sample_data_logs <1>
    | KEEP machine.os, machine.ram <2>
    ```
@@ -61,7 +61,7 @@

 1. Copy the query below:

    ```esql
    FROM kibana_sample_data_logs
    | KEEP machine.os, machine.ram, geo.dest
    | LIMIT 10
@@ -81,7 +81,7 @@

 1. Copy the query below:

    ```esql
    FROM kibana_sample_data_logs
    | KEEP machine.os, machine.ram, geo.dest
    | SORT machine.ram desc
@@ -113,7 +113,7 @@

 By default, when querying this data set, time series capabilities aren’t active. No visualization is generated and the time picker is disabled.

 ```esql
 FROM kibana_sample_data_ecommerce
 | KEEP customer_first_name, email, products._id.keyword
 ```
@@ -124,7 +124,7 @@

 While still querying the same data set, by adding the `?_start` and `?_tend` parameters based on the `order_date` field, **Discover** enables times series capabilities.

 ```esql
 FROM kibana_sample_data_ecommerce
 | WHERE order_date >= ?_tstart and order_date <= ?_tend
 ```

@@ -18,7 +18,7 @@ To detect change points:
 
 1. In your {{obs-serverless}} project, go to **Machine learning** → **Change point detection**.
 2. Choose a data view or saved search to access the data you want to analyze.
-3. Select a function: **avg**, **max***, ***min**, or **sum**.
+3. Select a function: **avg**, **max**, **min**, or **sum**.
 4. In the time filter, specify a time range over which you want to detect change points.
 5. From the **Metric field** list, select a field you want to check for change points.
 6. (Optional) From the **Split field** list, select a field to split the data by. If the cardinality of the split field exceeds 10,000, only the first 10,000 values, sorted by document count, are analyzed. Use this option when you want to investigate the change point across multiple instances, pods, clusters, and so on. For example, you may want to view CPU utilization split across multiple instances without having to jump across multiple dashboards and visualizations.

@@ -266,7 +266,7 @@ In addition to detecting anomalous behavior in your data, you can use the {{ml-f
 
 To create a forecast in {{kib}}:
 
-1. View your job results (for example, for the `low_request_rate` job) in the **Single Metric Viewer**. To find that view, click the **View series*** button in the ***Actions** column on the **Anomaly Detection** page.
+1. View your job results (for example, for the `low_request_rate` job) in the **Single Metric Viewer**. To find that view, click the **View series** button in the **Actions** column on the **Anomaly Detection** page.
 2. Click **Forecast**.
 
 :::{image} ../../../images/machine-learning-ml-gs-forecast.png

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Adding custom URLs to data frame analytics jobs [ml-dfa-custom-urls]
 
-You can optionally attach one or more custom URLs to your {{dfanalytics-jobs}}. These links can direct you to dashboards, the **Discover** app, or external websites. For example, you can define a custom URL that provides a way for users to drill down to the source data from a {{regression}} job. You can create a custom URL during job creation under **Additional settings** in the **Job details*** step. Alternatively, you can edit or add new custom URLs in the job list by clicking ***Edit** in the **Actions** menu.
+You can optionally attach one or more custom URLs to your {{dfanalytics-jobs}}. These links can direct you to dashboards, the **Discover** app, or external websites. For example, you can define a custom URL that provides a way for users to drill down to the source data from a {{regression}} job. You can create a custom URL during job creation under **Additional settings** in the **Job details** step. Alternatively, you can edit or add new custom URLs in the job list by clicking **Edit** in the **Actions** menu.
 
 :::{image} ../../../images/machine-learning-ml-dfa-custom-url.png
 :alt: Creating a custom URL during job creation

@@ -54,7 +54,7 @@ After you created the E5 {{infer}} endpoint, it’s ready to be used for semanti
 
 ### Alternative methods to download and deploy E5 [alternative-download-deploy-e5]
 
-You can also download and deploy the E5 model either from **{{ml-app}}** > **Trained Models***, from ***Search** > **Indices**, or by using the trained models API in Dev Console.
+You can also download and deploy the E5 model either from **{{ml-app}}** > **Trained Models**, from **Search** > **Indices**, or by using the trained models API in Dev Console.
 
 ::::{note}
 For most cases, the preferred version is the **Intel and Linux optimized** model, it is recommended to download and deploy that version.

@@ -89,7 +89,7 @@ After you created the ELSER {{infer}} endpoint, it’s ready to be used for sema
 
 ### Alternative methods to download and deploy ELSER [alternative-download-deploy]
 
-You can also download and deploy ELSER either from **{{ml-app}}** > **Trained Models***, from ***Search** > **Indices**, or by using the trained models API in Dev Console.
+You can also download and deploy ELSER either from **{{ml-app}}** > **Trained Models**, from **Search** > **Indices**, or by using the trained models API in Dev Console.
 
 ::::{note}
 * For most cases, the preferred version is the **Intel and Linux optimized** model, it is recommended to download and deploy that version.

@@ -15,7 +15,7 @@ After you [deploy a trained model in your cluster](ml-nlp-deploy-models.md), you
 
 ## Add an {{infer}} processor to an ingest pipeline [ml-nlp-inference-processor]
 
-In {{kib}}, you can create and edit pipelines in **{{stack-manage-app}}** > **Ingest Pipelines***. To open ***Ingest Pipelines**, find **{{stack-manage-app}}** in the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects).
+In {{kib}}, you can create and edit pipelines in **{{stack-manage-app}}** > **Ingest Pipelines**. To open **Ingest Pipelines**, find **{{stack-manage-app}}** in the main menu, or use the [global search field](../../overview/kibana-quickstart.md#_finding_your_apps_and_objects).
 
 :::{image} ../../../images/machine-learning-ml-nlp-pipeline-lang.png
 :alt: Creating a pipeline in the Stack Management app

@@ -30,7 +30,7 @@ Move the {{es}} Connector for Tableau to the Tableau Server connectors directory
 
 Restart Tableau Server.
 
-To load data into a workbook, add a **New Data Source** from the **Data*** menu or using the icon. In the ***Connectors*** tab of the ***Connect to Data** modal, select **Elasticsearch by Elastic**.
+To load data into a workbook, add a **New Data Source** from the **Data** menu or using the icon. In the **Connectors** tab of the **Connect to Data** modal, select **Elasticsearch by Elastic**.
 
 $$$apps_tableau_server_from_connector$$$
 ![Select Elasticsearch as the data source](../../../images/elasticsearch-reference-apps_tableau_server_from_connector.png "")