fix(docs): unresolved file references (#11903)

35 files changed, 69 insertions, 69 deletions

diff --git a/backends/WALKTHROUGH.md b/backends/WALKTHROUGH.md
index 12eea2ee1a..bb38e7c1c6 100644
--- a/backends/WALKTHROUGH.md
+++ b/backends/WALKTHROUGH.md
@@ -62,7 +62,7 @@ command to run (/bin/bash) and then chooses the base container images (centos:la
 sitting inside the shell of the container.
 
 After we have entered the shell we can install Netdata. This process could not be easier. If you take a look at [this
-link](../packaging/installer/README.md), the Netdata devs give us several one-liners to install Netdata. I have not had
+link](/packaging/installer/README.md), the Netdata devs give us several one-liners to install Netdata. I have not had
 any issues with these one liners and their bootstrapping scripts so far (If you guys run into anything do share). Run
 the following command in your container.
 
@@ -214,7 +214,7 @@ the `chart` dimension. If you’d like you can combine the ‘chart’ and ‘in
 Let’s give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}`
 
 This is the basics of using Prometheus to query Netdata. I’d advise everyone at this point to read [this
-page](../backends/prometheus/#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from
+page](/backends/prometheus/README.md#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from
 its internal DB or can send metrics “as-collected” by specifying the ‘source=as-collected’ url parameter like so.
 <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use
 this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to
diff --git a/claim/README.md b/claim/README.md
index b709b0f06f..41557d6b5e 100644
--- a/claim/README.md
+++ b/claim/README.md
@@ -70,7 +70,7 @@ When coming from  [Nodes view page](https://learn.netdata.cloud/docs/cloud/visua
 
 ### Connect an agent running in Linux
 
-If you want to connect a node that is running on a Linux environment, the script that will be provided to you by Netdata Cloud is the [kickstart](/packaging/installer/#automatic-one-line-installation-script) which will install the Netdata Agent on your node, if it isn't already installed, and connect the node to Netdata Cloud. It should be similar to:
+If you want to connect a node that is running on a Linux environment, the script that will be provided to you by Netdata Cloud is the [kickstart](/packaging/installer/README.md#automatic-one-line-installation-script) which will install the Netdata Agent on your node, if it isn't already installed, and connect the node to Netdata Cloud. It should be similar to:
 
 ```
 bash <(curl -Ss https://my-netdata.io/kickstart.sh) --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://app.netdata.cloud
@@ -80,7 +80,7 @@ the node in your Space after 60 seconds, see the [troubleshooting information](#
 
 Please note that to run it you will either need to have root privileges or run it with the user that is running the agent, more details on the [Connect an agent without root privileges](#connect-an-agent-without-root-privileges) section.
 
-For more details on what are the extra parameters `claim-token`, `claim-rooms` and `claim-url` please refer to [Connect node to Netdata Cloud during installation](/packaging/installer/methods/kickstart#connect-node-to-netdata-cloud-during-installation).
+For more details on what are the extra parameters `claim-token`, `claim-rooms` and `claim-url` please refer to [Connect node to Netdata Cloud during installation](/packaging/installer/methods/kickstart.md#connect-node-to-netdata-cloud-during-installation).
 
 ### Connect an agent without root privileges
 
@@ -224,7 +224,7 @@ you don't see the node in your Space after 60 seconds, see the [troubleshooting
 
 ### Connect an agent running in macOS
 
-To connect a node that is running on a macOS environment the script that will be provided to you by Netdata Cloud is the [kickstart](/packaging/installer/methods/macos#install-netdata-with-kickstart) which will install the Netdata Agent on your node, if it isn't already installed, and connect the node to Netdata Cloud. It should be similar to:
+To connect a node that is running on a macOS environment the script that will be provided to you by Netdata Cloud is the [kickstart](/packaging/installer/methods/macos.md#install-netdata-with-our-automatic-one-line-installation-script) which will install the Netdata Agent on your node, if it isn't already installed, and connect the node to Netdata Cloud. It should be similar to:
 
 ```bash
 bash <(curl -Ss https://my-netdata.io/kickstart.sh) --install /usr/local/ --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://app.netdata.cloud
@@ -234,7 +234,7 @@ the node in your Space after 60 seconds, see the [troubleshooting information](#
 
 ### Connect a Kubernetes cluster's parent Netdata pod
 
-Read our [Kubernetes installation](/packaging/installer/methods/kubernetes.md#connect-a-kubernetes-clusters-parent-pod)
+Read our [Kubernetes installation](/packaging/installer/methods/kubernetes.md#connect-your-kubernetes-cluster-to-netdata-cloud)
 for details on connecting a parent Netdata pod.
 
 ### Connect through a proxy
@@ -263,7 +263,7 @@ For example, a HTTP proxy setting may look like the following:
     proxy = http://proxy.example.com:1080 # With a URL
 ```
 
-You can now move on to connecting. When you connect with the [kickstart](/packaging/installer/#automatic-one-line-installation-script) script, add the `--claim-proxy=` parameter and
+You can now move on to connecting. When you connect with the [kickstart](/packaging/installer/README.md#automatic-one-line-installation-script) script, add the `--claim-proxy=` parameter and
 append the same proxy setting you added to `netdata.conf`.
 
 ```bash
@@ -458,7 +458,7 @@ using the [ACLK](/aclk/README.md).
 
 ### kickstart script
 
-The best way to install Netdata and connect your nodes to Netdata Cloud is with our automatic one-line installation script, [kickstart](/packaging/installer/#automatic-one-line-installation-script). This script will install the Netdata Agent, in case it isn't already installed, and connect your node to Netdata Cloud. 
+The best way to install Netdata and connect your nodes to Netdata Cloud is with our automatic one-line installation script, [kickstart](/packaging/installer/README.md#automatic-one-line-installation-script). This script will install the Netdata Agent, in case it isn't already installed, and connect your node to Netdata Cloud. 
 
 This  works with:
 * all Linux distributions, see [Netdata distribution support matrix](https://learn.netdata.cloud/docs/agent/packaging/distributions)
@@ -516,7 +516,7 @@ netdatacli reload-claiming-state
 
 This reloads the Agent connection state from disk.
 
-Our recommendation is to trigger the connection process using the [kickstart](/packaging/installer/#automatic-one-line-installation-script) whenever possible.
+Our recommendation is to trigger the connection process using the [kickstart](/packaging/installer/README.md#automatic-one-line-installation-script) whenever possible.
 
 ### Netdata Agent command line
 
diff --git a/collectors/COLLECTORS.md b/collectors/COLLECTORS.md
index 5f37dfc349..dd745366d9 100644
--- a/collectors/COLLECTORS.md
+++ b/collectors/COLLECTORS.md
@@ -129,7 +129,7 @@ configure any of these collectors according to your setup and infrastructure.
     metrics.
 -   [Redis (Go)](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/redis/): Monitor status from any
     number of database instances by reading the server's response to the `INFO ALL` command.
--   [Redis (Python)](/collectors/python.d.plugin/redis/): Monitor database status by reading the server's response to
+-   [Redis (Python)](/collectors/python.d.plugin/redis/README.md): Monitor database status by reading the server's response to
     the `INFO` command.
 -   [RethinkDB](/collectors/python.d.plugin/rethinkdbs/README.md): Collect database server and cluster statistics.
 -   [Riak KV](/collectors/python.d.plugin/riakkv/README.md): Collect database stats from the `/stats` endpoint.
@@ -169,14 +169,14 @@ configure any of these collectors according to your setup and infrastructure.
     plugins metrics from an endpoint provided by `in_monitor plugin`.
 -   [Logstash](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/logstash/): Monitor JVM threads,
     memory usage, garbage collection statistics, and more.
--   [OpenVPN status logs](/collectors/python.d.plugin/ovpn_status_log/): Parse server log files and provide summary
+-   [OpenVPN status logs](/collectors/python.d.plugin/ovpn_status_log/README.md): Parse server log files and provide summary
     (client, traffic) metrics.
 -   [Squid web server logs](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/squidlog/): Tail Squid
     access logs to return the volume of requests, types of requests, bandwidth, and much more.
 -   [Web server logs (Go version for Apache,
     NGINX)](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/weblog/): Tail access logs and provide
     very detailed web server performance statistics. This module is able to parse 200k+ rows in less than half a second.
--   [Web server logs (Python version for Apache, NGINX, Squid)](/collectors/python.d.plugin/web_log/): Tail access log
+-   [Web server logs (Python version for Apache, NGINX, Squid)](/collectors/python.d.plugin/web_log/README.md): Tail access log
     file and collect web server/caching proxy metrics.
 
 ### Messaging
@@ -217,7 +217,7 @@ configure any of these collectors according to your setup and infrastructure.
     server authentication and accounting statistics from the `status server`.
 -   [Freeradius (Python)](/collectors/python.d.plugin/freeradius/README.md): Collect server authentication and
     accounting statistics from the `status server` using the `radclient` tool.
--   [Libreswan](/collectors/charts.d.plugin/libreswan/): Collect bytes-in, bytes-out, and uptime metrics.
+-   [Libreswan](/collectors/charts.d.plugin/libreswan/README.md): Collect bytes-in, bytes-out, and uptime metrics.
 -   [Icecast](/collectors/python.d.plugin/icecast/README.md): Monitor the number of listeners for active sources.
 -   [ISC BIND](/collectors/node.d.plugin/named/README.md): Collect nameserver summary performance statistics via a web
     interface (`statistics-channels` feature).
@@ -267,7 +267,7 @@ configure any of these collectors according to your setup and infrastructure.
     blockchain indexes, memory usage, network usage, and transactions of wallet instances.
 -   [Energi Core (Python)](/collectors/python.d.plugin/energid/README.md): Monitor blockchain, memory, network, and
     unspent transactions statistics.
--   [Fronius Symo](/collectors/node.d.plugin/fronius/): Collect power, consumption, autonomy, energy, and inverter
+-   [Fronius Symo](/collectors/node.d.plugin/fronius/README.md): Collect power, consumption, autonomy, energy, and inverter
     statistics.
 -   [UPS/PDU](/collectors/charts.d.plugin/nut/README.md): Read the status of UPS/PDU devices using the `upsc` tool.
 -   [SMA Sunny WebBox](/collectors/node.d.plugin/sma_webbox/README.md): Collect power statistics.
diff --git a/collectors/QUICKSTART.md b/collectors/QUICKSTART.md
index 809ec18af8..d50a06c0c7 100644
--- a/collectors/QUICKSTART.md
+++ b/collectors/QUICKSTART.md
@@ -23,7 +23,7 @@ Netdata has _pre-installed_ collectors for hundreds of popular applications and
 anything to collect metrics from many popular services, like Nginx web servers, MySQL/MariaDB databases, and much more.
 
 To find whether Netdata has a pre-installed collector for your favorite app/service, check out our [collector support
-list](COLLECTORS.md). The only exception is the [third-party collectors](COLLECTORS.md#third-party-plugins), which
+list](COLLECTORS.md). The only exception is the [third-party collectors](COLLECTORS.md#third-party-collectors), which
 you do need to install yourself. However, this quickstart guide will focus on pre-installed collectors.
 
 When you find a collector you're interested in, take note of its orchestrator. These are in the headings above each
diff --git a/collectors/REFERENCE.md b/collectors/REFERENCE.md
index 4922ff9a9d..313526fbf0 100644
--- a/collectors/REFERENCE.md
+++ b/collectors/REFERENCE.md
@@ -116,7 +116,7 @@ This section features a list of Netdata's plugins, with a boolean setting to ena
 By default, most plugins are enabled, so you don't need to enable them explicitly to use their collectors. To enable or
 disable any specific plugin, remove the comment (`#`) and change the boolean setting to `yes` or `no`.
 
-All **external plugins** are managed by [plugins.d](plugins.d/), which provides additional management options.
+All **external plugins** are managed by [plugins.d](plugins.d/README.md), which provides additional management options.
 
 ## Internal plugins
 
@@ -178,10 +178,10 @@ through this, is to examine what other similar plugins do.
 
 ## External Plugins
 
-**External plugins** use the API and are managed by [plugins.d](plugins.d/).
+**External plugins** use the API and are managed by [plugins.d](plugins.d/README.md).
 
 ## Write a custom collector
 
-You can add custom collectors by following the [external plugins documentation](../collectors/plugins.d/).
+You can add custom collectors by following the [external plugins documentation](/collectors/plugins.d/README.md).
 
 [![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fcollectors%2REFERENCE&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()
diff --git a/collectors/python.d.plugin/example/README.md b/collectors/python.d.plugin/example/README.md
index 561ea62ede..46d3b780ff 100644
--- a/collectors/python.d.plugin/example/README.md
+++ b/collectors/python.d.plugin/example/README.md
@@ -6,6 +6,6 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/pytho
 # Example
 
 An example python data collection module.
-You can use this example to help you [write a new Python module](../#how-to-write-a-new-module).
+You can use this example to help you [write a new Python module](/collectors/python.d.plugin/README.md#how-to-write-a-new-module).
 
 [![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fcollectors%2Fpython.d.plugin%2Fexample%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)
diff --git a/collectors/python.d.plugin/web_log/README.md b/collectors/python.d.plugin/web_log/README.md
index 2cf60ed9e4..60583167ef 100644
--- a/collectors/python.d.plugin/web_log/README.md
+++ b/collectors/python.d.plugin/web_log/README.md
@@ -31,7 +31,7 @@ If Netdata is installed on a system running a web server, it will detect it and
 ![image](https://cloud.githubusercontent.com/assets/2662304/22900686/e283f636-f237-11e6-93d2-cbdf63de150c.png)
 *[**netdata**](https://my-netdata.io/) charts based on metrics collected by querying the `nginx` API (i.e. `/stub_status`).*
 
-> [**netdata**](https://my-netdata.io/) supports `apache`, `nginx`, `lighttpd` and `tomcat`. To obtain real-time information from a web server API, the web server needs to expose it. For directions on configuring your web server, check the config files for each web server. There is a directory with a config file for each web server under [`/etc/netdata/python.d/`](../). 
+> [**netdata**](https://my-netdata.io/) supports `apache`, `nginx`, `lighttpd` and `tomcat`. To obtain real-time information from a web server API, the web server needs to expose it. For directions on configuring your web server, check the config files for each web server. There is a directory with a config file for each web server under `/etc/netdata/python.d/`. 
 
 ## Configuration
 
diff --git a/database/engine/README.md b/database/engine/README.md
index 191366a465..a782716f0c 100644
--- a/database/engine/README.md
+++ b/database/engine/README.md
@@ -44,7 +44,7 @@ section for details.
 
 The `dbengine multihost disk space` option determines the amount of disk space in **MiB** that is dedicated to storing
 Netdata metric values and all related metadata describing them. You can use the [**database engine
-calculator**](/docs/store/change-metrics-storage.md#calculate-the-system-resources-RAM-disk-space-needed-to-store-metrics)
+calculator**](/docs/store/change-metrics-storage.md#calculate-the-system-resources-ram-disk-space-needed-to-store-metrics)
 to correctly set `dbengine multihost disk space` based on your metrics retention policy. The calculator gives an
 accurate estimate based on how many child nodes you have, how many metrics your Agent collects, and more.
 
@@ -62,7 +62,7 @@ Netdata metric values per legacy database engine instance (see [details on the l
 
 When using the multihost database engine, all parent and child nodes share the same `page cache size` and `dbengine
 multihost disk space` in a single dbengine instance. The [**database engine
-calculator**](/docs/store/change-metrics-storage.md#calculate-the-system-resources-RAM-disk-space-needed-to-store-metrics)
+calculator**](/docs/store/change-metrics-storage.md#calculate-the-system-resources-ram-disk-space-needed-to-store-metrics)
 helps you properly set `page cache size` and `dbengine multihost disk space` on your parent node to allocate enough
 resources based on your metrics retention policy and how many child nodes you have.
 
@@ -112,7 +112,7 @@ An important observation is that RAM usage depends on both the `page cache size`
 options.
 
 You can use our [database engine
-calculator](/docs/store/change-metrics-storage.md#calculate-the-system-resources-RAM-disk-space-needed-to-store-metrics)
+calculator](/docs/store/change-metrics-storage.md#calculate-the-system-resources-ram-disk-space-needed-to-store-metrics)
 to validate the memory requirements for your particular system(s) and configuration (**out-of-date**).
 
 ### Disk space requirements
diff --git a/docs/anonymous-statistics.md b/docs/anonymous-statistics.md
index 75e586bd41..5c82e05372 100644
--- a/docs/anonymous-statistics.md
+++ b/docs/anonymous-statistics.md
@@ -91,7 +91,7 @@ update. You can also export the environment variable `DO_NOT_TRACK` with a non-z
 
 When using Docker, **set your `DO_NOT_TRACK` environment variable to `1`.** You can set this variable with the following
 command: `export DO_NOT_TRACK=1`. When creating a container using Netdata's [Docker
-image](/packaging/docker/README.md#run-the-agent-with-the-docker-command) for the first time, this variable will disable
+image](/packaging/docker/README.md#create-a-new-netdata-agent-container) for the first time, this variable will disable
 the anonymous statistics script inside of the container.
 
 Each of these opt-out processes does the following:
diff --git a/docs/collect/application-metrics.md b/docs/collect/application-metrics.md
index fbc0ae249c..4fb9ed6abb 100644
--- a/docs/collect/application-metrics.md
+++ b/docs/collect/application-metrics.md
@@ -29,7 +29,7 @@ Our most popular application collectors:
     rows in less than half a second.
 -   [MySQL](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/mysql/): Collect database global,
     replication, and per-user statistics.
--   [Redis](/collectors/python.d.plugin/redis/): Monitor database status by reading the server's response to the `INFO`
+-   [Redis](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/redis): Monitor database status by reading the server's response to the `INFO`
     command.
 -   [Apache](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/apache/): Collect Apache web
     server performance metrics via the `server-status?auto` endpoint.
diff --git a/docs/collect/system-metrics.md b/docs/collect/system-metrics.md
index 599d6f5832..14e2cc2aa3 100644
--- a/docs/collect/system-metrics.md
+++ b/docs/collect/system-metrics.md
@@ -30,7 +30,7 @@ eBPF collector to analyze how and when a process accesses files, when it makes s
 creating zombie processes, and more.
 
 While the above plugins and associated collectors are the most important for system metrics, there are many others. You
-can find all system collectors in our [supported collectors list](/collectors/COLLECTORS.md#system-metrics).
+can find all system collectors in our [supported collectors list](/collectors/COLLECTORS.md#system-collectors).
 
 ## Collect Windows system metrics
 
diff --git a/docs/configure/common-changes.md b/docs/configure/common-changes.md
index 6749384acd..cf2e5d78a1 100644
--- a/docs/configure/common-changes.md
+++ b/docs/configure/common-changes.md
@@ -31,7 +31,7 @@ section](/daemon/config/README.md#global-section-options) of `netdata.conf`.
 ```
 
 Read our doc on [increasing long-term metrics storage](/docs/store/change-metrics-storage.md) for details, including a
-[calculator](/docs/store/change-metrics-storage.md#calculate-the-system-resources-RAM-disk-space-needed-to-store-metrics)
+[calculator](/docs/store/change-metrics-storage.md#calculate-the-system-resources-ram-disk-space-needed-to-store-metrics)
 to help you determine the exact settings for your desired retention period.
 
 ### Reduce the data collection frequency
diff --git a/docs/configure/secure-nodes.md b/docs/configure/secure-nodes.md
index 180ffe357d..02057ab9e5 100644
--- a/docs/configure/secure-nodes.md
+++ b/docs/configure/secure-nodes.md
@@ -11,7 +11,7 @@ internet at large, anyone can access the dashboard and your node's metrics at `h
 so that the local dashboard was immediately accessible to users, and so that we don't dictate how professionals set up
 and secure their infrastructures. 
 
-Despite this design decision, your [data](/docs/netdata-security.md#your-data-are-safe-with-netdata) and your
+Despite this design decision, your [data](/docs/netdata-security.md#your-data-is-safe-with-netdata) and your
 [systems](/docs/netdata-security.md#your-systems-are-safe-with-netdata) are safe with Netdata. Netdata is read-only,
 cannot do anything other than present metrics, and runs without special/`sudo` privileges. Also, the local dashboard
 only exposes chart metadata and metric values, not raw data.
diff --git a/docs/contributing/contributing-documentation.md b/docs/contributing/contributing-documentation.md
index 22df9fc3e1..76fc609d5f 100644
--- a/docs/contributing/contributing-documentation.md
+++ b/docs/contributing/contributing-documentation.md
@@ -18,7 +18,7 @@ The Netdata team aggregates and publishes all documentation at [learn.netdata.cl
 ## Before you get started
 
 Anyone interested in contributing to documentation should first read the [Netdata style
-guide](/docs/contributing/style-guide.md) and the [Netdata Community Code of Conduct](/CODE_OF_CONDUCT.md).
+guide](/docs/contributing/style-guide.md) and the [Netdata Community Code of Conduct](https://learn.netdata.cloud/contribute/code-of-conduct).
 
 Netdata's documentation uses Markdown syntax. If you're not familiar with Markdown, read the [Mastering
 Markdown](https://guides.github.com/features/mastering-markdown/) guide from GitHub for the basics on creating
@@ -92,7 +92,7 @@ request based on the changes you made in the new branch of your fork.
 
 ## Making a pull request
 
-Pull requests (PRs) should be concise and informative. See our [PR guidelines](/CONTRIBUTING.md#pr-guidelines) for
+Pull requests (PRs) should be concise and informative. See our [PR guidelines](https://learn.netdata.cloud/contribute/handbook#pr-guidelines) for
 specifics.
 
 - The title must follow the [imperative mood](https://en.wikipedia.org/wiki/Imperative_mood) and be no more than ~50
diff --git a/docs/contributing/style-guide.md b/docs/contributing/style-guide.md
index 625237bc07..025b45f64f 100644
--- a/docs/contributing/style-guide.md
+++ b/docs/contributing/style-guide.md
@@ -421,7 +421,7 @@ In Markdown, use the standard image syntax, `![]()`, and place the alt text betw
 using our logo:
 
 ```markdown
-![The Netdata logo](../../web/gui/images/netdata-logomark.svg)
+![The Netdata logo](/web/gui/static/img/netdata-logomark.svg)
 ```
 
 Reference in-product text, code samples, and terminal output with actual text content, not screen captures or other
diff --git a/docs/dashboard/customize.mdx b/docs/dashboard/customize.mdx
index 2c82a1c50e..d203379110 100644
--- a/docs/dashboard/customize.mdx
+++ b/docs/dashboard/customize.mdx
@@ -25,7 +25,7 @@ Here are a few popular settings:
 ### Change chart legend position
 
 Find this setting under the **Visual** tab. By default, Netdata places the [legend of
-dimensions](/docs/dashboard/dimensions-contexts-families.mdx#dimensions) _below_ charts. Click this toggle to
+dimensions](/docs/dashboard/dimensions-contexts-families.mdx#dimension) _below_ charts. Click this toggle to
 move the legend to the _right_ of charts.
 
 ### Change theme
diff --git a/docs/dashboard/dimensions-contexts-families.mdx b/docs/dashboard/dimensions-contexts-families.mdx
index da9aad78f9..0c6dd2adc9 100644
--- a/docs/dashboard/dimensions-contexts-families.mdx
+++ b/docs/dashboard/dimensions-contexts-families.mdx
@@ -26,7 +26,7 @@ utilization is represented as a percentage, disk I/O as `MiB/s`, and available R
 Beneath every chart (or on the right-side if you configure the dashboard) is a legend of dimensions. When there are
 multiple dimensions, you'll see a different entry in the legend for each dimension.
 
-The **Apps CPU Time** chart (with the [context](#contexts) `apps.cpu`), which visualizes CPU utilization of
+The **Apps CPU Time** chart (with the [context](#context) `apps.cpu`), which visualizes CPU utilization of
 different types of processes/services/applications on your node, always provides a vibrant example of a chart with
 multiple dimensions.
 
diff --git a/docs/export/external-databases.md b/docs/export/external-databases.md
index 309b03a878..67a55baadb 100644
--- a/docs/export/external-databases.md
+++ b/docs/export/external-databases.md
@@ -51,7 +51,7 @@ documentation and the [enabling a connector](/docs/export/enable-connector.md) d
 -   **KairosDB**: [Graphite](/exporting/graphite/README.md), [OpenTSDB](/exporting/opentsdb/README.md)
 -   **M3DB**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
 -   **MetricFire**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
--   **MongoDB**: [MongoDB](/exporting/mongodb/)
+-   **MongoDB**: [MongoDB](/exporting/mongodb/README.md)
 -   **New Relic**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
 -   **OpenTSDB**: [OpenTSDB](/exporting/opentsdb/README.md), [Prometheus remote
     write](/exporting/prometheus/remote_write/README.md)
diff --git a/docs/getting-started.md b/docs/getting-started.md
index 2d1f3de6d9..2dd045f090 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -28,7 +28,7 @@ dashboard](https://user-images.githubusercontent.com/1153921/80825153-abaec600-8
 
 **What's next?**: 
 
--   Read more about the [standard Netdata dashboard](/web/gui/).
+-   Read more about the [standard Netdata dashboard](/web/gui/README.md).
 -   Learn all the specifics of [using charts](/web/README.md#using-charts) or the differences between [charts,
     context, and families](/web/README.md#charts-contexts-families).
 
@@ -51,9 +51,9 @@ Once you save your changes, [restart Netdata](#start-stop-and-restart-netdata) t
 
 -   [Change how long Netdata stores metrics](#change-how-long-netdata-stores-metrics) by changing the `page cache size`
     and `dbengine disk space` settings in `netdata.conf`.
--   Move Netdata's dashboard to a [different port](/web/server/) or enable TLS/HTTPS
+-   Move Netdata's dashboard to a [different port](/web/server/README.md) or enable TLS/HTTPS
     encryption.
--   See all the `netdata.conf` options in our [daemon configuration documentation](/daemon/config/).
+-   See all the `netdata.conf` options in our [daemon configuration documentation](/daemon/config/README.md).
 -   Run your own [registry](/registry/README.md#run-your-own-registry).
 
 ## Change how long Netdata stores metrics
@@ -86,7 +86,7 @@ Netdata](#start-stop-and-restart-netdata).
 
 However, auto-detection only works if you installed the source using its standard installation procedure. If Netdata
 isn't collecting metrics after a restart, your source probably isn't configured correctly. Look at the [external plugin
-documentation](/collectors/plugins.d/) to find the appropriate module for your source. Those pages will contain
+documentation](/collectors/plugins.d/README.md) to find the appropriate module for your source. Those pages will contain
 more information about how to configure your source for auto-detection.
 
 Some modules, like `chrony`, are disabled by default and must be enabled manually for auto-detection to work.
@@ -186,7 +186,7 @@ Find the `SEND_EMAIL="YES"` line and change it to `SEND_EMAIL="NO"`.
 -   Follow the [health quickstart](/health/QUICKSTART.md) to locate and edit existing health entities, and then
     create your own.
 -   See all the alarm options via the [health configuration reference](/health/REFERENCE.md).
--   Add a new notification method, like [Slack](/health/notifications/slack/).
+-   Add a new notification method, like [Slack](/health/notifications/slack/README.md).
 
 ## Monitor multiple systems with Netdata Cloud
 
@@ -230,7 +230,7 @@ Take a look at some more advanced features and configurations:
 -   Enable long-term archiving of Netdata metrics via [exporting engine](/exporting/README.md) to time-series databases.
 -   Improve security by putting Netdata behind an [Nginx proxy with SSL](/docs/Running-behind-nginx.md).
 
-Or, learn more about how you can contribute to [Netdata core](/CONTRIBUTING.md) or our
+Or, learn more about how you can contribute to [Netdata core](/README.md#contribute) o