Use correct arrows in menu paths (elastic#194)

---------

Co-authored-by: Brandon Morelli <bmorelli25@gmail.com>

docs/aiops/aiops-analyze-spikes.mdx

@@ -18,7 +18,7 @@ to help you find and investigate the causes of unusual spikes or drops in log ra
 
 To analyze log spikes and drops:
 
-1. From the main menu in Elastic ((observability)), select **AIOps -> Log rate analysis**.
+1. From the main menu in Elastic ((observability)), select **AIOps → Log rate analysis**.
 1. Choose a data view or saved search to access the log data you want to analyze.
 1. In the histogram chart, click a spike (or drop) to start the analysis.
 

docs/aiops/aiops-detect-anomalies.mdx

@@ -48,7 +48,7 @@ To learn more about anomaly detection, refer to the [((ml))](((ml-docs))/ml-ad-o
 
 # Create and run an anomaly detection job
 
-1. From the main menu in Elastic ((observability)), select **AIOps -> Anomaly detection**.
+1. From the main menu in Elastic ((observability)), select **AIOps → Anomaly detection**.
 1. Click **Create anomaly detection job** (or **Create job** if other jobs exist).
 1. Choose a data view or saved search to access the data you want to analyze.
 1. Select the wizard for the type of job you want to create.
@@ -150,7 +150,7 @@ If a value is outside of this area then it will usually be identified as anomalo
 
 To explore your data:
 
-1. If the **Single Metric Explorer** is not already open, go to **AIOps -> Anomaly detection** and click the Single Metric Explorer icon next to the job you created.
+1. If the **Single Metric Explorer** is not already open, go to **AIOps → Anomaly detection** and click the Single Metric Explorer icon next to the job you created.
 Note that the Single Metric Explorer icon will be grayed out for advanced or multi-metric jobs.
 1. In the time filter, specify a time range that covers the majority of the analyzed data points.
 1. Notice that the model improves as it processes more data.
@@ -219,7 +219,7 @@ You might use a job like this if you want to look at both high and low request r
 To view advanced or multi-metric results in the
 **Anomaly Explorer**:
 
-1. If the **Anomaly Explorer** is not already open, go to **AIOps -> Anomaly detection** and click the Anomaly Explorer icon next to the job you created.
+1. If the **Anomaly Explorer** is not already open, go to **AIOps → Anomaly detection** and click the Anomaly Explorer icon next to the job you created.
 1. In the time filter, specify a time range that covers the majority of the analyzed data points.
 1. If you specified influencers during job creation, the view includes a list of the top influencers for all of the detected anomalies in that same time period.
 The list includes maximum anomaly scores, which in this case are aggregated for each influencer, for each bucket, across all detectors.

docs/aiops/aiops-detect-change-points.mdx

@@ -25,7 +25,7 @@ to detect change points. This aggregation can detect change points when:
 
 To detect change points:
 
-1. From the main menu in Elastic ((observability)), select **AIOps -> Change point detection**.
+1. From the main menu in Elastic ((observability)), select **AIOps → Change point detection**.
 1. Choose a data view or saved search to access the data you want to analyze.
 1. Select a function: **avg**, **max**, **min**, or **sum**.
 1. In the time filter, specify a time range over which you want to detect change points.

docs/aiops/aiops-tune-anomaly-detection-job.mdx

@@ -38,7 +38,7 @@ The ((ml)) model is not ill-affected, and you do not receive spurious results.
 
 To create a calendar and add scheduled events:
 
-1. From the main menu in Elastic ((observability)), select **AIOps -> Anomaly detection**.
+1. From the main menu in Elastic ((observability)), select **AIOps → Anomaly detection**.
 1. Click **Settings**.
 1. Under **Calendars**, click **Create**.
 1. Enter an ID and description for the calendar.
@@ -99,7 +99,7 @@ This gives you much greater control over which anomalous events affect the ((ml)
 
 To create a job rule, first create any filter lists you want to use in the rule, then configure the rule:
 
-1. From the main menu in Elastic ((observability)), select **AIOps -> Anomaly detection**.
+1. From the main menu in Elastic ((observability)), select **AIOps → Anomaly detection**.
 1. (Optional) Create one or more filter lists:
     1. Click **Settings**.
     1. Under **Filter lists**, click **Create**.
@@ -132,7 +132,7 @@ For example, you can define a custom URL that enables users to drill down to the
 
 To add a custom URL to the **Actions** menu:
 
-1. From the main menu in Elastic ((observability)), select **AIOps -> Anomaly detection**.
+1. From the main menu in Elastic ((observability)), select **AIOps → Anomaly detection**.
 1. From the **Actions** menu in the job list, select **Edit job**.
 1. Select the **Custom URLs** tab, then click **Add custom URL**.
 1. Enter the label to use for the link text.

docs/alerting/create-error-count-threshold-alert-rule.mdx

@@ -55,7 +55,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** -> **Error count rule**. 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** → **Error count rule**. 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:
 

docs/alerting/create-failed-transaction-rate-threshold-alert-rule.mdx

@@ -52,7 +52,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** -> **Failed transaction rate**. 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** → **Failed transaction rate**. 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:
 

docs/alerting/create-latency-threshold-alert-rule.mdx

@@ -54,7 +54,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:
 

docs/apm-agents/apm-agents-opentelemetry-collect-metrics.mdx

@@ -41,7 +41,7 @@ Use **Discover** to validate that metrics are successfully reported to your proj
 
 1. Open your Observability project.
 1. Under **Observability**, select **Log explorer**.
-1. Click **All logs** -> **Data Views** then select **APM**.
+1. Click **All logs** → **Data Views** then select **APM**.
 1. Filter the data to only show documents with metrics: `processor.name :"metric"`
 1. Narrow your search with a known OpenTelemetry field. For example, if you have an `order_value` field, add `order_value: *` to your search to return
     only OpenTelemetry metrics documents.

docs/apm-agents/apm-agents-opentelemetry.mdx

@@ -31,27 +31,27 @@ currently supported by the Java, Python, .NET, and Node.js agents.
 These Elastic APM agents translate OpenTelemetry API calls to Elastic APM API calls.
 This allows you to reuse your existing instrumentation to create Elastic APM transactions and spans—avoiding vendor lock-in and having to redo manual instrumentation.
 
-<DocLink id="serverlessObservabilityApmAgentsOtelApisdkWithElasticApmAgents">Get started -></DocLink>
+<DocLink id="serverlessObservabilityApmAgentsOtelApisdkWithElasticApmAgents">Get started →</DocLink>
 
 **OpenTelemetry agent**
 
 Elastic natively supports the OpenTelemetry protocol (OTLP).
 This means trace data and metrics collected from your applications and infrastructure by an
 OpenTelemetry agent can be sent directly to Elastic.
 
-<DocLink id="serverlessObservabilityApmAgentsOtelNativeSupport" section="send-data-from-an-opentelemetry-agent">Get started -></DocLink>
+<DocLink id="serverlessObservabilityApmAgentsOtelNativeSupport" section="send-data-from-an-opentelemetry-agent">Get started →</DocLink>
 
 **OpenTelemetry collector**
 
 Elastic natively supports the OpenTelemetry protocol (OTLP).
 This means trace data and metrics collected from your applications and infrastructure by an
 OpenTelemetry collector can be sent directly to Elastic.
 
-<DocLink id="serverlessObservabilityApmAgentsOtelNativeSupport" section="send-data-from-an-opentelemetry-collector">Get started -></DocLink>
+<DocLink id="serverlessObservabilityApmAgentsOtelNativeSupport" section="send-data-from-an-opentelemetry-collector">Get started →</DocLink>
 
 **Lambda collector exporter**
 
 AWS Lambda functions can be instrumented with OpenTelemetry and monitored with Elastic ((observability)).
 
-<DocLink id="serverlessObservabilityOtelLambdaSupport">Get started -></DocLink>
+<DocLink id="serverlessObservabilityOtelLambdaSupport">Get started →</DocLink>
 

docs/apm/apm-create-custom-links.mdx

@@ -22,7 +22,7 @@ The easiest way to create a custom link is from within the actions dropdown in t
 This method will automatically apply filters, scoping the link to that specific service,
 environment, transaction type, and transaction name.
 
-Alternatively, you can create a custom link by navigating to any page within **Applications** and selecting **Settings** -> **Custom Links** -> **Create custom link**.
+Alternatively, you can create a custom link by navigating to any page within **Applications** and selecting **Settings** → **Custom Links** → **Create custom link**.
 
 ### Label
 

docs/apm/apm-find-transaction-latency-and-failure-correlations.mdx

@@ -19,7 +19,7 @@ address or region, is facing increased latency due to local data center issues.
 
 To find correlations:
 
-1. Select a service in **Applications** -> **Services**
+1. Select a service in **Applications** → **Services**
 1. Select the **Transactions** tab
 1. Select a transaction group in the **Transactions** table
 

docs/apm/apm-get-started.mdx

@@ -34,7 +34,7 @@ your project:
 
 1. <DocLink id="serverlessObservabilityCreateAnObservabilityProject">Create a new ((observability)) project</DocLink>, or open an existing one.
 1. To install and configure one or more APM agents, do one of following:
-    * In your Observability project, go to **Get Started** -> **Collect application performance data** and follow the prompts.
+    * In your Observability project, go to **Get Started** → **Collect application performance data** and follow the prompts.
     * Use the following instructions:
 
         <DocTabs hasBorder>

docs/apm/apm-integrate-with-machine-learning.mdx

@@ -48,7 +48,7 @@ To enable machine learning anomaly detection:
 
 That's it! After a few minutes, the job will begin calculating results;
 it might take additional time for results to appear on your service maps.
-To manage existing jobs, click **Manage jobs** (or go to **AIOps** -> **Anomaly detection**).
+To manage existing jobs, click **Manage jobs** (or go to **AIOps** → **Anomaly detection**).
 
 ## Anomaly detection warning
 

docs/apm/apm-kibana-settings.mdx

@@ -81,7 +81,7 @@ preview:[] Enable the APM Trace Explorer feature, that allows you to search and
 
 **APM Labs** allows you to easily try out new features that are technical preview.
 
-To enable APM labs, navigate to **Applications** -> **Settings** -> **General settings** and toggle **Enable labs button in APM**.
+To enable APM labs, navigate to **Applications** → **Settings** → **General settings** and toggle **Enable labs button in APM**.
 Select **Save changes** and refresh the page.
 
 After enabling **APM Labs** select **Labs** in the toolbar to see the technical preview features available to try out.

docs/apm/apm-ui-services.mdx

@@ -14,7 +14,7 @@ The **Services** inventory provides a quick, high-level overview of the health a
 performance of all instrumented services.
 
 To help surface potential issues, services are sorted by their health status:
-**critical** -> **warning** -> **healthy** -> **unknown**.
+**critical** → **warning** → **healthy** → **unknown**.
 Health status is powered by <DocLink id="serverlessObservabilityApmIntegrateWithMachineLearning">machine learning</DocLink>
 and requires anomaly detection to be enabled.
 
@@ -35,7 +35,7 @@ and combine related alerts.
 
 To create a service group:
 
-1. Navigate to **Applications** -> **Services**.
+1. Navigate to **Applications** → **Services**.
 1. Switch to **Service groups**.
 1. Click **Create group**.
 1. Specify a name, color, and description.

docs/cases/create-manage-cases.mdx

@@ -44,7 +44,7 @@ When you upload a file, a comment is added to the case activity log.
 To view an image, click its name in the activity or file list.
 
 <DocCallOut title="Note">
-Uploaded files are also accessible under **Project settings -> Management -> Files**.
+Uploaded files are also accessible under **Project settings → Management → Files**.
 When you export cases as [saved objects](((kibana-ref))/managing-saved-objects.html), the case files are not exported.
 </DocCallOut>
 

docs/cases/send-cases-to-an-external-system.mdx

@@ -34,7 +34,7 @@ automatically close when they are sent to an external system.
 
 ## Create a connector
 
-1. Go to **Cases** -> **Settings**.
+1. Go to **Cases** → **Settings**.
 1. From the **Incident management system** list, select **Add new connector**.
 1. Select the system to send cases to: **((sn))**, **((jira))**, **((ibm-r))**, **((swimlane))**,
     or **((webhook-cm))**.
@@ -63,7 +63,7 @@ You can also configure which connector is used for each case individually. Refer
 
 To change the default connector used to send cases to external systems:
 
-1. Go to **Cases** -> **Settings**.
+1. Go to **Cases** → **Settings**.
 1. Select the required connector from the **Incident management system** list.
 
 To update an existing connector:
@@ -80,4 +80,4 @@ If you close cases in your external incident management system, the cases will r
 manually (the information is only sent in one direction).
 
 To close cases when they are sent to an external system, select
-**Automatically close cases when pushing new incident to external system** from **Cases** -> **Settings**.
+**Automatically close cases when pushing new incident to external system** from **Cases** → **Settings**.

docs/infra-monitoring/analyze-hosts.mdx

@@ -25,7 +25,7 @@ health and performance metrics to help you quickly:
 * Filter and search the data to focus on the hosts you care about the most.
 
 To access the **Hosts** page from the main ((observability)) menu, go to
-**Infrastructure -> Hosts**.
+**Infrastructure → Hosts**.
 
 ![Screenshot of the Hosts page](../images/hosts.png)
 
@@ -204,7 +204,7 @@ To fix this problem, change the selected time range at the top of the page.
 
 <DocCallOut title="Tip">
 Want to dig in further while maintaining the selected time duration?
-Hover over the chart you're interested in and select **Options** -> **Open in Lens**.
+Hover over the chart you're interested in and select **Options** → **Open in Lens**.
 Once in Lens, you can adjust the chart interval temporarily.
 Note that this change is not persisted in the **Hosts** view.
 </DocCallOut>

docs/infra-monitoring/configure-infra-settings.mdx

@@ -8,7 +8,7 @@ tags: [ 'serverless', 'observability', 'how to' ]
 
 <div id="configure-settings"></div>
 
-From the main ((observability)) menu, go to **Infrastructure** -> **Inventory** or **Hosts**,
+From the main ((observability)) menu, go to **Infrastructure** → **Inventory** or **Hosts**,
 and click the **Settings** link at the top of the page.
 The following settings are available:
 

docs/infra-monitoring/detect-metric-anomalies.mdx

@@ -25,7 +25,7 @@ However, you will remove any previously detected anomalies.
 
 {/* lint ignore anomaly-detection observability */}
 1. From the main menu in Elastic ((observability)),
-    select **Infrastructure -> Inventory** and click the **Anomaly detection** link at the top of the page.
+    select **Infrastructure → Inventory** and click the **Anomaly detection** link at the top of the page.
 1. Under **Hosts** or **Kubernetes Pods**, click **Enable** to create a ((ml)) job.
 1. Choose a start date for the ((ml)) analysis. ((ml-cap)) jobs analyze the last four weeks of data and continue to run indefinitely.
 1. Select a partition field.
@@ -48,14 +48,14 @@ These scores represent a severity of "warning" or higher in the selected time pe
 The **summary** value represents the increase between the actual value and the expected ("typical") value of the metric in the anomaly record result.
 
 To drill down and analyze the metric anomaly,
-select **Actions -> Open in Anomaly Explorer** to view the Anomaly Explorer.
-You can also select **Actions -> Show in Inventory** to view the host or Kubernetes pods Inventory page,
+select **Actions → Open in Anomaly Explorer** to view the Anomaly Explorer.
+You can also select **Actions → Show in Inventory** to view the host or Kubernetes pods Inventory page,
 filtered by the specific metric.
 
 <DocCallOut title="Note">
 
 These predefined ((anomaly-jobs)) use [custom rules](((ml-docs))/ml-rules.html).
-To update the rules in the Anomaly Explorer, select **Actions -> Configure rules**.
+To update the rules in the Anomaly Explorer, select **Actions → Configure rules**.
 The changes only take effect for new results.
 If you want to apply the changes to existing results, clone and rerun the job.
 

docs/infra-monitoring/get-started-with-metrics.mdx

@@ -12,7 +12,7 @@ then observe the data in Elastic ((observability)).
 To onboard system metrics data:
 
 1. <DocLink id="serverlessObservabilityCreateAnObservabilityProject">Create a new ((observability)) project</DocLink>, or open an existing one.
-1. From the main menu in Elastic ((observability)), go to **Infrastructure** -> **Inventory** or **Hosts**.
+1. From the main menu in Elastic ((observability)), go to **Infrastructure** → **Inventory** or **Hosts**.
 1. In the upper-right corner, click **Add data**.
 1. Type **System** in the search bar, then select the integration to see more details about it.
 1. Click **Add System**.
@@ -40,7 +40,7 @@ Notice that you can also configure the integration to collect logs.
 </DocCallOut>
 
 After the agent is installed and successfully streaming metrics data,
-go to **Infrastructure** -> **Inventory** or **Hosts** to see a metrics-driven view of your infrastructure.
+go to **Infrastructure** → **Inventory** or **Hosts** to see a metrics-driven view of your infrastructure.
 To learn more, refer to <DocLink id="serverlessObservabilityViewInfrastructureMetrics" /> or <DocLink id="serverlessObservabilityAnalyzeHosts" />.
 
 ## Next steps

docs/infra-monitoring/view-infrastructure-metrics.mdx

@@ -16,7 +16,7 @@ a core set of infrastructure metrics are displayed to give you a quick view of t
 of your infrastructure.
 
 To access the **Inventory** page from the main ((observability)) menu, go to
-**Infrastructure -> Inventory**.
+**Infrastructure → Inventory**.
 
 ![Infrastructure UI in ((kib))](../images/metrics-app.png)
 

docs/logging/get-started-with-logs.mdx

@@ -26,7 +26,7 @@ After the agent is installed and successfully streaming log data, you can view t
 1. Select **Log Explorer** from the main menu. The view shows all log datasets.
 Notice you can add fields, change the view, expand a document to see details,
 and perform other actions to explore your data.
-1. Click **All log datasets** and select **System -> syslog** to show syslog logs.
+1. Click **All log datasets** and select **System → syslog** to show syslog logs.
 
 ![Screen capture of the Log Explorer showing syslog dataset selected](../images/log-explorer-select-syslogs.png)
 

docs/logging/stream-log-files.mdx

@@ -186,7 +186,7 @@ You need to set the values for the following fields:
 
       If configuring the ((agent)) manually, create an API key:
 
-      1. Navigate to **Project settings -> Management -> API keys** and click **Create API key**.
+      1. Navigate to **Project settings → Management → API keys** and click **Create API key**.
       1. Select **Restrict privileges** and add the following JSON to give privileges for ingesting logs.
           ```json
           {