From 73e96dc88b270f3d03d508a0acd13aed56ac8caf Mon Sep 17 00:00:00 2001
From: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com>
Date: Tue, 9 Jul 2024 07:48:16 -0700
Subject: [PATCH] Fix some bad xref links (#1235)

---
 docs/sources/collect/opentelemetry-to-lgtm-stack.md          | 4 ++--
 .../clustering/distribute-prometheus-scrape-load.md          | 5 ++---
 docs/sources/configure/nonroot.md                            | 2 +-
 3 files changed, 5 insertions(+), 6 deletions(-)

diff --git a/docs/sources/collect/opentelemetry-to-lgtm-stack.md b/docs/sources/collect/opentelemetry-to-lgtm-stack.md
index e17e0786a6..aba349bd6e 100644
--- a/docs/sources/collect/opentelemetry-to-lgtm-stack.md
+++ b/docs/sources/collect/opentelemetry-to-lgtm-stack.md
@@ -1,7 +1,7 @@
 ---
 canonical: https://grafana.com/docs/alloy/latest/collect/opentelemetry-to-lgtm-stack/
 aliases:
-  - ../tasks/opentelemetry-to-lgtm-stack/ # /docs/alloy/latest/tasks/opentelemetry-to-lgtm-stack/
+  - ../tasks/collect-opentelemetry-to-lgtm-stack/ # /docs/alloy/latest/tasks/collect-opentelemetry-to-lgtm-stack/
 description: Learn how to collect OpenTelemetry data and forward it to the Grafana stack
 menuTitle: Collect OpenTelemetry data and forward to Grafana
 title: Collect OpenTelemetry data and forward to Grafana
@@ -339,7 +339,7 @@ You can check the pipeline graphically by visiting [http://localhost:12345/graph
 [Grafana Cloud Portal]: https://grafana.com/docs/grafana-cloud/account-management/cloud-portal#your-grafana-cloud-stack
 [Prometheus Remote Write]: https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage
 [Grafana Mimir]: https://grafana.com/oss/mimir/
-[Collect open telemetry data]: ../collect-opentelemetry-data/
+[Collect open telemetry data]: ../opentelemetry-data/
 [Components]: ../../get-started/components/
 [loki.write]: ../../reference/components/loki.write/
 [otelcol.auth.basic]: ../../reference/components/otelcol.auth.basic/
diff --git a/docs/sources/configure/clustering/distribute-prometheus-scrape-load.md b/docs/sources/configure/clustering/distribute-prometheus-scrape-load.md
index 462c7a53ad..e3306d3abc 100644
--- a/docs/sources/configure/clustering/distribute-prometheus-scrape-load.md
+++ b/docs/sources/configure/clustering/distribute-prometheus-scrape-load.md
@@ -17,7 +17,7 @@ A good predictor for the size of an {{< param "PRODUCT_NAME" >}} deployment is t
 
 - Familiarize yourself with how to [configure][] existing {{< param "PRODUCT_NAME" >}} installations.
 - [Configure Prometheus metrics collection][].
-- [Configure clustering][].
+- [Configure clustering][clustering].
 - Ensure that all of your clustered {{< param "PRODUCT_NAME" >}}s have the same configuration file.
 
 ## Steps
@@ -42,6 +42,5 @@ To distribute Prometheus metrics scrape load with clustering:
 
 [Clustering]: ../../clustering/
 [configure]: ../../../configure/
-[Configure Prometheus metrics collection]: ../../../collect/collect-prometheus-metrics/
-[Configure clustering]: ../../../configure/clustering/
+[Configure Prometheus metrics collection]: ../../../collect/prometheus-metrics/
 [UI]: ../../../troubleshoot/debug/#component-detail-page
diff --git a/docs/sources/configure/nonroot.md b/docs/sources/configure/nonroot.md
index 51fddc4cd2..56950bcf9a 100644
--- a/docs/sources/configure/nonroot.md
+++ b/docs/sources/configure/nonroot.md
@@ -47,4 +47,4 @@ However, if there was a bug in the Linux kernel that allowed Docker containers t
 [image]: https://hub.docker.com/r/grafana/alloy
 [beyla.ebpf]: ../../reference/components/beyla.ebpf
 [security context]: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
-[Grafana Helm chart]: ../configure-kubernetes/#configure-the-helm-chart
\ No newline at end of file
+[Grafana Helm chart]: ../../configure/kubernetes/#configure-the-helm-chart
\ No newline at end of file