Docs: Fix internal links and remove obsolete admonitions (#8946)

* Fixed a few more links

* Remove old syntax

* Abs-relative links to files in docs folder

* Trying to fix nother doc learn link

* Fix a few more links

* Add testing doc

* Tracking down mysteries

* Cleanup

* Update broken external links

* Remove index.html that appeared from testing

* Fix remainder of links

8 files changed, 23 insertions, 22 deletions

diff --git a/packaging/installer/UPDATE.md b/packaging/installer/UPDATE.md
index c5f56275f9..e398be13d8 100644
--- a/packaging/installer/UPDATE.md
+++ b/packaging/installer/UPDATE.md
@@ -95,8 +95,9 @@ First, pull the latest version of the image.
 docker pull netdata/netdata:latest
 ```
 
-Next, to stop and remove any containers using the `netdata/netdata` image. Replace `netdata` if you changed
-it from the default in our [Docker installation instructions](../docker/README.md#run-netdata-with-the-docker-command).
+Next, to stop and remove any containers using the `netdata/netdata` image. Replace `netdata` if you changed it from the
+default in our [Docker installation
+instructions](/packaging/docker/README.md#run-the-agent-with-the-docker-command).
 
 ```bash
 docker stop netdata
@@ -104,8 +105,8 @@ docker rm netdata
 ```
 
 You can now re-create your Netdata container using the `docker` command or a `docker-compose.yml` file. See our [Docker
-installation instructions](../docker/README.md#run-netdata-with-the-docker-command) for details. For example, using the
-`docker` command:
+installation instructions](/packaging/docker/README.md#run-the-agent-with-the-docker-command) for details. For
+example, using the `docker` command:
 
 ```bash
 docker run -d --name=netdata \
diff --git a/packaging/installer/methods/cloud-providers.md b/packaging/installer/methods/cloud-providers.md
index 457a4d015a..90989548b3 100644
--- a/packaging/installer/methods/cloud-providers.md
+++ b/packaging/installer/methods/cloud-providers.md
@@ -58,11 +58,11 @@ command from a remote system, and it fails, it's likely that a firewall is block
 Another option is to put Netdata behind web server, which will proxy requests through standard HTTP/HTTPS ports
 (80/443), which are likely already open on your instance. We have a number of guides available:
 
--   [Apache](../../../docs/Running-behind-apache.md)
--   [Nginx](../../../docs/Running-behind-nginx.md)
--   [Caddy](../../../docs/Running-behind-caddy.md)
--   [HAProxy](../../../docs/Running-behind-haproxy.md)
--   [lighttpd](../../../docs/Running-behind-lighttpd.md)
+-   [Apache](/docs/Running-behind-apache.md)
+-   [Nginx](/docs/Running-behind-nginx.md)
+-   [Caddy](/docs/Running-behind-caddy.md)
+-   [HAProxy](/docs/Running-behind-haproxy.md)
+-   [lighttpd](/docs/Running-behind-lighttpd.md)
 
 The next few sections outline how to add firewall rules to GCP, AWS, and Azure instances.
 
diff --git a/packaging/installer/methods/kickstart.md b/packaging/installer/methods/kickstart.md
index cd3c138654..528c7c50b2 100644
--- a/packaging/installer/methods/kickstart.md
+++ b/packaging/installer/methods/kickstart.md
@@ -44,7 +44,7 @@ installation. Here are a few important parameters:
 -   `--dont-start-it`: Prevent the installer from starting Netdata automatically.
 -   `--stable-channel`: Automatically update only on the release of new major versions.
 -   `--nightly-channel`: Automatically update on every new nightly build.
--   `--disable-telemetry`: Opt-out of [anonymous statistics](../../../docs/anonymous-statistics.md) we use to make
+-   `--disable-telemetry`: Opt-out of [anonymous statistics](/docs/anonymous-statistics.md) we use to make
     Netdata better.
 -   `--no-updates`: Prevent automatic updates of any kind.
 -   `--local-files`: Used for [offline installations](offline.md). Pass four file paths: the Netdata
@@ -65,8 +65,8 @@ If the script is valid, this command will return `OK, VALID`.
 
 ## What's next?
 
-When you finish installing Netdata, be sure to visit our [step-by-step tutorial](../../../docs/step-by-step/step-00.md)
+When you finish installing Netdata, be sure to visit our [step-by-step tutorial](/docs/step-by-step/step-00.md)
 for a fully-guided tour into Netdata's capabilities and how to configure it according to your needs.
 
 Or, if you're a monitoring and system administration pro, skip ahead to our [getting started
-guide](../../../docs/getting-started.md) for a quick overview.
+guide](/docs/getting-started.md) for a quick overview.
diff --git a/packaging/installer/methods/macos.md b/packaging/installer/methods/macos.md
index d51ffccf23..9e073f509e 100644
--- a/packaging/installer/methods/macos.md
+++ b/packaging/installer/methods/macos.md
@@ -56,7 +56,7 @@ to install some of Netdata's prerequisites.
 brew install ossp-uuid autoconf automake pkg-config libuv lz4 json-c openssl@1.1
 ```
 
-If you want to use the [database engine](../../../database/engine/README.md) to store your metrics, you need to download
+If you want to use the [database engine](/database/engine/README.md) to store your metrics, you need to download
 and install the [Judy library](https://sourceforge.net/projects/judy/) before proceeding compiling Netdata.
 
 Next, download Netdata from our GitHub repository:
@@ -79,8 +79,8 @@ sudo ./netdata-installer.sh --install /usr/local
 
 ## What's next?
 
-When you finish installing Netdata, be sure to visit our [step-by-step tutorial](../../../docs/step-by-step/step-00.md)
+When you finish installing Netdata, be sure to visit our [step-by-step tutorial](/docs/step-by-step/step-00.md)
 for a fully-guided tour into Netdata's capabilities and how to configure it according to your needs.
 
 Or, if you're a monitoring and system administration pro, skip ahead to our [getting started
-guide](../../../docs/getting-started.md) for a quick overview.
+guide](/docs/getting-started.md) for a quick overview.
diff --git a/packaging/installer/methods/manual.md b/packaging/installer/methods/manual.md
index fdcabaf89d..7aa9a7be24 100644
--- a/packaging/installer/methods/manual.md
+++ b/packaging/installer/methods/manual.md
@@ -216,8 +216,8 @@ In most cases, you can do this by running `CC=gcc ./netdata-installer.sh`.
 
 ## What's next?
 
-When you finish installing Netdata, be sure to visit our [step-by-step tutorial](../../../docs/step-by-step/step-00.md)
+When you finish installing Netdata, be sure to visit our [step-by-step tutorial](/docs/step-by-step/step-00.md)
 for a fully-guided tour into Netdata's capabilities and how to configure it according to your needs.
 
 Or, if you're a monitoring and system administration pro, skip ahead to our [getting started
-guide](../../../docs/getting-started.md) for a quick overview.
+guide](/docs/getting-started.md) for a quick overview.
diff --git a/packaging/installer/methods/offline.md b/packaging/installer/methods/offline.md
index adb829d139..dab7650737 100644
--- a/packaging/installer/methods/offline.md
+++ b/packaging/installer/methods/offline.md
@@ -76,8 +76,8 @@ bash kickstart.sh --local-files /tmp/netdata-(version-number-here).tar.gz /tmp/s
 bash kickstart-static64.sh --local-files /tmp/netdata-(version-number-here).gz.run /tmp/sha256sums.txt
 ```
 
