docs: fix unresolved file references (#13488)

collectors/ebpf.plugin/README.md

@@ -8,7 +8,7 @@ sidebar_label: "eBPF"
 
 # eBPF monitoring with Netdata
 
-The Netdata Agent provides many [eBPF](https://ebpf.io/what-is-ebpf/) programs to help you troubleshoot and debug how applications interact with the Linux kernel. The `ebpf.plugin` uses [tracepoints, trampoline, and2 kprobes](#data-collection) to collect a wide array of high value data about the host that would otherwise be impossible to capture. 
+The Netdata Agent provides many [eBPF](https://ebpf.io/what-is-ebpf/) programs to help you troubleshoot and debug how applications interact with the Linux kernel. The `ebpf.plugin` uses [tracepoints, trampoline, and2 kprobes](#how-netdata-collects-data-using-probes-and-tracepoints) to collect a wide array of high value data about the host that would otherwise be impossible to capture. 
 
 > ❗ eBPF monitoring only works on Linux systems and with specific Linux kernels, including all kernels newer than `4.11.0`, and all kernels on CentOS 7.6 or later. For kernels older than `4.11.0`, improved support is in active development.
 
@@ -20,8 +20,6 @@ For hands-on configuration and troubleshooting tips see our [tutorial on trouble
   <figcaption>An example of virtual file system (VFS) charts made possible by the eBPF collector plugin.</figcaption>
 </figure>
 
-<a id="data-collection"> </a>
-
 ## How Netdata collects data using probes and tracepoints
 
 Netdata uses the following features from the Linux kernel to run eBPF programs:

database/README.md

@@ -38,13 +38,13 @@ The default mode `[db].mode = dbengine` has been designed to scale for longer re
 for parent Agents in the _Parent - Child_ setups
 
 The other available database modes are designed to minimize resource utilization and should only be considered on
-[Parent - Child](/docs/metrics-storage-management/how-streaming-works) setups at the children side and only when the
+[Parent - Child](/docs/metrics-storage-management/how-streaming-works.mdx) setups at the children side and only when the
 resource constraints are very strict.
 
 So,
 
 - On a single node setup, use `[db].mode = dbengine`.
-- On a [Parent - Child](/docs/metrics-storage-management/how-streaming-works) setup, use `[db].mode = dbengine` on the
+- On a [Parent - Child](/docs/metrics-storage-management/how-streaming-works.mdx) setup, use `[db].mode = dbengine` on the
   parent to increase retention, a more resource efficient mode like, `dbengine` with light retention settings, and
   `save`, `ram` or `none` modes for the children to minimize resource utilization.
 
@@ -64,7 +64,7 @@ Metrics retention is controlled only by the disk space allocated to storing metr
 CPU required by the agent to query longer timeframes.
 
 Since Netdata Agents usually run on the edge, on production systems, Netdata Agent **parents** should be considered.
-When having a [**parent - child**](/docs/metrics-storage-management/how-streaming-works.md) setup, the child (the
+When having a [**parent - child**](/docs/metrics-storage-management/how-streaming-works.mdx) setup, the child (the
 Netdata Agent running on a production system) delegates all of its functions, including longer metrics retention and
 querying, to the parent node that can dedicate more resources to this task. A single Netdata Agent parent can centralize
 multiple children Netdata Agents (dozens, hundreds, or even thousands depending on its available resources).

docs/guides/troubleshoot/troubleshooting-agent-with-cloud-connection.md

@@ -51,7 +51,7 @@ and you must do it manually, using the following steps:
 :::note
 
 In some cases a simple restart of the Agent can fix the issue.  
-Read more about [Starting, Stopping and Restarting the Agent](/docs/configure/start-stop-restart).
+Read more about [Starting, Stopping and Restarting the Agent](/docs/configure/start-stop-restart.md).
 
 :::