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

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

5 files changed, 14 insertions, 14 deletions

diff --git a/health/notifications/custom/README.md b/health/notifications/custom/README.md
index 525503339b..df8f88e403 100644
--- a/health/notifications/custom/README.md
+++ b/health/notifications/custom/README.md
@@ -13,8 +13,8 @@ learn_autogeneration_metadata: "{'part_of_cloud': False, 'part_of_agent': True}"
 Netdata allows you to send custom notifications to any endpoint you choose.
 
 To configure custom notifications, you will need to customize `health_alarm_notify.conf`. Open the file for editing
-using [`edit-config`](/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) from the [Netdata config
-directory](/docs/configure/nodes.md#the-netdata-config-directory), which is typically at `/etc/netdata`.
+using [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) from the [Netdata config
+directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#the-netdata-config-directory), which is typically at `/etc/netdata`.
 
 You can look at the other senders in `/usr/libexec/netdata/plugins.d/alarm-notify.sh` for examples of how to modify the `custom_sender()` function in `health_alarm_notify.conf`.
 
diff --git a/health/notifications/gotify/README.md b/health/notifications/gotify/README.md
index e6158ccd56..d01502b65a 100644
--- a/health/notifications/gotify/README.md
+++ b/health/notifications/gotify/README.md
@@ -25,7 +25,7 @@ You can generate a new token in the Gotify Web UI.
 To set up Gotify in Netdata: 
 
 1. Switch to your [config
-directory](/docs/configure/nodes.md) and edit the file `health_alarm_notify.conf` using the edit config script.
+directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md) and edit the file `health_alarm_notify.conf` using the edit config script.
  
    ```bash
    ./edit-config health_alarm_notify.conf
diff --git a/health/notifications/opsgenie/README.md b/health/notifications/opsgenie/README.md
index 2ee353003f..20f14b396a 100644
--- a/health/notifications/opsgenie/README.md
+++ b/health/notifications/opsgenie/README.md
@@ -17,9 +17,9 @@ incidents.
 
 The first step is to create a [Netdata integration](https://docs.opsgenie.com/docs/api-integration) in the
 [Opsgenie](https://www.atlassian.com/software/opsgenie) dashboard. After this, you need to edit
-`health_alarm_notify.conf` on your system, by running the following from your [config
-directory](/docs/configure/nodes.md):
- 
+`health_alarm_notify.conf` on your system, by running the following from
+your [config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md):
+
 ```bash
 ./edit-config health_alarm_notify.conf
 ```
@@ -60,7 +60,7 @@ message:
 2020-09-03 23:07:00: alarm-notify.sh: ERROR: failed to send opsgenie notification for: hades test.chart.test_alarm is CRITICAL, with HTTP error code 401.
 ```
 
-You can find more details about the Opsgenie error codes in their [response
-docs](https://docs.opsgenie.com/docs/response).
+You can find more details about the Opsgenie error codes in
+their [response docs](https://docs.opsgenie.com/docs/response).
 
 
diff --git a/health/notifications/pagerduty/README.md b/health/notifications/pagerduty/README.md
index f52578cf38..c6190e83f7 100644
--- a/health/notifications/pagerduty/README.md
+++ b/health/notifications/pagerduty/README.md
@@ -18,7 +18,7 @@ resolution times.
 
 ## What you need to get started
 
-- An installation of the open-source [Netdata](/docs/get-started.mdx) monitoring agent.
+- An installation of the open-source [Netdata](https://github.com/netdata/netdata/blob/master/docs/get-started.mdx) monitoring agent.
 - An installation of the [PagerDuty agent](https://www.pagerduty.com/docs/guides/agent-install-guide/) on the node
   running Netdata.
 - A PagerDuty `Generic API` service using either the `Events API v2` or `Events API v1`.
@@ -29,8 +29,8 @@ resolution times.
 to PagerDuty. Click **Use our API directly** and select either `Events API v2` or `Events API v1`. Once you finish
 creating the service, click on the **Integrations** tab to find your **Integration Key**.
 
-Navigate to the [Netdata config directory](/docs/configure/nodes.md#the-netdata-config-directory) and use
-[`edit-config`](/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) to open
+Navigate to the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#the-netdata-config-directory) and use
+[`edit-config`](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) to open
 `health_alarm_notify.conf`.
 
 ```bash
@@ -63,5 +63,5 @@ sudo su -s /bin/bash netdata
 Aside from the three values set in `health_alarm_notify.conf`, there is no further configuration required to send alert
 notifications to PagerDuty.
 
-To configure individual alarms, read our [alert configuration](/docs/monitor/configure-alarms.md) doc or
-the [health entity reference](/health/REFERENCE.md) doc.
+To configure individual alarms, read our [alert configuration](https://github.com/netdata/netdata/blob/master/docs/monitor/configure-alarms.md) doc or
+the [health entity reference](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md) doc.
diff --git a/health/notifications/stackpulse/README.md b/health/notifications/stackpulse/README.md
index da2a084a71..25266e8225 100644
--- a/health/notifications/stackpulse/README.md
+++ b/health/notifications/stackpulse/README.md
@@ -44,7 +44,7 @@ STACKPULSE_WEBHOOK="https://hooks.stackpulse.io/v1/webhooks/YOUR_UNIQUE_ID"
 ```
 
 4.  Now restart Netdata using `sudo systemctl restart netdata`, or the [appropriate
-    method](/docs/configure/start-stop-restart.md) for your system. When your node creates an alarm, you can see the
+    method](https://github.com/netdata/netdata/blob/master/docs/configure/start-stop-restart.md) for your system. When your node creates an alarm, you can see the
     associated notification on your StackPulse Administration Portal 
 
 ## React to alarms with playbooks