diff --git a/explore-analyze/alerts/kibana/alerting-setup.md b/explore-analyze/alerts/kibana/alerting-setup.md
index a248a9f03e..361f8a0637 100644
--- a/explore-analyze/alerts/kibana/alerting-setup.md
+++ b/explore-analyze/alerts/kibana/alerting-setup.md
@@ -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.
 
diff --git a/explore-analyze/dashboards/_import_dashboards.md b/explore-analyze/dashboards/_import_dashboards.md
index 124abf943d..f0c3b0cd1a 100644
--- a/explore-analyze/dashboards/_import_dashboards.md
+++ b/explore-analyze/dashboards/_import_dashboards.md
@@ -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 "")
diff --git a/explore-analyze/dashboards/add-controls.md b/explore-analyze/dashboards/add-controls.md
index 0e8bf76e94..77177bcd99 100644
--- a/explore-analyze/dashboards/add-controls.md
+++ b/explore-analyze/dashboards/add-controls.md
@@ -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**.
 
diff --git a/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md b/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md
index 0c41d8a463..a3723dca95 100644
--- a/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md
+++ b/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md
@@ -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
diff --git a/explore-analyze/dashboards/create-dashboard.md b/explore-analyze/dashboards/create-dashboard.md
index 7870c8cd2b..1be1b20c90 100644
--- a/explore-analyze/dashboards/create-dashboard.md
+++ b/explore-analyze/dashboards/create-dashboard.md
@@ -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
diff --git a/explore-analyze/dashboards/open-dashboard.md b/explore-analyze/dashboards/open-dashboard.md
index cf082ad5c3..2973b5d326 100644
--- a/explore-analyze/dashboards/open-dashboard.md
+++ b/explore-analyze/dashboards/open-dashboard.md
@@ -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
diff --git a/explore-analyze/dashboards/sharing.md b/explore-analyze/dashboards/sharing.md
index f8e30579c2..7ce6059b9f 100644
--- a/explore-analyze/dashboards/sharing.md
+++ b/explore-analyze/dashboards/sharing.md
@@ -19,7 +19,7 @@ When sharing a dashboard with a link while a panel is in maximized view, the gen
 
 ## 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.
diff --git a/explore-analyze/discover/discover-get-started.md b/explore-analyze/discover/discover-get-started.md
index d758354abc..095ce25d0e 100644
--- a/explore-analyze/discover/discover-get-started.md
+++ b/explore-analyze/discover/discover-get-started.md
@@ -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).
 
diff --git a/explore-analyze/discover/document-explorer.md b/explore-analyze/discover/document-explorer.md
index c2067ff8cc..5d637b21ed 100644
--- a/explore-analyze/discover/document-explorer.md
+++ b/explore-analyze/discover/document-explorer.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.
 
diff --git a/explore-analyze/discover/try-esql.md b/explore-analyze/discover/try-esql.md
index 91b7a75a0e..0fe49d71f5 100644
--- a/explore-analyze/discover/try-esql.md
+++ b/explore-analyze/discover/try-esql.md
@@ -18,7 +18,7 @@ For the complete {{esql}} documentation, including tutorials, examples and the f
 
 ## 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]
