Change "netdata" to "Netdata" in all docs (#6621)

* First pass of changing netdata to Netdata

* Second pass of netdata -> Netdata

* Starting work on netdata with no whitespace after

* Pass for netdata with no whitespace at the end

* Pass for netdata with no whitespace at the front

6 files changed, 15 insertions, 15 deletions

diff --git a/libnetdata/README.md b/libnetdata/README.md
index 9892d67030..2dd093ed54 100644
--- a/libnetdata/README.md
+++ b/libnetdata/README.md
@@ -1,6 +1,6 @@
 # libnetdata
 
-`libnetdata` is a collection of library code that is used by all netdata `C` programs.
+`libnetdata` is a collection of library code that is used by all Netdata `C` programs.
 
 
 
diff --git a/libnetdata/adaptive_resortable_list/README.md b/libnetdata/adaptive_resortable_list/README.md
index ab0d7c5a87..23c036bb55 100644
--- a/libnetdata/adaptive_resortable_list/README.md
+++ b/libnetdata/adaptive_resortable_list/README.md
@@ -1,10 +1,10 @@
 
 # Adaptive Re-sortable List (ARL)
 
-This library allows netdata to read a series of `name - value` pairs
+This library allows Netdata to read a series of `name - value` pairs
 in the **fastest possible way**.
 
-ARLs are used all over netdata, as they are the most
+ARLs are used all over Netdata, as they are the most
 CPU utilization efficient way to process `/proc` files. They are used to
 process both vertical (csv like) and horizontal (one pair per line) `name - value` pairs.
 
@@ -82,7 +82,7 @@ test|code|string comparison|number parsing|duration
 
 Compared to unoptimized code (test No 1: 4.6sec):
  
- - before ARL netdata was using test No **7** with hashing and a custom `str2ull()` to achieve 602ms.
+ - before ARL Netdata was using test No **7** with hashing and a custom `str2ull()` to achieve 602ms.
  - the current ARL implementation is test No **9** that needs only 157ms (29 times faster vs unoptimized code, about 4 times faster vs optimized code).
 
 [Check the source code of this test](../../tests/profile/benchmark-value-pairs.c).
diff --git a/libnetdata/config/README.md b/libnetdata/config/README.md
index f0a27d9518..4fecef42c4 100644
--- a/libnetdata/config/README.md
+++ b/libnetdata/config/README.md
@@ -1,6 +1,6 @@
-# netdata ini config files
+# Netdata ini config files
 
-Configuration files `netdata.conf` and `stream.conf` are netdata ini files.
+Configuration files `netdata.conf` and `stream.conf` are Netdata ini files.
 
 ## Motivation
 
@@ -17,7 +17,7 @@ developers and the users.
 
 So, we did this:
 
-1. No configuration is required to run netdata
+1. No configuration is required to run Netdata
 2. There are plenty of options to tweak
 3. There is minimal documentation (or no at all)
 
@@ -35,9 +35,9 @@ file, the default is used. The lookup is made using B-Trees and hashes
 settings can be `my super duper setting that once set to yes, will turn the world upside down = no`
 - so goodbye to most of the documentation involved.
 
-Next, netdata can generate a valid configuration for the user to edit.
+Next, Netdata can generate a valid configuration for the user to edit.
 No need to remember anything or copy and paste settings. Just get the
-configuration from the server (`/netdata.conf` on your netdata server),
+configuration from the server (`/netdata.conf` on your Netdata server),
 edit it and save it.
 
 Last, what about options you believe you have set, but you misspelled?
diff --git a/libnetdata/procfile/README.md b/libnetdata/procfile/README.md
index 7037dc4ee8..de989ccb3d 100644
--- a/libnetdata/procfile/README.md
+++ b/libnetdata/procfile/README.md
@@ -58,6 +58,6 @@ When the caller exits:
 To achieve this kind of performance, the library tries to work in batches so that the code
 and the data are inside the processor's caches.
 
-This library is extensively used in netdata and its plugins.
+This library is extensively used in Netdata and its plugins.
 
 [![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Flibnetdata%2Fprocfile%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()
diff --git a/libnetdata/simple_pattern/README.md b/libnetdata/simple_pattern/README.md
index 79a7131689..12a3cc3291 100644
--- a/libnetdata/simple_pattern/README.md
+++ b/libnetdata/simple_pattern/README.md
@@ -1,9 +1,9 @@
-## netdata simple patterns
+## Netdata simple patterns
 
 Unix prefers regular expressions. But they are just too hard, too cryptic
 to use, write and understand.
 
-So, netdata supports **simple patterns**.
+So, Netdata supports **simple patterns**.
 
 Simple patterns are a space separated list of words, that can have `*`
 as a wildcard. Each world may use any number of `*`. Simple patterns
@@ -16,7 +16,7 @@ Simple patterns are quite powerful: `pattern = *foobar* !foo* !*bar *`
 matches everything containing `foobar`, except strings that start
 with `foo` or end with `bar`.
 
-You can use the netdata command line to check simple patterns,
+You can use the Netdata command line to check simple patterns,
 like this:
 
 ```sh
@@ -30,7 +30,7 @@ RESULT: NOT MATCHED - pattern '*foobar* !foo* !*bar *' does not match 'hello wor
 RESULT: MATCHED - pattern '*foobar* !foo* !*bar *' matches 'hello world foobar'
 ```
 
-netdata stops processing to the first positive or negative match
+Netdata stops processing to the first positive or negative match
 (left to right). If it is not matched by either positive or negative
 patterns, it is denied at the end.
 
diff --git a/libnetdata/storage_number/README.md b/libnetdata/storage_number/README.md
index 5c2c0b074a..df058a2618 100644
--- a/libnetdata/storage_number/README.md
+++ b/libnetdata/storage_number/README.md
@@ -1,4 +1,4 @@
-# netdata storage number
+# Netdata storage number
 
 Although `netdata` does all its calculations using `long double`, it stores all values using
 a **custom-made 32-bit number**.