summaryrefslogtreecommitdiffstats
path: root/docs/monitor
diff options
context:
space:
mode:
Diffstat (limited to 'docs/monitor')
-rw-r--r--docs/monitor/configure-alarms.md2
-rw-r--r--docs/monitor/enable-notifications.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/monitor/configure-alarms.md b/docs/monitor/configure-alarms.md
index 2a977955b..563e61560 100644
--- a/docs/monitor/configure-alarms.md
+++ b/docs/monitor/configure-alarms.md
@@ -117,7 +117,7 @@ Let's look into each of the lines to see how they create a working health entity
- `every`: How often to perform the `lookup` calculation to decide whether or not to trigger this alarm.
- `warn`/`crit`: The value at which Netdata should trigger a warning or critical alarm. This example uses simple
syntax, but most pre-configured health entities use
- [hysteresis](/health/REFERENCE.md#special-usage-of-the-conditional-operator) to avoid superfluous notifications.
+ [hysteresis](/health/REFERENCE.md#special-use-of-the-conditional-operator) to avoid superfluous notifications.
- `info`: A description of the alarm, which will appear in the dashboard and notifications.
In human-readable format:
diff --git a/docs/monitor/enable-notifications.md b/docs/monitor/enable-notifications.md
index e5b5a6f26..d0ff04d99 100644
--- a/docs/monitor/enable-notifications.md
+++ b/docs/monitor/enable-notifications.md
@@ -94,7 +94,7 @@ want to see alarm notifications from Netdata. Click the green **Add to Slack** b
On the following page, you'll receive a **Webhook URL**. That's what you'll need to configure Netdata, so keep it handy.
-Navigate to your [Netdata config directory](/docs/configure/nodes.md#netdata-config-directory) and use `edit-config` to
+Navigate to your [Netdata config directory](/docs/configure/nodes.md#the-netdata-config-directory) and use `edit-config` to
open the `health_alarm_notify.conf` file:
```bash