diff --git a/explore-analyze/machine-learning/aiops-labs/observability-aiops-detect-change-points.md b/explore-analyze/machine-learning/aiops-labs/observability-aiops-detect-change-points.md
index 82bd3c9dbb..427cbddaec 100644
--- a/explore-analyze/machine-learning/aiops-labs/observability-aiops-detect-change-points.md
+++ b/explore-analyze/machine-learning/aiops-labs/observability-aiops-detect-change-points.md
@@ -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.
diff --git a/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md b/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md
index 19a807f9d8..65a1036b5a 100644
--- a/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md
+++ b/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md
@@ -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
diff --git a/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-custom-urls.md b/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-custom-urls.md
index 6db53d6c83..7c4fa27788 100644
--- a/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-custom-urls.md
+++ b/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-custom-urls.md
@@ -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
diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-e5.md b/explore-analyze/machine-learning/nlp/ml-nlp-e5.md
index cd4fa6f1da..fe269a5142 100644
--- a/explore-analyze/machine-learning/nlp/ml-nlp-e5.md
+++ b/explore-analyze/machine-learning/nlp/ml-nlp-e5.md
@@ -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.
diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-elser.md b/explore-analyze/machine-learning/nlp/ml-nlp-elser.md
index b1ecf424e8..750fc1c2fb 100644
--- a/explore-analyze/machine-learning/nlp/ml-nlp-elser.md
+++ b/explore-analyze/machine-learning/nlp/ml-nlp-elser.md
@@ -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.
diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-inference.md b/explore-analyze/machine-learning/nlp/ml-nlp-inference.md
index d9ea5022ea..b66dbf4b43 100644
--- a/explore-analyze/machine-learning/nlp/ml-nlp-inference.md
+++ b/explore-analyze/machine-learning/nlp/ml-nlp-inference.md
@@ -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
diff --git a/explore-analyze/query-filter/languages/sql-client-apps-tableau-server.md b/explore-analyze/query-filter/languages/sql-client-apps-tableau-server.md
index 63a64e7674..840c70f1d7 100644
--- a/explore-analyze/query-filter/languages/sql-client-apps-tableau-server.md
+++ b/explore-analyze/query-filter/languages/sql-client-apps-tableau-server.md
@@ -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 "")
diff --git a/explore-analyze/query-filter/languages/sql-data-types.md b/explore-analyze/query-filter/languages/sql-data-types.md
index d4dea95e24..fe142b7858 100644
--- a/explore-analyze/query-filter/languages/sql-data-types.md
+++ b/explore-analyze/query-filter/languages/sql-data-types.md
@@ -33,7 +33,7 @@ mapped_pages:
 | *types not mentioned above* | `unsupported` | OTHER | 0 |
 
 ::::{note}
