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

19 files changed, 53 insertions, 55 deletions

diff --git a/health/README.md b/health/README.md
index 345f7fc70d..a03c7eec7e 100644
--- a/health/README.md
+++ b/health/README.md
@@ -1,9 +1,9 @@
 # Health monitoring
 
-Each netdata node runs an independent thread evaluating health monitoring checks.
+Each Netdata node runs an independent thread evaluating health monitoring checks.
 This thread has lock free access to the database, so that it can operate as a watchdog.
 
-Health checks (alarms) are attached to netdata charts, allowing netdata to automatically
+Health checks (alarms) are attached to Netdata charts, allowing Netdata to automatically
 activate an alarm as soon as a chart is created. This is very important for
 netdata, since many charts are dynamically created during runtime (for example, the
 chart tracking network interface packet drops, is automatically created on the first
@@ -20,15 +20,15 @@ use expressions combining the latest value of any number of metrics.
 
 ## Health configuration reference
 
-Stock netdata health configuration is in `/usr/lib/netdata/conf.d/health.d`.
+Stock Netdata health configuration is in `/usr/lib/netdata/conf.d/health.d`.
 These files can be overwritten by copying them and editing them in `/etc/netdata/health.d`
 (run `/etc/netdata/edit-config` to edit them).
 
 In `/etc/netdata/health.d` you can also put any number of files (in any number of sub-directories)
-with a suffix `.conf` to have them processed by netdata.
+with a suffix `.conf` to have them processed by Netdata.
 
-Health configuration can be reloaded at any time, without restarting netdata.
-Just send netdata the SIGUSR2 signal, like this:
+Health configuration can be reloaded at any time, without restarting Netdata.
+Just send Netdata the SIGUSR2 signal, like this:
 
 ```sh
 killall -USR2 netdata
@@ -50,7 +50,7 @@ The only difference is the label `alarm` or `template`.
 Netdata supports overriding **templates** with **alarms**.
 For example, when a template is defined for a set of charts, an alarm with exactly the
 same name attached to the same chart the template matches, will have higher precedence
-(i.e. netdata will use the alarm on this chart and prevent the template from being applied
+(i.e. Netdata will use the alarm on this chart and prevent the template from being applied
 to it).
 
 ### The format
@@ -135,7 +135,7 @@ hosts: server1 server2 database* !redis3 redis*
 The above says: use this alarm on all hosts named `server1`, `server2`, `database*`, and
 all `redis*` except `redis3`.
 
-This is useful when you centralize metrics from multiple hosts, to one netdata.
+This is useful when you centralize metrics from multiple hosts, to one Netdata.
 
 ---
 
@@ -187,7 +187,7 @@ Everything is the same with [badges](../web/api/badges/). In short:
 
 - `of DIMENSIONS` is optional and has to be the last parameter. Dimensions have to be separated
    by `,` or `|`. The space characters found in dimensions will be kept as-is (a few dimensions
-   have spaces in their names). This accepts netdata simple patterns and the `match-ids` and
+   have spaces in their names). This accepts Netdata simple patterns and the `match-ids` and
    `match-names` options affect the searches for dimensions.
 
 The result of the lookup will be available as `$this` and `$NAME` in expressions.
@@ -289,8 +289,8 @@ Format:
 exec: SCRIPT
 ```
 
-The default `SCRIPT` is netdata's `alarm-notify.sh`, which supports all the notifications
-methods netdata supports, including custom hooks.
+The default `SCRIPT` is Netdata's `alarm-notify.sh`, which supports all the notifications
+methods Netdata supports, including custom hooks.
 
 ---
 
@@ -373,19 +373,17 @@ For some alarms we need compare two time-frames, to detect anomalies. For exampl
 
 ### Expressions
 
-netdata has an internal [infix expression parser](../libnetdata/eval).
+Netdata has an internal [infix expression parser](../libnetdata/eval).
 This parses expressions and creates an internal structure that allows fast execution of them.
 
 These operators are supported `+`, `-`, `*`, `/`, `<`, `<=`, `<>`, `!=`, `>`, `>=`, `&&`, `||`,
 `!`, `AND`, `OR`, `NOT`. Boolean operators result in either `1` (true) or `0` (false).
 
-The conditional evaluation operator `?` is supported too. Using this operator IF-THEN-ELSE
-conditional statements can be specified. The format is: `(condition) ? (true expression) :
-(false expression)`. So, netdata will first evaluate the `condition` and based on the result
-will either evaluate `true expression` or `false expression`.
+The conditional evaluation operator `?` is supported too. Using this operator IF-THEN-ELSE conditional statements can be specified. The format is: `(condition) ? (true expression) :(false expression)`. So, Netdata will first evaluate the `condition` and based on the result will either evaluate `true expression` or `false expression`.
+
 Example: `($this > 0) ? ($avail * 2) : ($used / 2)`.
-Nested such expressions are also supported (i.e. `true expression` and `false expression` can
-contain conditional evaluations).
+
+Nested such expressions are also supported (i.e. `true expression` and `false expression` can contain conditional evaluations).
 
 Expressions also support the `abs()` function.
 
@@ -407,7 +405,7 @@ or warning thresholds.  This usage helps to avoid bogus messages resulting from
 variations in the value when it is varying regularly but staying close to the threshold
 value, without needing to delay sending messages at all.
 
-An example of such usage from the default CPU usage alarms bundled with netdata is:
+An example of such usage from the default CPU usage alarms bundled with Netdata is:
 
 ```
 warn: $this > (($status >= $WARNING)  ? (75) : (85))
@@ -491,7 +489,7 @@ Although the `alarm_variables` link shows you variables for a particular chart,
 
 Alarms can have the following statuses:
 
-  - `REMOVED` - the alarm has been deleted (this happens when a SIGUSR2 is sent to netdata
+  - `REMOVED` - the alarm has been deleted (this happens when a SIGUSR2 is sent to Netdata
      to reload health configuration)
 
   - `UNINITIALIZED` - the alarm is not initialized yet
@@ -509,7 +507,7 @@ The external script will be called for all status changes.
 
 ## Examples
 
-Check the `health/health.d/` directory for all alarms shipped with netdata.
+Check the `health/health.d/` directory for all alarms shipped with Netdata.
 
 Here are a few examples:
 
@@ -526,7 +524,7 @@ template: apache_last_collected_secs
     crit: $this > (10 * $update_every)
 ```
 
-The above checks that netdata is able to collect data from apache. In detail:
+The above checks that Netdata is able to collect data from apache. In detail:
 
 ```
 template: apache_last_collected_secs
@@ -653,12 +651,12 @@ The `lookup` line will calculate the sum of the all dropped packets in the last
 The `crit` line will issue a critical alarm if even a single packet has been dropped.
 
 Note that the drops chart does not exist if a network interface has never dropped a single packet.
-When netdata detects a dropped packet, it will add the chart and it will automatically attach this
+When Netdata detects a dropped packet, it will add the chart and it will automatically attach this
 alarm to it.
 
 ## Troubleshooting
 
-You can compile netdata with [debugging](../daemon#debugging) and then set in `netdata.conf`:
+You can compile Netdata with [debugging](../daemon#debugging) and then set in `netdata.conf`:
 
 ```
 [global]
@@ -671,7 +669,7 @@ Important: this will generate a lot of output in debug.log.
 You can find the context of charts by looking up the chart in either
 `http://your.netdata:19999/netdata.conf` or `http://your.netdata:19999/api/v1/charts`.
 
-You can find how netdata interpreted the expressions by examining the alarm at `http://your.netdata:19999/api/v1/alarms?all`. For each expression, netdata will return the expression as given in its config file, and the same expression with additional parentheses added to indicate the evaluation flow of the expression.
+You can find how Netdata interpreted the expressions by examining the alarm at `http://your.netdata:19999/api/v1/alarms?all`. For each expression, Netdata will return the expression as given in its config file, and the same expression with additional parentheses added to indicate the evaluation flow of the expression.
 
 ## Disabling health checks or silencing notifications at runtime
 
diff --git a/health/notifications/awssns/README.md b/health/notifications/awssns/README.md
index 82c7ef7a0a..7bb3487143 100644
--- a/health/notifications/awssns/README.md
+++ b/health/notifications/awssns/README.md
@@ -14,9 +14,9 @@ To get this working, you will need:
 * The Amazon Web Services CLI tools.  Most distributions provide these with the package name `awscli`.
 * An actual home directory for the user you run Netdata as, instead of just using `/` as a home directory.  Setup of this is distribution specific.  `/var/lib/netdata` is the recommended directory (because the permissions will already be correct) if you are using a dedicated user (which is how most distributions work).
 * An Amazon SNS topic to send notifications to with one or more subscribers.  The [Getting Started](https://docs.aws.amazon.com/sns/latest/dg/GettingStarted.html) section of the Amazon SNS documentation covers the basics of how to set this up.  Make note of the Topic ARN when you create the topic.
-* While not mandatory, it is highly recommended to create a dedicated IAM user on your account for netdata to send notifications.  This user needs to have programmatic access, and should only allow access to SNS.  If you're really paranoid, you can create one for each system or group of systems.
+* While not mandatory, it is highly recommended to create a dedicated IAM user on your account for Netdata to send notifications.  This user needs to have programmatic access, and should only allow access to SNS.  If you're really paranoid, you can create one for each system or group of systems.
 
-Once you have all the above, run the following command as the user netdata runs under:
+Once you have all the above, run the following command as the user Netdata runs under:
 
     aws configure
 
@@ -28,6 +28,6 @@ Notes:
 
    * Netdata's native email notification support is far better in almost all respects than it's support through Amazon SNS.  If you want email notifications, use the native support, not SNS.
     * If you need to change the notification format for SNS notifications, you can do so by specifying the format in `AWSSNS_MESSAGE_FORMAT` in the configuration.  This variable supports all the same vairiables you can use in custom notifications.
-    * While Amazon SNS supports sending differently formatted messages for different delivery methods, netdata does not currently support this functionality.
+    * While Amazon SNS supports sending differently formatted messages for different delivery methods, Netdata does not currently support this functionality.
 
 [![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%2Fhealth%2Fnotifications%2Fawssns%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()
diff --git a/health/notifications/custom/README.md b/health/notifications/custom/README.md
index eeaad8a606..80210572b2 100644
--- a/health/notifications/custom/README.md
+++ b/health/notifications/custom/README.md
@@ -46,7 +46,7 @@ Variables available to the custom_sender:
  - `${alarm_id}`           the unique id of the alarm that generated this event
  - `${event_id}`           the incremental id of the event, for this alarm id
  - `${when}`               the timestamp this event occurred
- - `${name}`               the name of the alarm, as given in netdata health.d entries
+ - `${name}`               the name of the alarm, as given in Netdata health.d entries
  - `${url_name}`           same as `${name}` but URL encoded
  - `${chart}`              the name of the chart (type.id)
  - `${url_chart}`          same as `${chart}` but URL encoded
@@ -67,7 +67,7 @@ Variables available to the custom_sender:
  - `${old_value_string}`   friendly old value (with units)
  - `${image}`              the URL of an image to represent the status of the alarm
  - `${color}`              a color in #AABBCC format for the alarm
- - `${goto_url}`           the URL the user can click to see the netdata dashboard
+ - `${goto_url}`           the URL the user can click to see the Netdata dashboard
  - `${calc_expression}`    the expression evaluated to provide the value for the alarm
  - `${calc_param_values}`  the value of the variables in the evaluated expression
  - `${total_warnings}`     the total number of alarms in WARNING state on the host
diff --git a/health/notifications/discord/README.md b/health/notifications/discord/README.md
index 7694fef4b9..7b43f4e229 100644
--- a/health/notifications/discord/README.md
+++ b/health/notifications/discord/README.md
@@ -6,7 +6,7 @@ This is what you will get:
 
 You need:
 
-1. The **incoming webhook URL** as given by Discord. Create a webhook by following the official [Discord documentation](https://support.discordapp.com/hc/en-us/articles/228383668-Intro-to-Webhooks). You can use the same on all your netdata servers (or you can have multiple if you like - your decision).
+1. The **incoming webhook URL** as given by Discord. Create a webhook by following the official [Discord documentation](https://support.discordapp.com/hc/en-us/articles/228383668-Intro-to-Webhooks). You can use the same on all your Netdata servers (or you can have multiple if you like - your decision).
 2. One or more Discord channels to post the messages to.
 
 Set them in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system run `/etc/netdata/edit-config health_alarm_notify.conf`), like this:
diff --git a/health/notifications/email/README.md b/health/notifications/email/README.md
index 84a9e0ce71..ebe72f6d86 100644
--- a/health/notifications/email/README.md
+++ b/health/notifications/email/README.md
@@ -2,7 +2,7 @@
 
 You need a working `sendmail` command for email alerts to work. Almost all MTAs provide a `sendmail` interface.
 
-netdata sends all emails as user `netdata`, so make sure your `sendmail` works for local users.
+Netdata sends all emails as user `netdata`, so make sure your `sendmail` works for local users.
 
 email notifications look like this:
 
@@ -16,7 +16,7 @@ You can configure recipients in [`/etc/netdata/health_alarm_notify.conf`](https:
 
 You can also configure per role recipients [in the same file, a few lines below](https://github.com/netdata/netdata/blob/99d44b7d0c4e006b11318a28ba4a7e7d3f9b3bae/conf.d/health_alarm_notify.conf#L313).
 
-Changes to this file do not require netdata restart.
+Changes to this file do not require a Netdata restart.
 
 You can test your configuration by issuing the commands:
 
diff --git a/health/notifications/flock/README.md b/health/notifications/flock/README.md
index 0d679ce6b3..70a850376e 100644
--- a/health/notifications/flock/README.md
+++ b/health/notifications/flock/README.md
@@ -7,7 +7,7 @@ This is what you will get:
 
 You need:
 
-The **incoming webhook URL** as given by flock.com. You can use the same on all your netdata servers (or you can have multiple if you like - your decision).
+The **incoming webhook URL** as given by flock.com. You can use the same on all your Netdata servers (or you can have multiple if you like - your decision).
 
 Get them here: https://admin.flock.com/webhooks
 
@@ -21,8 +21,8 @@ Set them in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system r
 SEND_FLOCK="YES"
 
 # Login to flock.com and create an incoming webhook.
-# You need only one for all your netdata servers.
-# Without it, netdata cannot send flock notifications.
+# You need only one for all your Netdata servers.
+# Without it, Netdata cannot send flock notifications.
 FLOCK_WEBHOOK_URL="https://api.flock.com/hooks/sendMessage/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
 
 # if a role recipient is not configured, no notification will be sent
diff --git a/health/notifications/irc/README.md b/health/notifications/irc/README.md
index 9ea86e92d0..804ff6041b 100644
--- a/health/notifications/irc/README.md
+++ b/health/notifications/irc/README.md
@@ -10,7 +10,7 @@ Irssi terminal client:
 
 
 You need:
-1. The `nc` utility. If you do not set the path, netdata will search for it in your system `$PATH`.
+1. The `nc` utility. If you do not set the path, Netdata will search for it in your system `$PATH`.
 
 Set the path for `nc` in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system run `/etc/netdata/edit-config health_alarm_notify.conf`), like this:
 
diff --git a/health/notifications/kavenegar/README.md b/health/notifications/kavenegar/README.md
index d833eef82e..b8026b89a4 100644
--- a/health/notifications/kavenegar/README.md
+++ b/health/notifications/kavenegar/README.md
@@ -32,7 +32,7 @@ SEND_KAVENEGAR="YES"
 # copy your api key. You can generate new API Key too.
 # You can find and select kevenegar sender number from this place.
 
-# Without an API key, netdata cannot send KAVENEGAR text messages.
+# Without an API key, Netdata cannot send KAVENEGAR text messages.
 KAVENEGAR_API_KEY=""
 KAVENEGAR_SENDER=""
 DEFAULT_RECIPIENT_KAVENEGAR=""
diff --git a/health/notifications/messagebird/README.md b/health/notifications/messagebird/README.md
index cdb3e8dc11..62b8b2eaa3 100644
--- a/health/notifications/messagebird/README.md
+++ b/health/notifications/messagebird/README.md
@@ -31,7 +31,7 @@ SEND_MESSAGEBIRD="YES"
 # to get the API key, click on 'API' in the sidebar, then 'API Access (REST)' 
 # click 'Add access key' and fill in data (you want a live key to send SMS)
 
-# Without an access key, netdata cannot send Messagebird text messages.
+# Without an access key, Netdata cannot send Messagebird text messages.
 MESSAGEBIRD_ACCESS_KEY="XXXXXXXX"
 MESSAGEBIRD_NUMBER="XXXXXXX"
 DEFAULT_RECIPIENT_MESSAGEBIRD="XXXXXXX"
diff --git a/health/notifications/pagerduty/README.md b/health/notifications/pagerduty/README.md
index 884b979235..8f03a0695e 100644
--- a/health/notifications/pagerduty/README.md
+++ b/health/notifications/pagerduty/README.md
@@ -2,11 +2,11 @@
 
 [PagerDuty](https://www.pagerduty.com/company/) is the enterprise incident resolution service that integrates with ITOps and DevOps monitoring stacks to improve operational reliability and agility. From enriching and aggregating events to correlating them into incidents, PagerDuty streamlines the incident management process by reducing alert noise and resolution times.
 
-Here is an example of a PagerDuty dashboard with netdata notifications:
+Here is an example of a PagerDuty dashboard with Netdata notifications:
 
-![PagerDuty dashboard with netdata notifications](https://cloud.githubusercontent.com/assets/19278582/21233877/b466a08a-c2a5-11e6-8d66-ee6eed43818f.png)
+![PagerDuty dashboard with Netdata notifications](https://cloud.githubusercontent.com/assets/19278582/21233877/b466a08a-c2a5-11e6-8d66-ee6eed43818f.png)
 
-To have netdata send notifications to PagerDuty, you'll first need to set up a PagerDuty `Generic API` service and install the PagerDuty agent on the host running netdata.  See the following guide for details:
+To have Netdata send notifications to PagerDuty, you'll first need to set up a PagerDuty `Generic API` service and install the PagerDuty agent on the host running Netdata.  See the following guide for details:
 
 https://www.pagerduty.com/docs/guides/agent-install-guide/
 
diff --git a/health/notifications/pushbullet/README.md b/health/notifications/pushbullet/README.md
index 42b343e457..0c0b9a3224 100644
--- a/health/notifications/pushbullet/README.md
+++ b/health/notifications/pushbullet/README.md
@@ -36,7 +36,7 @@ SEND_PUSHBULLET="YES"
 # not have a pushbullet account, the pushbullet service will send an email
 # to that address instead
 
-# Without an access token, netdata cannot send pushbullet notifications.
+# Without an access token, Netdata cannot send pushbullet notifications.
 PUSHBULLET_ACCESS_TOKEN="o.Sometokenhere"
 DEFAULT_RECIPIENT_PUSHBULLET="admin1@example.com admin3@somemail.com"
 ```
diff --git a/health/notifications/pushover/README.md b/health/notifications/pushover/README.md
index 1debf5dcd4..90e2646a9b 100644
--- a/health/notifications/pushover/README.md
+++ b/health/notifications/pushover/README.md
@@ -2,11 +2,11 @@
 
 pushover.net allows you to receive push notifications on your mobile phone. The service seems free for up to 7.500 messages per month.
 
-netdata will send warning messages with priority `0` and critical messages with priority `1`. pushover.net allows you to select do-not-disturb hours. The way this is configured, critical notifications will ring and vibrate your phone, even during the do-not-disturb-hours. All other notifications will be delivered silently.
+Netdata will send warning messages with priority `0` and critical messages with priority `1`. pushover.net allows you to select do-not-disturb hours. The way this is configured, critical notifications will ring and vibrate your phone, even during the do-not-disturb-hours. All other notifications will be delivered silently.
 
 You need:
 
-1. APP TOKEN. You can use the same on all your netdata servers.
+1. APP TOKEN. You can use the same on all your Netdata servers.
 2. USER TOKEN for each user you are going to send notifications to. This is the actual recipient of the notification.
 
 The configuration is like above (slack messages).
diff --git a/health/notifications/rocketchat/README.md b/health/notifications/rocketchat/README.md
index f05e73f08b..f2650aedbd 100644
--- a/health/notifications/rocketchat/README.md
+++ b/health/notifications/rocketchat/README.md
@@ -4,7 +4,7 @@ This is what you will get:
 ![Netdata on RocketChat](https://i.imgur.com/Zu4t3j3.png)
 You need:
 
-1. The **incoming webhook URL** as given by RocketChat. You can use the same on all your netdata servers (or you can have multiple if you like - your decision).
+1. The **incoming webhook URL** as given by RocketChat. You can use the same on all your Netdata servers (or you can have multiple if you like - your decision).
 2. One or more channels to post the messages to.
 
 Get them here: https://rocket.chat/docs/administrator-guides/integrations/index.html#how-to-create-a-new-incoming-webhook
@@ -22,8 +22,8 @@ Set them in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system r
 SEND_ROCKETCHAT="YES"
 
 # Login to rocket.chat and create an incoming webhook. You need only one for all
-# your netdata servers (or you can have one for each of your netdata).
-# Without it, netdata cannot send rocketchat notifications.
+# your Netdata servers (or you can have one for each of your Netdata).
+# Without it, Netdata cannot send rocketchat notifications.
 ROCKETCHAT_WEBHOOK_URL="<your_incoming_webhook_url>"
 
 # if a role's recipients are not configured, a notification will be send to
diff --git a/health/notifications/slack/README.md b/health/notifications/slack/README.md
index 0616de4636..ba6b90e0d0 100644
--- a/health/notifications/slack/README.md
+++ b/health/notifications/slack/README.md
@@ -5,7 +5,7 @@ This is what you will get:
 
 You need:
 
-1. The **incoming webhook URL** as given by slack.com. You can use the same on all your netdata servers (or you can have multiple if you like - your decision).
+1. The **incoming webhook URL** as given by slack.com. You can use the same on all your Netdata servers (or you can have multiple if you like - your decision).
 2. One or more channels to post the messages to.
 
 To get a webhook that works on multiple channels, you will need to login to your slack.com workspace and create an incoming webhook using the [Incoming Webhooks App](https://slack.com/apps/A0F7XDUAZ-incoming-webhooks).
@@ -29,7 +29,7 @@ DEFAULT_RECIPIENT_SLACK="alarms"
 
 You can define multiple recipients like this: `# #alarms systems @myuser`. 
 This example will send the alarm to:
-- The recipient defined in slack for the webhook (not known to netdata)
+- The recipient defined in slack for the webhook (not known to Netdata)
 - The channel 'alarms'
 - The channel 'systems'
 - The user @myuser
diff --git a/health/notifications/smstools3/README.md b/health/notifications/smstools3/README.md
index 4a1469853e..67e62f7774 100644
--- a/health/notifications/smstools3/README.md
+++ b/health/notifications/smstools3/README.md
@@ -2,7 +2,7 @@
 
 The [SMS Server Tools 3](http://smstools3.kekekasvi.com/) is a SMS Gateway software which can send and receive short messages through GSM modems and mobile phones.
 
-To have netdata send notifications via SMS Server Tools 3, you'll first need to [install](http://smstools3.kekekasvi.com/index.php?p=compiling) and [configure](http://smstools3.kekekasvi.com/index.php?p=configure) smsd.
+To have Netdata send notifications via SMS Server Tools 3, you'll first need to [install](http://smstools3.kekekasvi.com/index.php?p=compiling) and [configure](http://smstools3.kekekasvi.com/index.php?p=configure) smsd.
 
 Ensure that the user `netdata` can execute `sendsms`. Any user executing `sendsms` needs to:
 
diff --git a/health/notifications/syslog/README.md b/health/notifications/syslog/README.md
index 597db0cd22..76f686c9cd 100644
--- a/health/notifications/syslog/README.md
+++ b/health/notifications/syslog/README.md
@@ -18,7 +18,7 @@ Targets are defined as follows:
 
 `prefix` defines what the log messages are prefixed with.  By default, all lines are prefixed with 'netdata'.
 
-The `facility` and `level` are the standard syslog facility and level options, for more info on them see your local `logger` and `syslog` documentation.  By default, netdata will log to the `local6` facility, with a log level dependent on the type of message (`crit` for CRITICAL, `warning` for WARNING, and `info` for everything else).
+The `facility` and `level` are the standard syslog facility and level options, for more info on them see your local `logger` and `syslog` documentation.  By default, Netdata will log to the `local6` facility, with a log level dependent on the type of message (`crit` for CRITICAL, `warning` for WARNING, and `info` for everything else).
 
 You can configure sending directly to remote log servers by specifying a host (and optionally a port).  However, this has a somewhat high overhead, so it is much preferred to use your local syslog daemon to handle the forwarding of messages to remote systems (pretty much all of them allow at least simple forwarding, and most of the really popular ones support complex queueing and routing of messages to remote log servers).
 
diff --git a/health/notifications/telegram/README.md b/health/notifications/telegram/README.md
index 9d652542c6..0d91f70eac 100644
--- a/health/notifications/telegram/README.md
+++ b/health/notifications/telegram/README.md
@@ -4,7 +4,7 @@
 
 With Telegram, you can send messages, photos, videos and files of any type (doc, zip, mp3, etc), as well as create groups for up to 30,000 people or channels for broadcasting to unlimited audiences. You can write to your phone contacts and find people by their usernames. As a result, Telegram is like SMS and email combined — and can take care of all your personal or business messaging needs.
 
-netdata will send warning messages without vibration.
+Netdata will send warning messages without vibration.
 
 You need:
 
diff --git a/health/notifications/twilio/README.md b/health/notifications/twilio/README.md
index 743f54e3c2..dc532fb8a5 100644
--- a/health/notifications/twilio/README.md
+++ b/health/notifications/twilio/README.md
@@ -32,7 +32,7 @@ SEND_TWILIO="YES"
 # Then just set the recipients' phone numbers.
 # The trial account is only allowed to use the number specified when set up.
 
-# Without an account sid and token, netdata cannot send Twilio text messages.
+# Without an account sid and token, Netdata cannot send Twilio text messages.
 TWILIO_ACCOUNT_SID="xxxxxxxxx"
 TWILIO_ACCOUNT_TOKEN="xxxxxxxxxx"
 TWILIO_NUMBER="xxxxxxxxxxx"
diff --git a/health/notifications/web/README.md b/health/notifications/web/README.md
index 0aac9419b9..2b2e575bfe 100644
--- a/health/notifications/web/README.md
+++ b/health/notifications/web/README.md
@@ -1,6 +1,6 @@
 # Dashboard
 
-The netdata dashboard shows HTML notifications, when it is open.
+The Netdata dashboard shows HTML notifications, when it is open.
 
 Such web notifications look like this:
 ![image](https://cloud.githubusercontent.com/assets/2662304/18407279/82bac6a6-7714-11e6-847e-c2e84eeacbfb.png)