diff --git a/docs/sources/getting-started/troubleshooting.md b/docs/sources/getting-started/troubleshooting.md
index c5f0dff142d0..a2904b0cbb3b 100644
--- a/docs/sources/getting-started/troubleshooting.md
+++ b/docs/sources/getting-started/troubleshooting.md
@@ -46,11 +46,11 @@ Promtail yet. There may be one of many root causes:
 Promtail exposes two web pages that can be used to understand how its service
 discovery works.
 
-The service discovery page (../service-discovery`) shows all
+The service discovery page (`/service-discovery`) shows all
 discovered targets with their labels before and after relabeling as well as
 the reason why the target has been dropped.
 
-The targets page (../targets`) displays only targets that are being actively
+The targets page (`/targets`) displays only targets that are being actively
 scraped and their respective labels, files, and positions.
 
 On Kubernetes, you can access those two pages by port-forwarding the Promtail
@@ -109,7 +109,7 @@ kubectl exec -it promtail-bth9q -- /bin/sh
 Once connected, verify the config in `/etc/promtail/promtail.yml` has the
 contents you expect.
 
-Also check `/var/log/positions.yaml` (../run/promtail/positions.yaml` when
+Also check `/var/log/positions.yaml` (`/run/promtail/positions.yaml` when
 deployed by Helm or whatever value is specified for `positions.file`) and make
 sure Promtail is tailing the logs you would expect.