summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorJosh Soref <2119212+jsoref@users.noreply.github.com>2021-12-22 10:14:10 -0500
committerGitHub <noreply@github.com>2021-12-22 18:14:10 +0300
commite7b6fe7f61ac72db2b221d3215aa616ddd766238 (patch)
tree3b020b08a5ad406ba96aca3a7e60a6c247add70f /docs
parent5049de8f7a132205b32f2c523998f93cbbfc0481 (diff)
Spelling (#10976)
Co-authored-by: Tina Luedtke <kickoke@users.noreply.github.com> Co-authored-by: Josh Soref <jsoref@users.noreply.github.com> Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Diffstat (limited to 'docs')
-rw-r--r--docs/anonymous-statistics.md2
-rw-r--r--docs/guides/monitor/kubernetes-k8s-netdata.md2
-rw-r--r--docs/guides/monitor/lamp-stack.md2
-rw-r--r--docs/guides/monitor/statsd.md4
-rw-r--r--docs/guides/python-collector.md2
5 files changed, 6 insertions, 6 deletions
diff --git a/docs/anonymous-statistics.md b/docs/anonymous-statistics.md
index 5c82e05372..82c018e1b3 100644
--- a/docs/anonymous-statistics.md
+++ b/docs/anonymous-statistics.md
@@ -30,7 +30,7 @@ You can opt-out from sending anonymous statistics to Netdata through three diffe
## Agent Dashboard - PostHog JavaScript
-When you kick off an Agent dashboard session by visiting `http://NODE:19999`, Netdata will initialiszes a PostHog session and masks various event attributes.
+When you kick off an Agent dashboard session by visiting `http://NODE:19999`, Netdata initializes a PostHog session and masks various event attributes.
_Note_: You can see the relevant code in the [dashboard repository](https://github.com/netdata/dashboard/blob/master/src/domains/global/sagas.ts#L107) where the `window.posthog.register()` call is made.
diff --git a/docs/guides/monitor/kubernetes-k8s-netdata.md b/docs/guides/monitor/kubernetes-k8s-netdata.md
index 5d4886e682..bd893ede6d 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 38b9d0bef3..fbf9ae0b4e 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/statsd.md b/docs/guides/monitor/statsd.md
index e4f04c5752..214b488f20 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/python-collector.md b/docs/guides/python-collector.md
index b8facd9f02..c3784194ab 100644
--- a/docs/guides/python-collector.md
+++ b/docs/guides/python-collector.md
@@ -433,7 +433,7 @@ weather_station_1:
name: 'Greece'
endpoint: 'https://endpoint_1.com'
port: 67
- type: 'celcius'
+ type: 'celsius'
weather_station_2:
name: 'Florida USA'
endpoint: 'https://endpoint_2.com'