Fix typos (#7375)

9 files changed, 16 insertions, 16 deletions

diff --git a/docs/Running-behind-haproxy.md b/docs/Running-behind-haproxy.md
index cf411b9f86..a50cccb425 100644
--- a/docs/Running-behind-haproxy.md
+++ b/docs/Running-behind-haproxy.md
@@ -26,7 +26,7 @@ A simple example where the base URL, say <http://example.com>, is used with no s
 
 ### Frontend
 
-Create a frontend to recieve the request.
+Create a frontend to receive the request.
 
 ```conf
 frontend http_frontend
@@ -80,7 +80,7 @@ frontend http_frontend
 
 ### Backend
 
-Same as simple example, expept remove `/netdata/` with regex.
+Same as simple example, except remove `/netdata/` with regex.
 
 ```conf
 backend netdata_backend
diff --git a/docs/configuration-guide.md b/docs/configuration-guide.md
index abb79c65ba..a6a1c701bb 100644
--- a/docs/configuration-guide.md
+++ b/docs/configuration-guide.md
@@ -82,7 +82,7 @@ To modify how the alarm gets triggered, we suggest that you go through the guide
 
 ##### Receive notifications using my preferred method
 
-You only need to configure `health_alarm_notify.conf`. To learn how to do it, read first [alarm notifications](../health/notifications/#netdata-alarm-notifications) and then open the submenu `Supported Notifications` under `Alarm notifications` in the documentation to find the specific page on your prefered notification method. 
+You only need to configure `health_alarm_notify.conf`. To learn how to do it, read first [alarm notifications](../health/notifications/#netdata-alarm-notifications) and then open the submenu `Supported Notifications` under `Alarm notifications` in the documentation to find the specific page on your preferred notification method. 
 
 ### Make security-related customizations
 
diff --git a/docs/contributing/contributing-documentation.md b/docs/contributing/contributing-documentation.md
index ebdffdbf6d..57e4fe972c 100644
--- a/docs/contributing/contributing-documentation.md
+++ b/docs/contributing/contributing-documentation.md
@@ -57,7 +57,7 @@ Make changes as you see fit.
 You can use the `Preview changes` button to ensure your Markdown syntax is working properly.
 
 Under the `Propose file change` header, write in a descriptive title for your requested change. 
-Beneath that, add a concise descrition of what you've changed and why you think it's important. Then, click the `Propose file change` button. 
+Beneath that, add a concise description of what you've changed and why you think it's important. Then, click the `Propose file change` button. 
 
 After you've hit that button, 
 jump down to our instructions on [pull requests and cleanup](#pull-requests-and-final-steps) for your next steps. 
@@ -95,7 +95,7 @@ corresponds to. Many sub-folders contain a `README.md` file,
 which is then used to populate the documentation about that feature/component of Netdata.
 
 For example, the file at `packaging/installer/README.md` becomes `https://docs.netdata.cloud/packaging/installer/` 
-and is our installation documentation. By co-locating it with quick-start installtion code, 
+and is our installation documentation. By co-locating it with quick-start installation code, 
 we ensure documentation is always tightly knit with the functions it describes.
 
 You might find other `.md` files within these directories. The `packaging/installer/` folder also contains `UPDATE.md` 
@@ -112,7 +112,7 @@ a direct relationship to a specific component of Netdata. It's where we house ou
 guide](../../docs/getting-started.md), guides on [running Netdata behind Nginx](../../docs/Running-behind-nginx.md), and
 more.
 
-If the documentation you're working on doesn't have a direct relaionship to a component of Netdata, 
+If the documentation you're working on doesn't have a direct relationship to a component of Netdata, 
 it can be placed in this `docs/` folder.
 
 ### Make your edits
@@ -141,7 +141,7 @@ Follow the [Python installation instructions](https://www.python.org/downloads/)
 
 Use `pip`, which was installed alongside Python, to install `mkdocs` and `mkdocs-material`. 
 Your operating system might force you to use `pip2` or `pip3` instead, 
-dependin on which version of Python you have installed.
+depending on which version of Python you have installed.
 
 ```bash
 pip install mkdocs mkdocs-material
diff --git a/docs/generator/checklinks.sh b/docs/generator/checklinks.sh
index 6773839deb..ab5964312a 100755
--- a/docs/generator/checklinks.sh
+++ b/docs/generator/checklinks.sh
@@ -18,7 +18,7 @@ printhelp () {
 	-f Just check the passed md file
 	General Options:
 	 -x Execute commands. By default the script runs in test mode with no files changed by the script (results and fixes are just shown). Use -x to have it apply the changes.
-	 -u trys to follow URLs using curl
+	 -u Tries to follow URLs using curl
 	 -v Outputs debugging messages
 	By default, nothing is actually checked. The following options tell it what to check:
 	 -a Check all link types
diff --git a/docs/getting-started.md b/docs/getting-started.md
index eca94df337..9c7f1353dd 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -4,7 +4,7 @@ Thanks for trying Netdata! In this getting started guide, we'll quickly walk you
 after getting Netdata installed.
 
 Netdata can collect thousands of metrics in real-time without any configuration, but there are some valuable things to
-know to get the most of out Netdata based on your needs.
+know to get the most out of Netdata based on your needs.
 
 We'll skip right into some technical details, so if you're brand-new to monitoring the health and performance of systems
 and applications, our [**step-by-step tutorial**](step-by-step/step-00.md) might be a better fit.
@@ -147,7 +147,7 @@ Edit your `/etc/netdata/netdata.conf` file and set the following:
 ```
 
 If you want to keep health monitoring enabled, but turn email notifications off, edit your `health_alarm_notify.conf`
-file with `edit-config`, or with your the text editor of your choice:
+file with `edit-config`, or with the text editor of your choice:
 
 ```bash
 sudo /etc/netdata/edit-config health_alarm_notify.conf
diff --git a/docs/netdata-security.md b/docs/netdata-security.md
index 50d91df04a..c49ab7b8d8 100644
--- a/docs/netdata-security.md
+++ b/docs/netdata-security.md
@@ -86,7 +86,7 @@ In Netdata v1.9+ there is also access list support, like this:
 	allow connections from = localhost 10.* 192.168.*
 ```
 
-#### Fine-grainined access control
+#### Fine-grained access control
 
 The access list support allows filtering of all incoming connections, by specific IP addresses, ranges
 or validated DNS lookups. Only connections that match an entry on the list will be allowed:
@@ -97,7 +97,7 @@ or validated DNS lookups. Only connections that match an entry on the list will
 ```
 
 Connections from the IP addresses are allowed if the connection IP matches one of the patterns given.
-The alias localhost is alway checked against 127.0.0.1, any other symbolic names need to resolve in
+The alias localhost is always checked against 127.0.0.1, any other symbolic names need to resolve in
 both directions using DNS. In the above example the IP address of `homeip.net` must reverse DNS resolve
 to the incoming IP address and a DNS lookup on `homeip.net` must return the incoming IP address as
 one of the resolved addresses.
@@ -191,7 +191,7 @@ Of course, there are many more methods you could use to protect Netdata:
 
 The default configuration uses a public registry under registry.my-netdata.io (more information about the registry here: [mynetdata-menu-item](../registry/) ). Please be aware that if you use that public registry, you submit the following information to a third party server: 
 
--   The url where you open the web-ui in the browser (via http request referer)
+-   The url where you open the web-ui in the browser (via http request referrer)
 -   The hostnames of the Netdata servers
 
 If sending this information to the central Netdata registry violates your security policies, you can configure Netdat to [run your own registry](../registry/#run-your-own-registry).
diff --git a/docs/privacy-policy.md b/docs/privacy-policy.md
index 4f1c74598a..9ac0bfeccd 100644
--- a/docs/privacy-policy.md
+++ b/docs/privacy-policy.md
@@ -74,7 +74,7 @@ The statistics calculated from this information are used for:
 
 2.  **Usage statistics**, to help us focus on the parts of Netdata that are used the most, or help us identify the extend our development decisions influence the community.
 
-To opt-out from sending anonymous statistics, you can create reate a file called `.opt-out-from-anonymous-statistics` under the user configuration directory (usually `/etc/netdata`).
+To opt-out from sending anonymous statistics, you can create a file called `.opt-out-from-anonymous-statistics` under the user configuration directory (usually `/etc/netdata`).
 
 Emails and Newsletters: When you sign up to receive updates from Netdata or otherwise subscribe to one of our mailing lists, you will be asked to provide some personal information. ND collects and uses this personal information pursuant to its legitimate interest in providing news and updates to, and collaborating with, its supporters and volunteers.
 
diff --git a/docs/what-is-netdata.md b/docs/what-is-netdata.md
index e9b4d1598f..e3e2bf15c2 100644
--- a/docs/what-is-netdata.md
+++ b/docs/what-is-netdata.md
@@ -103,7 +103,7 @@ The result is a highly efficient, low latency system, supporting multiple reader
 ## Infographic
 
 This is a high level overview of Netdata feature set and architecture.
-Click it to to interact with it (it has direct links to documentation).
+Click it to interact with it (it has direct links to documentation).
 
 [![image](https://user-images.githubusercontent.com/43294513/60951037-8ba5d180-a2f8-11e9-906e-e27356f168bc.png)](https://my-netdata.io/infographic.html)
 
diff --git a/docs/why-netdata/meaningful-presentation.md b/docs/why-netdata/meaningful-presentation.md
index 2623d152af..803d33941f 100644
--- a/docs/why-netdata/meaningful-presentation.md
+++ b/docs/why-netdata/meaningful-presentation.md
@@ -26,7 +26,7 @@ The monitoring industry believes there is this "IT Operations Hero", a person co
 
 1.  Has a deep understanding of IT architectures and is a skillful SysAdmin.
 2.  Is a superb Network Administrator (can even read and understand the Linux kernel networking stack).
-3.  Is a exceptional database administrator.
+3.  Is an exceptional database administrator.
 4.  Is fluent in software engineering, capable of understanding the internal workings of applications.
 5.  Masters Data Science, statistical algorithms and is fluent in writing advanced mathematical queries to reveal the meaning of metrics.