Fixing sneaky broken links (#11175)

3 files changed, 7 insertions, 6 deletions

diff --git a/docs/guides/deploy/ansible.md b/docs/guides/deploy/ansible.md
index 8298fd00c8..b1afdf3158 100644
--- a/docs/guides/deploy/ansible.md
+++ b/docs/guides/deploy/ansible.md
@@ -7,9 +7,9 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/depl
 
 # Deploy Netdata with Ansible
 
-Netdata's [one-line kickstart](https://learn.netdata.cloud/docs/get) is zero-configuration, highly adaptable, and
-compatible with tons of different operating systems and Linux distributions. You can use it on bare metal, VMs,
-containers, and everything in-between.
+Netdata's [one-line kickstart](/docs/get-started.mdx) is zero-configuration, highly adaptable, and compatible with tons
+of different operating systems and Linux distributions. You can use it on bare metal, VMs, containers, and everything
+in-between.
 
 But what if you're trying to bootstrap an infrastructure monitoring solution as quickly as possible. What if you need to
 deploy Netdata across an entire infrastructure with many nodes? What if you want to make this deployment reliable,
diff --git a/docs/guides/monitor/statsd.md b/docs/guides/monitor/statsd.md
index 120715b19a..a4d06043e0 100644
--- a/docs/guides/monitor/statsd.md
+++ b/docs/guides/monitor/statsd.md
@@ -22,14 +22,15 @@ In general, the process for creating a StatsD collector can be summarized in 2 s
 
 - Run an experiment by sending StatsD metrics to Netdata, without any prior configuration. This will create a chart per metric (called private charts) and will help you verify that everything works as expected from the application side of things.
     - Make sure to reload the dashboard tab **after** you start sending data to Netdata.
-- Create a configuration file for your app using [edit-config](https://learn.netdata.cloud/guides/step-by-step/step-04): `sudo ./edit-config statsd.d/myapp.conf`
+- Create a configuration file for your app using [edit-config](/docs/configure/nodes.md): `sudo ./edit-config
+  statsd.d/myapp.conf`
     - Each app will have it's own section in the right-hand menu.
 
 Now, let's see the above process in detail.
 
 ## Prerequisites
 
-- A node with the [Netdata Agent](https://learn.netdata.cloud/docs/get#install-the-netdata-agent) installed.
+- A node with the [Netdata](/docs/get-started.mdx) installed.
 - An application to instrument. For this guide, that will be [k6](https://k6.io/docs/getting-started/installation).
 
 ## Understanding the metrics
diff --git a/docs/guides/using-host-labels.md b/docs/guides/using-host-labels.md
index 6d4af2e5da..79558dd169 100644
--- a/docs/guides/using-host-labels.md
+++ b/docs/guides/using-host-labels.md
@@ -27,7 +27,7 @@ sudo ./edit-config netdata.conf
 ```
 
 Create a new `[host labels]` section defining a new host label and its value for the system in question. Make sure not
-to violate any of the [host label naming rules](/docs/configuration-guide.md#netdata-labels).
+to violate any of the [host label naming rules](/docs/configure/common-changes.md#organize-nodes-with-host-labels).
 
 ```conf
 [host labels]