diff --git a/docs/en/observability/synthetics-troubleshooting.asciidoc b/docs/en/observability/synthetics-troubleshooting.asciidoc
index 1a7bef5d7d..50b65883b4 100644
--- a/docs/en/observability/synthetics-troubleshooting.asciidoc
+++ b/docs/en/observability/synthetics-troubleshooting.asciidoc
@@ -88,7 +88,7 @@ Start by identifying the cause of the issue. First, check if the time it takes t
 
 1. Go to the Synthetics app.
 2. Click the monitor, then click **Go to monitor**.
-3. Go to the [Overview tab](https://www.elastic.co/guide/en/observability/current/synthetics-analyze.html#synthetics-analyze-individual-monitors-overview) to see the _Avg. duration_. You can also view the duration for individual runs in the [History tab](https://www.elastic.co/guide/en/observability/current/synthetics-analyze.html#synthetics-analyze-individual-monitors-history).
+3. Go to the https://www.elastic.co/guide/en/observability/current/synthetics-analyze.html#synthetics-analyze-individual-monitors-overview[Overview tab] to see the _Avg. duration_. You can also view the duration for individual runs in the https://www.elastic.co/guide/en/observability/current/synthetics-analyze.html#synthetics-analyze-individual-monitors-history[History tab].
 4. Compare the duration to the scheduled frequency. If the duration is _greater than_ the scheduled frequency, for example if the monitor that takes 90 seconds to run and its scheduled frequency is 1 minute, the next scheduled run will not occur because the current one is still running so you may see results for every other scheduled run.
 
 To fix this, you can either:
@@ -100,7 +100,7 @@ If the duration is _less than_ the scheduled frequency or the suggestion above d
 
 To fix this issue, you can either:
 
-* Increase the number of concurrent browser monitors allowed (as described in [Scaling Private Locations](https://observability-docs_3105.docs-preview.app.elstc.co/guide/en/observability/master/synthetics-private-location.html#synthetics-private-location-scaling), paying attention to the scaling and hardware requirements documented).
+* Increase the number of concurrent browser monitors allowed (as described in https://observability-docs_3105.docs-preview.app.elstc.co/guide/en/observability/master/synthetics-private-location.html#synthetics-private-location-scaling[Scaling Private Locations]), paying attention to the scaling and hardware requirements documented).
 * Create multiple Private Locations and spread your browser monitors across them more evenly (effectively horizontally scaling your Private Locations).
 
 [discrete]