-Most of {{es}} [data types](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html) are available in Elasticsearch SQL, as indicated above. As one can see, all of {{es}} [data types](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html) are mapped to the data type with the same name in Elasticsearch SQL, with the exception of **date** data type which is mapped to **datetime*** in Elasticsearch SQL. This is to avoid confusion with the ANSI SQL types ***DATE** (date only) and **TIME** (time only), which are also supported by Elasticsearch SQL in queries (with the use of [`CAST`](sql-functions-type-conversion.md#sql-functions-type-conversion-cast)/[`CONVERT`](sql-functions-type-conversion.md#sql-functions-type-conversion-convert)), but don’t correspond to an actual mapping in {{es}} (see the [`table`](#es-sql-only-types) below).
+Most of {{es}} [data types](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html) are available in Elasticsearch SQL, as indicated above. As one can see, all of {{es}} [data types](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html) are mapped to the data type with the same name in Elasticsearch SQL, with the exception of **date** data type which is mapped to **datetime** in Elasticsearch SQL. This is to avoid confusion with the ANSI SQL types **DATE** (date only) and **TIME** (time only), which are also supported by Elasticsearch SQL in queries (with the use of [`CAST`](sql-functions-type-conversion.md#sql-functions-type-conversion-cast)/[`CONVERT`](sql-functions-type-conversion.md#sql-functions-type-conversion-convert)), but don’t correspond to an actual mapping in {{es}} (see the [`table`](#es-sql-only-types) below).
 ::::
 
 
diff --git a/explore-analyze/report-and-share/automating-report-generation.md b/explore-analyze/report-and-share/automating-report-generation.md
index 18a6749adf..2cb21e89ae 100644
--- a/explore-analyze/report-and-share/automating-report-generation.md
+++ b/explore-analyze/report-and-share/automating-report-generation.md
@@ -140,7 +140,7 @@ The response payload of a request to generate a report includes the path to down
 
 * **`400` (Bad Request)**: When sending requests to the POST URL, if you don’t use `POST` as the HTTP method, or if your request is missing the `kbn-xsrf` header, Kibana will return a code `400` status response for the request.
 * **`503` (Service Unavailable)**: When using the `path` to request the download, you will get a `503` status response if report generation hasn’t completed yet. The response will include a `Retry-After` header. You can set the script to wait the number of seconds in the `Retry-After` header, and then repeat if needed, until the report is complete.
-* **`500` (Internal Server Error)***: When using the `path` to request the download, you will get a `500` status response if the report isn’t available due to an error when generating the report. More information is available at ***Management > Kibana > Reporting**.
+* **`500` (Internal Server Error)**: When using the `path` to request the download, you will get a `500` status response if the report isn’t available due to an error when generating the report. More information is available at **Management > Kibana > Reporting**.
 
 
 ## Deprecated report URLs [deprecated-report-urls]
diff --git a/explore-analyze/report-and-share/reporting-troubleshooting-csv.md b/explore-analyze/report-and-share/reporting-troubleshooting-csv.md
index f821d34bf9..b8a2899668 100644
--- a/explore-analyze/report-and-share/reporting-troubleshooting-csv.md
+++ b/explore-analyze/report-and-share/reporting-troubleshooting-csv.md
@@ -72,7 +72,7 @@ The listing of reports in **Stack Management > Reporting** allows you to inspect
 
 1. Go to **Stack Management > Reporting** and click the info icon next to a report.
 2. In the footer of the report flyout, click **Actions**.
-3. Click **Inspect query in Console*** in the ***Actions** menu.
+3. Click **Inspect query in Console** in the **Actions** menu.
 4. This will open the **Console** application, pre-filled with the queries used to generate the CSV export.
 
 :::{image} https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt4758e67aaec715d9/67897d0be92e090a6dc626a8/inspect-query-from-csv-export.gif
diff --git a/explore-analyze/visualize.md b/explore-analyze/visualize.md
index 17470025ef..6775f0c799 100644
--- a/explore-analyze/visualize.md
+++ b/explore-analyze/visualize.md
@@ -11,7 +11,7 @@ Use one of the editors to create visualizations of your data. Each editor offers
 
 $$$panels-editors$$$
 
-| **Content*** | ***Panel type*** | ***Description** |
+| **Content** | **Panel type** | **Description** |
 | --- | --- | --- |
 | Visualizations | [Lens](visualize/lens.md) | The default editor for creating powerful [charts](visualize/supported-chart-types.md) in {{kib}} |
 | [ES|QL](https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-kibana.md) | Create visualizations from ES|QL queries |
diff --git a/explore-analyze/visualize/esorql.md b/explore-analyze/visualize/esorql.md
index e9240f7f9f..ddf5945bac 100644
--- a/explore-analyze/visualize/esorql.md
+++ b/explore-analyze/visualize/esorql.md
@@ -18,7 +18,7 @@ You can then **Save** and add it to an existing or a new dashboard using the sav
 ## Create from dashboard [_create_from_dashboard]
 
 1. From your dashboard, select **Add panel**.
-2. Choose **ES|QL*** under ***Visualizations***. An ES|QL editor appears and lets you configure your query and its associated visualization. The ***Suggestions** panel can help you find alternative ways to configure the visualization.
+2. Choose **ES|QL** under **Visualizations**. An ES|QL editor appears and lets you configure your query and its associated visualization. The **Suggestions** panel can help you find alternative ways to configure the visualization.
 
     ::::{tip}
     Check the [ES|QL reference](https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-language.html) to get familiar with the syntax and optimize your query.
diff --git a/explore-analyze/visualize/field-statistics.md b/explore-analyze/visualize/field-statistics.md
index ab92faa76d..2513d13fd8 100644
--- a/explore-analyze/visualize/field-statistics.md
+++ b/explore-analyze/visualize/field-statistics.md
@@ -8,7 +8,7 @@ mapped_pages:
 **Field statistics** panels allow you to display a table with additional field information in your dashboards, such as document count, values, and distribution.
 
 1. From your dashboard, select **Add panel**.
-2. Choose **Field statistics*** under ***Visualizations**. An ES|QL editor appears and lets you configure your query with the fields and information that you want to show.
+2. Choose **Field statistics** under **Visualizations**. An ES|QL editor appears and lets you configure your query with the fields and information that you want to show.
 
     ::::{tip}
     Check the [ES|QL reference](https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-language.html) to get familiar with the syntax and optimize your query.
diff --git a/explore-analyze/visualize/lens.md b/explore-analyze/visualize/lens.md
index f1aaf2f74a..c5003774ba 100644
--- a/explore-analyze/visualize/lens.md
+++ b/explore-analyze/visualize/lens.md
@@ -48,7 +48,7 @@ Edit and delete.
 6. Click **Apply and close**.
 
 ::::{tip}
-Use the **Edit visualization*** flyout to make edits without having to leave the dashboard, or click ***Edit in Lens** in the flyout to make edits using the Lens application.
+Use the **Edit visualization** flyout to make edits without having to leave the dashboard, or click **Edit in Lens** in the flyout to make edits using the Lens application.
 ::::
 
 
@@ -362,7 +362,7 @@ The options available can vary based on the type of chart you’re setting up. F
 
 **Change the legend’s display**
 
-With the **Visibility***, ***Position***, and ***Width** options, you can adjust the way the legend appears in or next to the visualization.
+With the **Visibility**, **Position**, and **Width** options, you can adjust the way the legend appears in or next to the visualization.
 
 **Truncate long labels**
 
@@ -370,9 +370,9 @@ With the **Label truncation** option, you can keep your legend minimal in case o
 
 **Show additional statistics for time series charts**
 
-To make your legends as informative as possible, you can show some additional **Statistics*** for charts with a timestamp on one of the axes, and add a ***Series header**.
+To make your legends as informative as possible, you can show some additional **Statistics** for charts with a timestamp on one of the axes, and add a **Series header**.
 
-**Bar***, ***Line*** and ***Area** charts can show the following values:
+**Bar**, **Line** and **Area** charts can show the following values:
 
 * **Average**: Average value considering all data points in the chart
 * **Median**: Median value considering all data points in the chart
diff --git a/explore-analyze/visualize/link-panels.md b/explore-analyze/visualize/link-panels.md
index 0b5a8b4154..fb4c6ac02b 100644
--- a/explore-analyze/visualize/link-panels.md
+++ b/explore-analyze/visualize/link-panels.md
@@ -5,7 +5,7 @@ mapped_pages:
 
 # Link panels [dashboard-links]
 
-You can use **Links*** panels to create links to other dashboards or external websites. When creating links to other dashboards, you have the option to carry the time range, query, and filters to apply over to the linked dashboard. Links to external websites follow the [`externalUrl.policy`](https://www.elastic.co/guide/en/kibana/current/url-drilldown-settings-kb.html#external-URL-policy) settings. ***Links** panels support vertical and horizontal layouts and may be saved to the **Library** for use in other dashboards.
+You can use **Links** panels to create links to other dashboards or external websites. When creating links to other dashboards, you have the option to carry the time range, query, and filters to apply over to the linked dashboard. Links to external websites follow the [`externalUrl.policy`](https://www.elastic.co/guide/en/kibana/current/url-drilldown-settings-kb.html#external-URL-policy) settings. **Links** panels support vertical and horizontal layouts and may be saved to the **Library** for use in other dashboards.
 
 :::{image} ../../images/kibana-dashboard_links_panel.png
 :alt: A screenshot displaying the new links panel
@@ -22,11 +22,11 @@ You can use **Links*** panels to create links to other dashboards or external we
 To add a links panel to your dashboard:
 
 1. From your dashboard, select **Add panel**.
-2. In the **Add panel*** flyout, select ***Links***. The ***Create links panel** flyout appears and lets you add the link you want to display.
+2. In the **Add panel** flyout, select **Links**. The **Create links panel** flyout appears and lets you add the link you want to display.
 3. Choose between the panel displaying vertically or horizontally on your dashboard and add your link.
 4. Specify the following:
 
-    * **Go to*** - Select **Dashboard** to link to another dashboard, or ***URL** to link to an external website.
+    * **Go to** - Select **Dashboard** to link to another dashboard, or **URL** to link to an external website.
     * **Choose destination** - Use the dropdown to select another dashboard or enter an external URL.
     * **Text** - Enter text for the link, which displays in the panel.
     * **Options** - When linking to another dashboard, use the sliders to use the filters and queries from the original dashboard, use the date range from the original dashboard, or open the dashboard in a new tab. When linking to an external URL, use the sliders to open the URL in a new tab, or encode the URL.
@@ -40,7 +40,7 @@ To add a links panel to your dashboard:
 To add a previously saved links panel to another dashboard:
 
 1. From your dashboard, select **Add from library**.
-2. In the **Add from library*** flyout, select ***Links*** from the ***Types** dropdown and then select the Links panel you want to add.
+2. In the **Add from library** flyout, select **Links** from the **Types** dropdown and then select the Links panel you want to add.
 3. Click **Save**.
 
 
diff --git a/explore-analyze/visualize/maps/maps-getting-started.md b/explore-analyze/visualize/maps/maps-getting-started.md
index 40fb19eeaf..e9248e8051 100644
--- a/explore-analyze/visualize/maps/maps-getting-started.md
+++ b/explore-analyze/visualize/maps/maps-getting-started.md
@@ -41,12 +41,12 @@ When you complete this tutorial, you’ll have a map that looks like this:
 
 The first layer you’ll add is a choropleth layer to shade world countries by web log traffic. Darker shades will symbolize countries with more web log traffic, and lighter shades will symbolize countries with less traffic.
 
-1. Click **Add layer***, and then click ***Choropleth**.
-2. From the **EMS boundaries*** dropdown menu, select ***World Countries**.
+1. Click **Add layer**, and then click **Choropleth**.
+2. From the **EMS boundaries** dropdown menu, select **World Countries**.
 3. In **Statistics source**, set:
 
-    * **Data view*** to ***kibana_sample_data_logs**
-    * **Join field*** to ***geo.dest**
+    * **Data view** to **kibana_sample_data_logs**
+    * **Join field** to **geo.dest**
 
 4. Click **Add and continue**.
 5. In **Layer settings**, set:
@@ -64,7 +64,7 @@ The first layer you’ll add is a choropleth layer to shade world countries by w
 
     * Set **Fill color > As number** to the grey color ramp.
     * Set **Border color** to white.
-    * Under **Label***, change ***By value*** to ***Fixed**.
+    * Under **Label**, change **By value** to **Fixed**.
 
 8. Click **Keep changes**.
 
@@ -86,8 +86,8 @@ To avoid overwhelming the user with too much data at once, you’ll add two laye
 
 This layer displays web log documents as points. The layer is only visible when users zoom in.
 
-1. Click **Add layer***, and then click ***Documents**.
-2. Set **Data view*** to ***kibana_sample_data_logs**.
+1. Click **Add layer**, and then click **Documents**.
+2. Set **Data view** to **kibana_sample_data_logs**.
 3. Click **Add and continue**.
 4. In **Layer settings**, set:
 
@@ -95,9 +95,9 @@ This layer displays web log documents as points. The layer is only visible when
     * **Visibility** to the range [9, 24]
     * **Opacity** to 100%
 
-5. Add a tooltip field and select **agent***, ***bytes***, ***clientip***, ***host***, ***machine.os***, ***request***, ***response***, and ***timestamp**.
+5. Add a tooltip field and select **agent**, **bytes**, **clientip**, **host**, **machine.os**, **request**, **response**, and **timestamp**.
 6. In **Scaling**, enable **Limit results to 10,000.**
-7. In **Layer style***, set ***Fill color*** to ***#2200FF**.
+7. In **Layer style**, set **Fill color** to **#2200FF**.
 8. Click **Keep changes**.
 
     Your map will look like this from zoom level 9 to 24:
@@ -113,8 +113,8 @@ This layer displays web log documents as points. The layer is only visible when
 
 You’ll create a layer for [aggregated data](../../aggregations.md) and make it visible only when the map is zoomed out. Darker colors will symbolize grids with more web log traffic, and lighter colors will symbolize grids with less traffic. Larger circles will symbolize grids with more total bytes transferred, and smaller circles will symbolize grids with less bytes transferred.
 
-1. Click **Add layer***, and select ***Clusters**.
-2. Set **Data view*** to ***kibana_sample_data_logs**.
+1. Click **Add layer**, and select **Clusters**.
+2. Set **Data view** to **kibana_sample_data_logs**.
 3. Click **Add and continue**.
 4. In **Layer settings**, set:
 
@@ -124,11 +124,11 @@ You’ll create a layer for [aggregated data](../../aggregations.md) and make it
 
 5. In **Metrics**:
 
-    * Set **Aggregation*** to ***Count**.
+    * Set **Aggregation** to **Count**.
     * Click **Add metric**.
-    * Set **Aggregation*** to ***Sum*** with ***Field*** set to ***bytes**.
+    * Set **Aggregation** to **Sum** with **Field** set to **bytes**.
 
-6. In **Layer style***, change ***Symbol size**:
+6. In **Layer style**, change **Symbol size**:
 
     * Set **By value** to **sum bytes**.
     * Set the min size to 7 and the max size to 25 px.
@@ -156,7 +156,7 @@ Now that your map is complete, save it and return to the dashboard.
 View your geospatial data alongside a heat map and pie chart, and then filter the data. When you apply a filter in one panel, it is applied to all panels on the dashboard.
 
 1. Click **Add from library** to open a list of panels that you can add to the dashboard.
-2. Add **[Logs] Unique Destination Heatmap*** and ***[Logs] Bytes distribution** to the dashboard.
+2. Add **[Logs] Unique Destination Heatmap** and **[Logs] Bytes distribution** to the dashboard.
 
     :::{image} ../../../images/kibana-gs_dashboard_with_map.png
     :alt: Map in a dashboard with 2 other panels
@@ -168,7 +168,7 @@ View your geospatial data alongside a heat map and pie chart, and then filter th
 5. Set a filter from the map:
 
     1. Open a tooltip by clicking anywhere in the United States vector.
-    2. To show only documents where **geo.src*** is ***US***, click the filter icon ![filter icon](../../../images/kibana-gs-filter-icon.png "")in the row for ***ISO 3066-1 alpha-2**.
+    2. To show only documents where **geo.src** is **US**, click the filter icon ![filter icon](../../../images/kibana-gs-filter-icon.png "")in the row for **ISO 3066-1 alpha-2**.
 
         :::{image} ../../../images/kibana-gs_tooltip_filter.png
         :alt: Tooltip on map
diff --git a/explore-analyze/visualize/maps/maps-vector-style-properties.md b/explore-analyze/visualize/maps/maps-vector-style-properties.md
index 1b29c68f6c..ff75ee2c40 100644
--- a/explore-analyze/visualize/maps/maps-vector-style-properties.md
+++ b/explore-analyze/visualize/maps/maps-vector-style-properties.md
@@ -52,9 +52,9 @@ Available icons
 
 Custom Icons
 
-You can also use your own SVG icon to style Point features in your map. In **Layer settings*** open the **icon** dropdown, and click the ***Add custom icon** button. For best results, your SVG icon should be monochrome and have limited details.
+You can also use your own SVG icon to style Point features in your map. In **Layer settings** open the **icon** dropdown, and click the **Add custom icon** button. For best results, your SVG icon should be monochrome and have limited details.
 
-Dynamic styling in **Elastic Maps*** requires rendering SVG icons as PNGs using a [signed distance function](https://en.wikipedia.org/wiki/Signed_distance_function). As a result, sharp corners and intricate details may not render correctly. Modifying the settings under ***Advanced Options*** in the ***Add custom icon** modal may improve rendering.
+Dynamic styling in **Elastic Maps** requires rendering SVG icons as PNGs using a [signed distance function](https://en.wikipedia.org/wiki/Signed_distance_function). As a result, sharp corners and intricate details may not render correctly. Modifying the settings under **Advanced Options** in the **Add custom icon** modal may improve rendering.
 
 Manage your custom icons in [settings](maps-settings.md).