fixed links

grafana · Aug 7, 2024 · 04dddfd · 04dddfd
1 parent 4998809
commit 04dddfd
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/alloy/send-logs-to-loki/finish.md b/alloy/send-logs-to-loki/finish.md
@@ -2,4 +2,4 @@
 
 You have installed and configured Alloy, and sent logs from your local host to your local Grafana stack.
 
-In the [next tutorial](https://grafana.com/../send-metrics-to-prometheus/), you learn more about configuration concepts and metrics.
+In the [next tutorial](https://grafana.com/docs/alloy/latest/tutorials/send-metrics-to-prometheus/), you learn more about configuration concepts and metrics.
diff --git a/alloy/send-logs-to-loki/step4.md b/alloy/send-logs-to-loki/step4.md
@@ -12,7 +12,7 @@
     curl -X POST http://localhost:12345/-/reload
    ```{{exec}}
 
-   > This step uses the Alloy UI on `localhost` port `12345`. If you chose to run Alloy in a Docker container, make sure you use the `--server.http.listen-addr=` argument. If you don’t use this argument, the [debugging UI][debug] won’t be available outside of the Docker container.
+   > This step uses the Alloy UI on `localhost` port `12345`. If you chose to run Alloy in a Docker container, make sure you use the `--server.http.listen-addr=` argument. If you don’t use this argument, the [debugging UI][https://grafana.com/docs/alloy/latest/troubleshoot/debug/#alloy-ui] won’t be available outside of the Docker container.
 
 1. Optional: You can do a system service restart Alloy and load the configuration file: