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

1 files changed, 6 insertions, 6 deletions

diff --git a/docs/privacy-policy.md b/docs/privacy-policy.md
index e46d783ed2..4d7a7e526e 100644
--- a/docs/privacy-policy.md
+++ b/docs/privacy-policy.md
@@ -37,22 +37,22 @@ The menu lists the Netdata servers you have visited. For example, when you jump
 (like the currently viewed charts, the current zoom and pan operations on the charts, etc.) are propagated to the new server, so that the new dashboard will come with exactly the 
 same view. The global registry keeps track of 4 entities:
 
-1. **machines**: i.e. the netdata installations (a random GUID generated by each netdata the first time it starts; we call this **machine_guid**)
+1. **machines**: i.e. the Netdata installations (a random GUID generated by each Netdata the first time it starts; we call this **machine_guid**)
 
-  For each netdata installation (each `machine_guid`) the registry keeps track of the different URLs it is accessed.
+  For each Netdata installation (each `machine_guid`) the registry keeps track of the different URLs it is accessed.
 
-2. **persons**: i.e. the web browsers accessing the netdata installations (a random GUID generated by the registry the first time it sees a new web browser; we call this **person_guid**)
+2. **persons**: i.e. the web browsers accessing the Netdata installations (a random GUID generated by the registry the first time it sees a new web browser; we call this **person_guid**)
 
-  For each person, the registry keeps track of the netdata installations it has accessed and their URLs. 
+  For each person, the registry keeps track of the Netdata installations it has accessed and their URLs. 
 
-3. **URLs** of netdata installations (as seen by the web browsers)
+3. **URLs** of Netdata installations (as seen by the web browsers)
 
   For each URL, the registry keeps the URL and nothing more. Each URL is linked to *persons* and *machines*. The only way to find a URL is to know its **machine_guid** or have a **person_guid** it is linked to it.
 
 4. **accounts**: i.e. the information used to sign-in via one of the available sign-in methods. Depending on the method, this may include an email, an email and a profile picture.
 
 For *persons*/*accounts* and *machines*, the registry keeps links to *URLs*, each link with 2 timestamps (first time seen, last time seen) and a counter (number of times it has been seen).
-*machines*, *persons*, and timestamps are stored in the netdata registry regardless of whether you sign in or not.
+*machines*, *persons*, and timestamps are stored in the Netdata registry regardless of whether you sign in or not.
 
 If sending this information is against your policies, you can [run your own registry](../registry/#run-your-own-registry). 
 Note that ND versions with the 'Sign in' feature of the ND Cloud do not use the global registry.