[obs] Cleanup formatting

solutions/observability/cloud/monitor-amazon-web-services-aws-with-beats.md

@@ -568,7 +568,7 @@ You can now start {{metricbeat}}:
 
 ## Step 10: Visualize metrics [aws-step-ten]
 
-Now that the metrics are being streamed to {{es}} we can visualize them in {{kib}}. To open **Infrastructure inventory**, find **Infrastructure*** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Make sure to show the ***AWS** source and the **EC2 Instances**:
+Now that the metrics are being streamed to {{es}} we can visualize them in {{kib}}. To open **Infrastructure inventory**, find **Infrastructure** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Make sure to show the **AWS** source and the **EC2 Instances**:
 
 :::{image} ../../../images/observability-EC2-instances.png
 :alt: Your EC2 Infrastructure

solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md

@@ -148,7 +148,7 @@ The following table shows the type of data ingested by the supported AWS service
 :sync: stack
 
 1. In {{kib}}, go to the **Observability** UI and click **Add Data**.
-2. Under **What do you want to monitor?** select **Cloud***, ***AWS**, and then select **AWS Firehose**.
+2. Under **What do you want to monitor?** select **Cloud**, **AWS**, and then select **AWS Firehose**.
 
     :::{image} ../../../images/observability-quickstart-aws-firehose-entry-point.png
     :alt: AWS Firehose entry point
@@ -166,7 +166,7 @@ The following table shows the type of data ingested by the supported AWS service
 
 1. [Create a new {{obs-serverless}} project](../../../solutions/observability/get-started/create-an-observability-project.md), or open an existing one.
 2. In your {{obs-serverless}} project, go to **Add Data**.
-3. Under **What do you want to monitor?** select **Cloud***, ***AWS**, and then select **AWS Firehose**.
+3. Under **What do you want to monitor?** select **Cloud**, **AWS**, and then select **AWS Firehose**.
 
     :::{image} ../../../images/serverless-quickstart-aws-firehose-entry-point.png
     :alt: AWS Firehose entry point
@@ -196,4 +196,4 @@ Here is an example of the VPC Flow logs dashboard:
 :class: screenshot
 :::
 
-Refer to [What is Elastic {{observability}}?](../../../solutions/observability/get-started/what-is-elastic-observability.md) for a description of other useful features.
+Refer to [What is Elastic {{observability}}?](../../../solutions/observability/get-started/what-is-elastic-observability.md) for a description of other useful features.

solutions/observability/incident-management/alerting.md

@@ -27,7 +27,7 @@ On the **Alerts** page, the Alerts table provides a snapshot of alerts occurring
 :class: screenshot
 :::
 
-You can filter this table by alert status or time period, customize the visible columns, and search for specific alerts (for example, alerts related to a specific service or environment) using KQL. Select **View alert detail** from the **More actions*** menu ![action menu](../../../images/serverless-boxesHorizontal.svg ""), or click the Reason link for any alert to [view alert](../../../solutions/observability/incident-management/view-alerts.md) in detail, and you can then either ***View in app** or **View rule details**.
+You can filter this table by alert status or time period, customize the visible columns, and search for specific alerts (for example, alerts related to a specific service or environment) using KQL. Select **View alert detail** from the **More actions** menu ![action menu](../../../images/serverless-boxesHorizontal.svg ""), or click the Reason link for any alert to [view alert](../../../solutions/observability/incident-management/view-alerts.md) in detail, and you can then either **View in app** or **View rule details**.
 
 
 ## Next steps [observability-alerting-next-steps]

solutions/observability/incident-management/create-an-inventory-rule.md

@@ -22,7 +22,7 @@ Based on the resources listed on the **Infrastructure inventory** page within th
 Additionally, each rule can be defined using multiple conditions that combine metrics and thresholds to create precise notifications and reduce false positives.
 
 1. To access this page, go to **{{observability}}** → **Infrastructure**.
-2. On the **Infrastructure inventory** page or the **Metrics Explorer*** page, click ***Alerts and rules** → **Infrastructure**.
+2. On the **Infrastructure inventory** page or the **Metrics Explorer** page, click **Alerts and rules** → **Infrastructure**.
 3. Select **Create inventory rule**.
 
 ::::{tip}

solutions/observability/incident-management/create-failed-transaction-rate-threshold-rule.md

@@ -25,7 +25,7 @@ You can create a failed transaction rate threshold rule to alert you when the ra
 :::
 
 ::::{tip}
-These steps show how to use the **Alerts** UI. You can also create a failed transaction rate threshold rule directly from any page within **Applications***. Click the ***Alerts and rules*** button, and select ***Create threshold rule*** and then ***Failed transaction rate***. When you create a rule this way, the ***Name** and **Tags** fields will be prepopulated but you can still change these.
+These steps show how to use the **Alerts** UI. You can also create a failed transaction rate threshold rule directly from any page within **Applications**. Click the **Alerts and rules** button, and select **Create threshold rule** and then **Failed transaction rate**. When you create a rule this way, the **Name** and **Tags** fields will be prepopulated but you can still change these.
 
 ::::
 

solutions/observability/incident-management/create-latency-threshold-rule.md

@@ -25,7 +25,7 @@ You can create a latency threshold rule to alert you when the latency of a speci
 :::
 
 ::::{tip}
