Merging upstream version 1.33.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

5 files changed, 7 insertions, 7 deletions

diff --git a/docs/guides/monitor/kubernetes-k8s-netdata.md b/docs/guides/monitor/kubernetes-k8s-netdata.md
index 5d4886e68..bd893ede6 100644
--- a/docs/guides/monitor/kubernetes-k8s-netdata.md
+++ b/docs/guides/monitor/kubernetes-k8s-netdata.md
@@ -1,6 +1,6 @@
 <!--
 title: "Kubernetes monitoring with Netdata: Overview and visualizations"
-description: "Learn how to navigate Netdata's Kubernetes monitoring features for visualizing the health and performance of a Kubernetes cluster with per-second granulrity."
+description: "Learn how to navigate Netdata's Kubernetes monitoring features for visualizing the health and performance of a Kubernetes cluster with per-second granularity."
 image: /img/seo/guides/monitor/kubernetes-k8s-netdata.png
 author: "Joel Hans"
 author_title: "Editorial Director, Technical & Educational Resources"
diff --git a/docs/guides/monitor/lamp-stack.md b/docs/guides/monitor/lamp-stack.md
index 38b9d0bef..fbf9ae0b4 100644
--- a/docs/guides/monitor/lamp-stack.md
+++ b/docs/guides/monitor/lamp-stack.md
@@ -89,7 +89,7 @@ metrics](https://httpd.apache.org/docs/2.4/mod/mod_status.html), which is just _
 
 The Netdata Agent also comes with a [web log
 collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/weblog), which reads Apache's access
-log file, procesess each line, and converts them into per-second metrics. On Debian systems, it reads the file at
+log file, processes each line, and converts them into per-second metrics. On Debian systems, it reads the file at
 `/var/log/apache2/access.log`.
 
 At installation, the Netdata Agent adds itself to the [`adm`
diff --git a/docs/guides/monitor/pi-hole-raspberry-pi.md b/docs/guides/monitor/pi-hole-raspberry-pi.md
index dc5e0b314..4147ca976 100644
--- a/docs/guides/monitor/pi-hole-raspberry-pi.md
+++ b/docs/guides/monitor/pi-hole-raspberry-pi.md
@@ -100,7 +100,7 @@ part of your system might affect another.
 action](https://user-images.githubusercontent.com/1153921/80827388-b9fee100-8b98-11ea-8f60-0d7824667cd3.gif)
 
 If you're completely new to Netdata, look at our [step-by-step guide](/docs/guides/step-by-step/step-00.md) for a
-walkthrough of all its features. For a more expedited tour, see the [get started guide](/docs/getting-started.md).
+walkthrough of all its features. For a more expedited tour, see the [get started guide](/docs/get-started.md).
 
 ### Enable temperature sensor monitoring
 
@@ -137,7 +137,7 @@ more than 256.
 ```
 
 Use our [database sizing
-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)
 and [guide on storing historical metrics](/docs/guides/longer-metrics-storage.md) to help you determine the right
 setting for your Raspberry Pi.
 
diff --git a/docs/guides/monitor/statsd.md b/docs/guides/monitor/statsd.md
index e4f04c575..214b488f2 100644
--- a/docs/guides/monitor/statsd.md
+++ b/docs/guides/monitor/statsd.md
@@ -266,9 +266,9 @@ The `info` field supports `html`, embedding useful links and instructions in the
 
 ## Vendoring a new collector
 
-After all this hussle, not only did we illustrate how to visualize any data source in Netdata using the StatsD protocol, but we have also created a new collector in the process.
+While we learned how to visualize any data source in Netdata using the StatsD protocol, we have also created a new collector.
 
-While using the same underlying collector-StatsD-every new `myapp.conf` file will in essence create a new data source and dashboard section for Netdata. While Netdata will load all the configuration files by default, it will **not** create dashboard sections or charts, unless it start receiving data for that particular data source. This means that we can now share our collector with the rest of the Netdata community. 
+As long as you use the same underlying collector, every new `myapp.conf` file will create a new data source and dashboard section for Netdata. Netdata loads all the configuration files by default, but it will **not** create dashboard sections or charts, unless it starts receiving data for that particular data source. This means that we can now share our collector with the rest of the Netdata community. 
 
 If you want to contribute or you need any help in developing your collector, we have a whole [Forum Category](https://community.netdata.cloud/c/agent-development/9) dedicated to contributing to the Netdata Agent.
 
diff --git a/docs/guides/monitor/stop-notifications-alarms.md b/docs/guides/monitor/stop-notifications-alarms.md
index 587880ab1..ad054d5c7 100644
--- a/docs/guides/monitor/stop-notifications-alarms.md
+++ b/docs/guides/monitor/stop-notifications-alarms.md
@@ -80,7 +80,7 @@ You can add `to: silent` to any alarm you'd rather not bother you with notificat
 You should now know the fundamentals behind silencing any individual alarm in Netdata.
 
 To learn about _all_ of Netdata's health configuration possibilities, visit the [health reference
-guide](/health/REFERENCE.md), or check out other [tutorials on health monitoring](/health/README.md#tutorials).
+guide](/health/REFERENCE.md), or check out other [tutorials on health monitoring](/health/README.md#guides).
 
 Or, take better control over how you get notified about alarms via the [notification
 system](/health/notifications/README.md).