Covert our documentation links to GH absolute links (#14344)

Signed-off-by: Tasos Katsoulas <tasos@netdata.cloud>

16 files changed, 133 insertions, 130 deletions

diff --git a/packaging/PLATFORM_SUPPORT.md b/packaging/PLATFORM_SUPPORT.md
index 084672d677..62e208c73f 100644
--- a/packaging/PLATFORM_SUPPORT.md
+++ b/packaging/PLATFORM_SUPPORT.md
@@ -39,7 +39,8 @@ The following table shows a general outline of the various support tiers and cat
 | Previously Supported | Users asked to upgrade | None | None | Yes, but only already published versions | Best Effort |
 
 - ‘Bug Support’: How we handle of platform-specific bugs.
-- ‘Guaranteed Configurations’: Which runtime configurations for the agent we try to guarantee will work with minimal effort from users.
+- ‘Guaranteed Configurations’: Which runtime configurations for the agent we try to guarantee will work with minimal
+  effort from users.
 - ‘CI Coverage’: What level of coverage we provide for the platform in CI.
 - ‘Native Packages’: Whether we provide native packages for the system package manager for the platform.
 - ‘Static Build Support’: How well our static builds are expected to work on the platform.
@@ -50,31 +51,32 @@ The following table shows a general outline of the various support tiers and cat
 
 Platforms in the core support tier are our top priority. They are covered rigorously in our CI, usually
 include official binary packages, and any platform-specific bugs receive a high priority. From the perspective
-of our developers, platforms in the core support tier _must_ work, with almost no exceptions. Our [static
-builds](#static-builds) are expected to work on these platforms if available. Source-based installs are expected
+of our developers, platforms in the core support tier _must_ work, with almost no exceptions.
+Our [static builds](#static-builds) are expected to work on these platforms if available. Source-based installs are
+expected
 to work on these platforms with minimal user effort.
 
-| Platform | Version | Official Native Packages | Notes |
-| -------- | ------- | ------------------------ | ----- |
-| Alpine Linux | 3.17 | No | The latest release of Alpine Linux is guaranteed to remain at **Core** tier due to usage for our Docker images |
-| Alma Linux | 9.x | x86\_64, AArch64 | Also includes support for Rocky Linux and other ABI compatible RHEL derivatives |
-| Alma Linux | 8.x | x86\_64, AArch64 | Also includes support for Rocky Linux and other ABI compatible RHEL derivatives |
-| CentOS | 7.x | x86\_64 | |
-| Docker | 19.03 or newer | x86\_64, i386, ARMv7, AArch64, POWER8+ | See our [Docker documentation](/packaging/docker/README.md) for more info on using Netdata on Docker |
-| Debian | 11.x | x86\_64, i386, ARMv7, AArch64 | |
-| Debian | 10.x | x86\_64, i386, ARMv7, AArch64 | |
-| Fedora | 37 | x86\_64, AArch64 | |
-| Fedora | 36 | x86\_64, AArch64 | |
-| openSUSE | Leap 15.4 | x86\_64, AArch64 | |
-| Oracle Linux | 9.x | x86\_64, AArch64 | |
-| Oracle Linux | 8.x | x86\_64, AArch64 | |
-| Red Hat Enterprise Linux | 9.x | x86\_64, AArch64 | |
-| Red Hat Enterprise Linux | 8.x | x86\_64, AArch64 | |
-| Red Hat Enterprise Linux | 7.x | x86\_64 | |
-| Ubuntu | 22.10 | x86\_64, ARMv7, AArch64 | |
-| Ubuntu | 22.04 | x86\_64, ARMv7, AArch64 | |
-| Ubuntu | 20.04 | x86\_64, ARMv7, AArch64 | |
-| Ubuntu | 18.04 | x86\_64, i386, ARMv7, AArch64 | |
+| Platform                 | Version        | Official Native Packages               | Notes                                                                                                                                              |
+|--------------------------|----------------|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| Alpine Linux             | 3.17           | No                                     | The latest release of Alpine Linux is guaranteed to remain at **Core** tier due to usage for our Docker images                                     |
+| Alma Linux               | 9.x            | x86\_64, AArch64                       | Also includes support for Rocky Linux and other ABI compatible RHEL derivatives                                                                    |
+| Alma Linux               | 8.x            | x86\_64, AArch64                       | Also includes support for Rocky Linux and other ABI compatible RHEL derivatives                                                                    |
+| CentOS                   | 7.x            | x86\_64                                |                                                                                                                                                    |
+| Docker                   | 19.03 or newer | x86\_64, i386, ARMv7, AArch64, POWER8+ | See our [Docker documentation](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md) for more info on using Netdata on Docker |
+| Debian                   | 11.x           | x86\_64, i386, ARMv7, AArch64          |                                                                                                                                                    |
+| Debian                   | 10.x           | x86\_64, i386, ARMv7, AArch64          |                                                                                                                                                    |
+| Fedora                   | 37             | x86\_64, AArch64                       |                                                                                                                                                    |
+| Fedora                   | 36             | x86\_64, AArch64                       |                                                                                                                                                    |
+| openSUSE                 | Leap 15.4      | x86\_64, AArch64                       |                                                                                                                                                    |
+| Oracle Linux             | 9.x            | x86\_64, AArch64                       |                                                                                                                                                    |
+| Oracle Linux             | 8.x            | x86\_64, AArch64                       |                                                                                                                                                    |
+| Red Hat Enterprise Linux | 9.x            | x86\_64, AArch64                       |                                                                                                                                                    |
+| Red Hat Enterprise Linux | 8.x            | x86\_64, AArch64                       |                                                                                                                                                    |
+| Red Hat Enterprise Linux | 7.x            | x86\_64                                |                                                                                                                                                    |
+| Ubuntu                   | 22.10          | x86\_64, ARMv7, AArch64                |                                                                                                                                                    |
+| Ubuntu                   | 22.04          | x86\_64, ARMv7, AArch64                |                                                                                                                                                    |
+| Ubuntu                   | 20.04          | x86\_64, ARMv7, AArch64                |                                                                                                                                                    |
+| Ubuntu                   | 18.04          | x86\_64, i386, ARMv7, AArch64          |                                                                                                                                                    |
 
 ### Intermediate
 
@@ -85,13 +87,13 @@ platforms that we officially support ourselves to the intermediate tier. Our [st
 expected to work on these platforms if available. Source-based installs are expected to work on these platforms
 with minimal user effort.
 
-| Platform | Version | Official Native Packages | Notes |
-| -------- | ------- | ------------------------ | ----- |
-| Alpine Linux | 3.16 | No | |
-| Alpine Linux | 3.15 | No | |
-| Alpine Linux | 3.14 | No | |
-| Arch Linux | Latest | No | We officially recommend the community packages available for Arch Linux |
-| Manjaro Linux | Latest | No | We officially recommend the community packages available for Arch Linux |
+| Platform      | Version | Official Native Packages | Notes                                                                   |
+|---------------|---------|--------------------------|-------------------------------------------------------------------------|
+| Alpine Linux  | 3.16    | No                       |                                                                         |
+| Alpine Linux  | 3.15    | No                       |                                                                         |
+| Alpine Linux  | 3.14    | No                       |                                                                         |
+| Arch Linux    | Latest  | No                       | We officially recommend the community packages available for Arch Linux |
+| Manjaro Linux | Latest  | No                       | We officially recommend the community packages available for Arch Linux |
 
 ### Community
 
@@ -101,19 +103,19 @@ to add support for a new platform, that platform generally will start in this ti
 are expected to work on these platforms if available. Source-based installs are usually expected to work on these
 platforms, but may require some extra effort from users.
 
-| Platform | Version | Official Native Packages | Notes |
-| -------- | ------- | ------------------------ | ----- |
-| Alpine Linux | Edge | No | |
-| Clear Linux | Latest | No | |
-| Debian | Sid | No | |
-| Fedora | Rawhide | No | |
-| FreeBSD | 13-STABLE | No | Netdata is included in the FreeBSD Ports Tree, and this is the recommended installation method on FreeBSD |
-| FreeBSD | 12-STABLE | No | Netdata is included in the FreeBSD Ports Tree, and this is the recommended installation method on FreeBSD |
-| Gentoo | Latest | No | |
-| macOS | 12 | No | Currently only works for Intel-based hardware. Requires Homebrew for dependencies |
-| macOS | 11 | No | Currently only works for Intel-based hardware. Requires Homebrew for dependencies.  |
-| macOS | 10.15 | No | Requires Homebrew for dependencies.  |
-| openSUSE | Tumbleweed | No | |
+| Platform     | Version    | Official Native Packages | Notes                                                                                                     |
+|--------------|------------|--------------------------|-----------------------------------------------------------------------------------------------------------|
+| Alpine Linux | Edge       | No                       |                                                                                                           |
+| Clear Linux  | Latest     | No                       |                                                                                                           |
+| Debian       | Sid        | No                       |                                                                                                           |
+| Fedora       | Rawhide    | No                       |                                                                                                           |
+| FreeBSD      | 13-STABLE  | No                       | Netdata is included in the FreeBSD Ports Tree, and this is the recommended installation method on FreeBSD |
+| FreeBSD      | 12-STABLE  | No                       | Netdata is included in the FreeBSD Ports Tree, and this is the recommended installation method on FreeBSD |
+| Gentoo       | Latest     | No                       |                                                                                                           |
+| macOS        | 12         | No                       | Currently only works for Intel-based hardware. Requires Homebrew for dependencies                         |
+| macOS        | 11         | No                       | Currently only works for Intel-based hardware. Requires Homebrew for dependencies.                        |
+| macOS        | 10.15      | No                       | Requires Homebrew for dependencies.                                                                       |
+| openSUSE     | Tumbleweed | No                       |                                                                                                           |
 
 ## Third-party supported platforms
 
@@ -142,22 +144,22 @@ Platforms that meet these criteria will be immediately transitioned to the **Pre
 with no prior warning from Netdata and no deprecation notice, unlike those being dropped for technical reasons,
 as our end of support should already coincide with the end of the normal support lifecycle for that platform.
 
-On occasion, we may also drop support for a platform due to technical limitations.  In such cases, this will be
+On occasion, we may also drop support for a platform due to technical limitations. In such cases, this will be
 announced in the release notes of the next stable release with a deprecation notice. The platform will be supported
 for _that release_, and will be removed from nightlies some time before the next release after that one.
 
 This is a list of platforms that we have supported in the recent past but no longer officially support:
 
-| Platform | Version | Notes |
-| -------- | ------- | ----- |
-| Alpine Linux | 3.13 | EOL as of 2022-11-01 |
-| Alpine Linux | 3.12 | EOL as of 2022-05-01 |
-| Debian | 9.x | EOL as of 2022-06-30 |
-| Fedora | 35 | EOL as of 2022-12-13 |
-| Fedora | 34 | EOL as of 2022-06-07 |
-| openSUSE | Leap 15.3 | EOL as of 2022-12-01 |
-| Ubuntu | 21.10 | EOL as of 2022-07-31 |
-| Ubuntu | 21.04 | EOL as of 2022-01-01 |
+| Platform     | Version   | Notes                |
+|--------------|-----------|----------------------|
+| Alpine Linux | 3.13      | EOL as of 2022-11-01 |
+| Alpine Linux | 3.12      | EOL as of 2022-05-01 |
+| Debian       | 9.x       | EOL as of 2022-06-30 |
+| Fedora       | 35        | EOL as of 2022-12-13 |
+| Fedora       | 34        | EOL as of 2022-06-07 |
+| openSUSE     | Leap 15.3 | EOL as of 2022-12-01 |
+| Ubuntu       | 21.10     | EOL as of 2022-07-31 |
+| Ubuntu       | 21.04     | EOL as of 2022-01-01 |
 
 ## Static builds
 
diff --git a/packaging/docker/README.md b/packaging/docker/README.md
index 67cde0fc75..aec5723e3f 100644
--- a/packaging/docker/README.md
+++ b/packaging/docker/README.md
@@ -16,7 +16,7 @@ you get set up quickly, and doesn't install anything permanent on the system, wh
 See our full list of Docker images at [Docker Hub](https://hub.docker.com/r/netdata/netdata).
 
 Starting with v1.30, Netdata collects anonymous usage information by default and sends it to a self-hosted PostHog instance within the Netdata infrastructure. Read
-about the information collected, and learn how to-opt, on our [anonymous statistics](/docs/anonymous-statistics.md)
+about the information collected, and learn how to-opt, on our [anonymous statistics](https://github.com/netdata/netdata/blob/master/docs/anonymous-statistics.md)
 page.
 
 The usage statistics are _vital_ for us, as we use them to discover bugs and prioritize new features. We thank you for
@@ -176,7 +176,7 @@ to restart the container: `docker restart netdata`.
 
 ### Host-editable configuration
 
-> **Warning**: [edit-config](/docs/configure/nodes.md#the-netdata-config-directory) script doesn't work when executed on
+> **Warning**: [edit-config](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#the-netdata-config-directory) script doesn't work when executed on
 > the host system.
 
 If you want to make your container's configuration directory accessible from the host system, you need to use a
@@ -322,7 +322,7 @@ your machine from within the container. Please read the following carefully.
 #### Docker socket proxy (safest option)
 
 Deploy a Docker socket proxy that accepts and filters out requests using something like
-[HAProxy](/docs/Running-behind-haproxy.md) so that it restricts connections to read-only access to the CONTAINERS
+[HAProxy](https://github.com/netdata/netdata/blob/master/docs/Running-behind-haproxy.md) so that it restricts connections to read-only access to the CONTAINERS
 endpoint.
 
 The reason it's safer to expose the socket to the proxy is because Netdata has a TCP port exposed outside the Docker
@@ -441,13 +441,13 @@ services:
 ### Pass command line options to Netdata
 
 Since we use an [ENTRYPOINT](https://docs.docker.com/engine/reference/builder/#entrypoint) directive, you can provide
-[Netdata daemon command line options](/daemon/README.md#command-line-options) such as the IP address Netdata will be
+[Netdata daemon command line options](https://github.com/netdata/netdata/blob/master/daemon/README.md#command-line-options) such as the IP address Netdata will be
 running on, using the [command instruction](https://docs.docker.com/engine/reference/builder/#cmd). 
 
 ## Install the Agent using Docker Compose with SSL/TLS enabled HTTP Proxy
 
 For a permanent installation on a public server, you should [secure the Netdata
-instance](/docs/netdata-security.md). This section contains an example of how to install Netdata with an SSL
+instance](https://github.com/netdata/netdata/blob/master/docs/netdata-security.md). This section contains an example of how to install Netdata with an SSL
 reverse proxy and basic authentication.
 
 You can use the following `docker-compose.yml` and Caddyfile files to run Netdata with Docker. Replace the domains and
diff --git a/packaging/installer/README.md b/packaging/installer/README.md
index 75a0114e52..90d3b8de2f 100644
--- a/packaging/installer/README.md
+++ b/packaging/installer/README.md
@@ -24,7 +24,7 @@ packages. We recommend you install Netdata using one of the methods listed below
 checksum-verified packages.
 
 Netdata collects anonymous usage information by default and sends it to our self hosted [PostHog](https://github.com/PostHog/posthog) installation. PostHog is an open source product analytics platform, you can read
-about the information collected, and learn how to-opt, on our [anonymous statistics](/docs/anonymous-statistics.md)
+about the information collected, and learn how to-opt, on our [anonymous statistics](https://github.com/netdata/netdata/blob/master/docs/anonymous-statistics.md)
 page.
 
 The usage statistics are _vital_ for us, as we use them to discover bugs and prioritize new features. We thank you for
@@ -49,17 +49,17 @@ This script will preferentially use native DEB/RPM packages if we provide them f
 
 To see more information about this installation script, including how to disable automatic updates, get nightly vs.
 stable releases, or disable anonymous statistics, see the [`kickstart.sh` method
-page](/packaging/installer/methods/kickstart.md).
+page](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
 
 Scroll down for details about [automatic updates](#automatic-updates) or [nightly vs. stable
 releases](#nightly-vs-stable-releases).
 
 ### Post-installation
 
-When you're finished with installation, check out our [single-node](/docs/quickstart/single-node.md) or
-[infrastructure](/docs/quickstart/infrastructure.md) monitoring quickstart guides based on your use case.
+When you're finished with installation, check out our [single-node](https://github.com/netdata/netdata/blob/master/docs/quickstart/single-node.md) or
+[infrastructure](https://github.com/netdata/netdata/blob/master/docs/quickstart/infrastructure.md) monitoring quickstart guides based on your use case.
 
-Or, skip straight to [configuring the Netdata Agent](/docs/configure/nodes.md).
+Or, skip straight to [configuring the Netdata Agent](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md).
 
 Read through Netdata's [documentation](https://learn.netdata.cloud/docs), which is structured based on actions and
 solutions, to enable features like health monitoring, alarm notifications, long-term metrics storage, exporting to
@@ -68,7 +68,7 @@ external databases, and more.
 ## Have a different operating system, or want to try another method?
 
 Netdata works on many different platforms. To see all supported platforms, check out our [platform support
-policy](/packaging/PLATFORM_SUPPORT.md).
+policy](https://github.com/netdata/netdata/blob/master/packaging/PLATFORM_SUPPORT.md).
 
 Below, you can find a few additional installation methods, followed by separate instructions for a variety of unique
 operating systems.
@@ -123,7 +123,7 @@ wget -O /tmp/netdata-kickstart.sh https://my-netdata.io/kickstart.sh && sh /tmp/
 ```
 
 With automatic updates disabled, you can choose exactly when and how you [update
-Netdata](/packaging/installer/UPDATE.md).
+Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md).
 
 ### Network usage of Netdata’s automatic updater
 
@@ -182,8 +182,8 @@ man-in-the-middle attacks.
 ### CentOS 6 and CentOS 8
 
 To install the Agent on certain CentOS and RHEL systems, you must enable non-default repositories, such as EPEL or
-PowerTools, to gather hard dependencies. See the [CentOS 6](/packaging/installer/methods/manual.md#centos--rhel-6x) and
-[CentOS 8](/packaging/installer/methods/manual.md#centos--rhel-8x) sections for more information.
+PowerTools, to gather hard dependencies. See the [CentOS 6](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#centos--rhel-6x) and
+[CentOS 8](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#centos--rhel-8x) sections for more information.
 
 ### Access to file is not permitted
 
@@ -217,6 +217,6 @@ both.
 
 Our current build process has some issues when using certain configurations of the `clang` C compiler on Linux. See [the
 section on `nonrepresentable section on output`
-errors](/packaging/installer/methods/manual.md#nonrepresentable-section-on-output-errors) for a workaround.
+errors](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#nonrepresentable-section-on-output-errors) for a workaround.
 
 
diff --git a/packaging/installer/REINSTALL.md b/packaging/installer/REINSTALL.md
index 6446da5221..c24fdee8c2 100644
--- a/packaging/installer/REINSTALL.md
+++ b/packaging/installer/REINSTALL.md
@@ -18,11 +18,11 @@ Netdata Agent on your node.
 ### Reinstalling with the same install type
 
 Run the one-line installer script with the `--reinstall` parameter to reinstall the Netdata Agent. This will preserve
-any [user configuration](/docs/configure/nodes.md) in `netdata.conf` or other files, and will keep the same install
+any [user configuration](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md) in `netdata.conf` or other files, and will keep the same install
 type that was used for the original install.
 
 If you used any [optional
-parameters](/packaging/installer/methods/kickstart.md#optional-parameters-to-alter-your-installation) during initial
+parameters](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md#optional-parameters-to-alter-your-installation) during initial
 installation, you need to pass them to the script again during reinstallation. If you cannot remember which options you
 used, read the contents of the `.environment` file and look for a `REINSTALL_OPTIONS` line. This line contains a list of
 optional parameters.
@@ -39,7 +39,7 @@ getting a badly broken installation working again. Unlike the regular `--reinsta
 different install type than the original install used.
 
 If you used any [optional
-parameters](/packaging/installer/methods/kickstart.md#optional-parameters-to-alter-your-installation) during initial
+parameters](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md#optional-parameters-to-alter-your-installation) during initial
 installation, you need to pass them to the script again during reinstallation. If you cannot remember which options you
 used, read the contents of the `.environment` file and look for a `REINSTALL_OPTIONS` line. This line contains a list of
 optional parameters.
@@ -69,8 +69,8 @@ When copying these directories back after the reinstall, you may need to update
 ## Troubleshooting
 
 If you still experience problems with your Netdata Agent installation after following one of these processes, the next
-best route is to [uninstall](/packaging/installer/UNINSTALL.md) and then try a fresh installation using the [one-line
-installer](/packaging/installer/methods/kickstart.md).
+best route is to [uninstall](https://github.com/netdata/netdata/blob/master/packaging/installer/UNINSTALL.md) and then try a fresh installation using the [one-line
+installer](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
 
 You can also post to our [community forums](https://community.netdata.cloud/c/support/13) or create a new [bug
 report](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml).
diff --git a/packaging/installer/UNINSTALL.md b/packaging/installer/UNINSTALL.md
index 669af609fb..2ff22f5c64 100644
--- a/packaging/installer/UNINSTALL.md
+++ b/packaging/installer/UNINSTALL.md
@@ -12,7 +12,7 @@ learn_rel_path: "Installation"
 
 > ⚠️ If you're having trouble updating Netdata, moving from one installation method to another, or generally having
 > issues with your Netdata Agent installation, consider our [**reinstall Netdata**
-> doc](/packaging/installer/REINSTALL.md) instead of removing the Netdata Agent entirely.
+> doc](https://github.com/netdata/netdata/blob/master/packaging/installer/REINSTALL.md) instead of removing the Netdata Agent entirely.
 
 The recommended method to uninstall Netdata on a system is to use our kickstart installer script with the `--uninstall` option like so:
 
diff --git a/packaging/installer/UPDATE.md b/packaging/installer/UPDATE.md
index e8869c6752..9d4289f85c 100644
--- a/packaging/installer/UPDATE.md
+++ b/packaging/installer/UPDATE.md
@@ -15,7 +15,7 @@ you installed. If you opted out of automatic updates, you need to update your Ne
 or stable version. You can also [enable or disable automatic updates on an existing install](#control-automatic-updates).
 
 > 💡 Looking to reinstall the Netdata Agent to enable a feature, update an Agent that cannot update automatically, or
-> troubleshoot an error during the installation process? See our [reinstallation doc](/packaging/installer/REINSTALL.md)
+> troubleshoot an error during the installation process? See our [reinstallation doc](https://github.com/netdata/netdata/blob/master/packaging/installer/REINSTALL.md)
 > for reinstallation steps.
 
 Before you update the Netdata Agent, check to see if your Netdata Agent is already up-to-date by clicking on the update
@@ -84,8 +84,8 @@ On such installs, you can update Netdata using your distribution package manager
 ### If the kickstart script does not work
 
 If the above command fails, you can [reinstall
-Netdata](/packaging/installer/REINSTALL.md#one-line-installer-script-kickstartsh) to get the latest version. This
-also preserves your [configuration](/docs/configure/nodes.md) in `netdata.conf` or other files just like updating
+Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/REINSTALL.md#one-line-installer-script-kickstartsh) to get the latest version. This
+also preserves your [configuration](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md) in `netdata.conf` or other files just like updating
 normally would, though you will need to specify any installation options you used originally again.
 
 ## Docker
@@ -109,7 +109,7 @@ 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](/packaging/docker/README.md#create-a-new-netdata-agent-container) for details.
+installation instructions](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md#create-a-new-netdata-agent-container) for details.
 
 ## macOS
 
@@ -128,7 +128,7 @@ instructions](#updates-for-most-systems) to update Netdata.
 
 ## Manual installation from Git
 
-If you installed [Netdata manually from Git](/packaging/installer/methods/manual.md), you can run that installer again
+If you installed [Netdata manually from Git](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md), you can run that installer again
 to update your agent. First, run our automatic requirements installer, which works on many Linux distributions, to
 ensure your system has the dependencies necessary for new features.
 
diff --git a/packaging/installer/methods/cloud-providers.md b/packaging/installer/methods/cloud-providers.md
index bc5c9aae25..6b8fa6de1f 100644
--- a/packaging/installer/methods/cloud-providers.md
+++ b/packaging/installer/methods/cloud-providers.md
@@ -8,7 +8,7 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/packaging/instal
 
 Netdata is fully compatible with popular cloud providers like Google Cloud Platform (GCP), Amazon Web Services (AWS),
 Azure, and others. You can install Netdata on cloud instances to monitor the apps/services running there, or use
-multiple instances in a [parent-child streaming](/streaming/README.md) configuration.
+multiple instances in a [parent-child streaming](https://github.com/netdata/netdata/blob/master/streaming/README.md) configuration.
 
 In some cases, using Netdata on these cloud providers requires unique installation or configuration steps. This page
 aims to document some of those steps for popular cloud providers.
@@ -53,11 +53,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](https://github.com/netdata/netdata/blob/master/docs/Running-behind-apache.md)
+-   [Nginx](https://github.com/netdata/netdata/blob/master/docs/Running-behind-nginx.md)
+-   [Caddy](https://github.com/netdata/netdata/blob/master/docs/Running-behind-caddy.md)
+-   [HAProxy](https://github.com/netdata/netdata/blob/master/docs/Running-behind-haproxy.md)
+-   [lighttpd](https://github.com/netdata/netdata/blob/master/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/freebsd.md b/packaging/installer/methods/freebsd.md
index d1e3af2699..ea7099b367 100644
--- a/packaging/installer/methods/freebsd.md
+++ b/packaging/installer/methods/freebsd.md
@@ -66,7 +66,7 @@ You can now access the Netdata dashboard by navigating to `http://NODE:19999`, r
 
 Starting with v1.30, Netdata collects anonymous usage information by default and sends it to a self hosted PostHog instance within the Netdata infrastructure. To read
 more about the information collected and how to opt-out, check the [anonymous statistics
-page](/docs/anonymous-statistics.md).
+page](https://github.com/netdata/netdata/blob/master/docs/anonymous-statistics.md).
 
 ## Updating the Agent on FreeBSD
 If you have not passed the `--auto-update` or `-u` parameter for the installer to enable automatic updating, repeat the last step to update Netdata whenever a new version becomes available. 
diff --git a/packaging/installer/methods/kickstart.md b/packaging/installer/methods/kickstart.md
index cb2e9897c9..5eaa820201 100644
--- a/packaging/installer/methods/kickstart.md
+++ b/packaging/installer/methods/kickstart.md
@@ -18,8 +18,8 @@ This page covers detailed instructions on using and configuring the automatic on
 
 The kickstart script works on all Linux distributions and macOS environments. By default, automatic nightly updates are enabled. If you are installing on macOS, make sure to check the [install documentation for macOS](macos.md) before continuing.
 
-> If you are unsure whether you want nightly or stable releases, read the [installation guide](/packaging/installer/README.md#nightly-vs-stable-releases). 
-> If you want to turn off [automatic updates](/packaging/installer/README.md#automatic-updates), use the `--no-updates` option. You can find more installation options below.
+> If you are unsure whether you want nightly or stable releases, read the [installation guide](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#nightly-vs-stable-releases). 
+> If you want to turn off [automatic updates](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#automatic-updates), use the `--no-updates` option. You can find more installation options below.
 
 To install Netdata, run the following as your normal user:
 
@@ -79,7 +79,7 @@ The `kickstart.sh` script accepts a number of optional parameters to control how
 - `--reinstall-clean`: Performs an uninstall of Netdata and clean installation.
 - `--local-build-options`: Specify additional options to pass to the installer code when building locally. Only valid if `--build-only` is also specified.
 - `--static-install-options`: Specify additional options to pass to the static installer code. Only valid if --static-only is also specified.
-- `--prepare-offline-install-source`: Instead of insallling the agent, prepare a directory that can be used to install on another system without needing to download anything. See our [offline installation documentation](/packaging/installer/methods/offline.md) for more info.
+- `--prepare-offline-install-source`: Instead of insallling the agent, prepare a directory that can be used to install on another system without needing to download anything. See our [offline installation documentation](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/offline.md) for more info.
 
 Additionally, the following environment variables may be used to further customize how the script runs (most users
 should not need to use special values for any of these):
@@ -94,9 +94,9 @@ should not need to use special values for any of these):
 
 ### Connect node to Netdata Cloud during installation
 
-The `kickstart.sh` script accepts additional parameters to automatically [connect](/claim/README.md) your node to Netdata Cloud immediately after installation. 
+The `kickstart.sh` script accepts additional parameters to automatically [connect](https://github.com/netdata/netdata/blob/master/claim/README.md) your node to Netdata Cloud immediately after installation. 
 
-> Note: You either need to run the command with root privileges or run it with the user that is running the agent.  More details: [Connect an agent without root privileges](/claim/README.md#connect-an-agent-without-root-privileges) section.
+> Note: You either need to run the command with root privileges or run it with the user that is running the agent.  More details: [Connect an agent without root privileges](https://github.com/netdata/netdata/blob/master/claim/README.md#connect-an-agent-without-root-privileges) section.
 
 To automatically claim nodes after installation: 
 
@@ -109,7 +109,7 @@ To automatically claim nodes after installation:
   after the install.
 - `--claim-rooms`: Specify a comma-separated list of tokens for each War Room this node should appear in.
 - `--claim-proxy`: Specify a proxy to use when connecting to the cloud in the form of `http://[user:pass@]host:ip` for an HTTP(S) proxy.
-  See [connecting through a proxy](/claim/README.md#connect-through-a-proxy) for details.
+  See [connecting through a proxy](https://github.com/netdata/netdata/blob/master/claim/README.md#connect-through-a-proxy) for details.
 - `--claim-url`: Specify a URL to use when connecting to the cloud. Defaults to `https://api.netdata.cloud`.
 
 For example:
@@ -163,10 +163,10 @@ If the script is valid, this command will return `OK, VALID`.
 
 ## What's next?
 
-When you're finished with installation, check out our [single-node](/docs/quickstart/single-node.md) or
-[infrast