-These steps show how to use the **Alerts** UI. You can also create a latency threshold rule directly from any page within **Applications***. Click the ***Alerts and rules*** button, and select ***Create threshold rule*** and then ***Latency***. When you create a rule this way, the ***Name** and **Tags** fields will be prepopulated but you can still change these.
+These steps show how to use the **Alerts** UI. You can also create a latency threshold rule directly from any page within **Applications**. Click the **Alerts and rules** button, and select **Create threshold rule** and then **Latency**. When you create a rule this way, the **Name** and **Tags** fields will be prepopulated but you can still change these.
 
 ::::
 
@@ -36,7 +36,7 @@ To create your latency threshold rule:
 2. Select **Manage Rules** from the **Alerts** page, and select **Create rule**.
 3. Enter a **Name** for your rule, and any optional **Tags** for more granular reporting (leave blank if unsure).
 4. Select the **Latency threshold** rule type from the APM use case.
-5. Select the appropriate **Service**, **Type***, ***Environment*** and ***Name*** (or leave ***ALL** to include all options). Alternatively, you can select **Use KQL Filter** and enter a KQL expression to limit the scope of your rule.
+5. Select the appropriate **Service**, **Type**, **Environment** and **Name** (or leave **ALL** to include all options). Alternatively, you can select **Use KQL Filter** and enter a KQL expression to limit the scope of your rule.
 6. Define the threshold and period:
 
     * **When**: Choose between `Average`, `95th percentile`, or `99th percentile`.
@@ -169,7 +169,7 @@ This guide will create an alert for an error group ID based on the following cri
 * Check every 1 minute
 * Send the alert via email to the site reliability team
 
-From any page in **Applications**, select **Alerts and rules*** → ***Create threshold rule** → **Latency threshold**. Change the name of the alert (if you wish), but do not edit the tags.
+From any page in **Applications**, select **Alerts and rules** → **Create threshold rule** → **Latency threshold**. Change the name of the alert (if you wish), but do not edit the tags.
 
 Based on the criteria above, define the following rule details:
 

solutions/observability/incident-management/create-manage-cases.md

@@ -37,7 +37,7 @@ Open a new case to keep track of issues and share the details with colleagues. T
 8. After you’ve completed all of the required fields, click **Create case**.
 
 ::::{tip}
-You can also create a case from an alert or add an alert to an existing case. From the **Alerts** page, click the **More options*** ![More actions](../../../images/serverless-boxesHorizontal.svg "") icon and choose either ***Add to existing case** or **Create new case**, and select or complete the details as required.
+You can also create a case from an alert or add an alert to an existing case. From the **Alerts** page, click the **More options** ![More actions](../../../images/serverless-boxesHorizontal.svg "") icon and choose either **Add to existing case** or **Create new case**, and select or complete the details as required.
 
 ::::
 

solutions/observability/incident-management/view-alerts.md

@@ -65,7 +65,7 @@ There are three common alert statuses:
 ::::{admonition} Flapping alerts
 :class: note
 
-The flapping state is possible only if you have enabled alert flapping detection. Go to the **Alerts** page and click **Manage Rules*** to navigate to the {{obs-serverless}} ***{{rules-app}}** page. Click **Settings** then set the look back window and threshold that are used to determine whether alerts are flapping. For example, you can specify that the alert must change status at least 6 times in the last 10 runs. If the rule has actions that run when the alert status changes, those actions are suppressed while the alert is flapping.
+The flapping state is possible only if you have enabled alert flapping detection. Go to the **Alerts** page and click **Manage Rules** to navigate to the {{obs-serverless}} **{{rules-app}}** page. Click **Settings** then set the look back window and threshold that are used to determine whether alerts are flapping. For example, you can specify that the alert must change status at least 6 times in the last 10 runs. If the rule has actions that run when the alert status changes, those actions are suppressed while the alert is flapping.
 
 ::::
 
@@ -86,7 +86,7 @@ To view the alert in the app that triggered it:
 Use the toolbar buttons in the upper-left of the alerts table to customize the columns you want displayed:
 
 * **Columns**: Reorder the columns.
-* ***x* fields sorted**: Sort the table by one or more columns.
+* **x* fields sorted**: Sort the table by one or more columns.
 * **Fields**: Select the fields to display in the table.
 
 For example, click **Fields** and choose the `Maintenance Windows` field. If an alert was affected by a maintenance window, its identifier appears in the new column. For more information about their impact on alert notifications, refer to [{{maint-windows-cap}}](../../../explore-analyze/alerts-cases/alerts/maintenance-windows.md).

solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md

@@ -180,7 +180,7 @@ The **Anomalies** tab displays a list of each single metric {{anomaly-detect}} j
 
 Along with the name of each anomaly job, detected anomalies with a severity score equal to 50 or higher are listed. These scores represent a severity of "warning" or higher in the selected time period. The **summary** value represents the increase between the actual value and the expected ("typical") value of the host metric in the anomaly record result.
 
-To drill down and analyze the metric anomaly, select **Actions** → **Open in Anomaly Explorer***. You can also select ***Actions** → **Show in Inventory** to view the host Inventory page, filtered by the specific metric.
+To drill down and analyze the metric anomaly, select **Actions** → **Open in Anomaly Explorer**. You can also select **Actions** → **Show in Inventory** to view the host Inventory page, filtered by the specific metric.
 
 :::{image} ../../../images/serverless-anomalies-overlay.png
 :alt: Anomalies