-Now that Netdata is installed, be sure to visit our [getting started guide](../../../docs/getting-started.md) for a
+Now that Netdata is installed, be sure to visit our [getting started guide](/docs/getting-started.md) for a
 quick overview of configuring Netdata, enabling plugins, and controlling Netdata's daemon. 
 
 Or, get the full guided tour of Netdata's capabilities with our [step-by-step
-tutorial](../../../docs/step-by-step/step-00.md)!
+tutorial](/docs/step-by-step/step-00.md)!
diff --git a/packaging/installer/methods/packages.md b/packaging/installer/methods/packages.md
index 1d8887e97a..1573445bcb 100644
--- a/packaging/installer/methods/packages.md
+++ b/packaging/installer/methods/packages.md
@@ -50,8 +50,8 @@ If you are using such a setup, there are a couple of ways you can work around th
 
 ## What's next?
 
-When you finish installing Netdata, be sure to visit our [step-by-step tutorial](../../../docs/step-by-step/step-00.md)
+When you finish installing Netdata, be sure to visit our [step-by-step tutorial](/docs/step-by-step/step-00.md)
 for a fully-guided tour into Netdata's capabilities and how to configure it according to your needs.
 
 Or, if you're a monitoring and system administration pro, skip ahead to our [getting started
-guide](../../../docs/getting-started.md) for a quick overview.
+guide](/docs/getting-started.md) for a quick overview.
diff --git a/packaging/installer/methods/synology.md b/packaging/installer/methods/synology.md
index a8b60b0f7e..1b743d164c 100644
--- a/packaging/installer/methods/synology.md
+++ b/packaging/installer/methods/synology.md
@@ -24,7 +24,7 @@ installations run it as the `netdata` user, you might wish to do the same. This
 2.  Create a user `netdata` via the Synology user interface. Give it no access to anything and a random password. Assign
     the user to the `netdata` group. Netdata will chuid to this user when running.
 3.  Change ownership of the following directories, as defined in [Netdata
-    Security](../../../docs/netdata-security.md#security-design):
+    Security](/docs/netdata-security.md#security-design):
 
 ```sh
 chown -R root:netdata /opt/netdata/usr/share/netdata