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

7 files changed, 43 insertions, 43 deletions

diff --git a/web/api/README.md b/web/api/README.md
index 44afbc90d1..21cebdfa17 100644
--- a/web/api/README.md
+++ b/web/api/README.md
@@ -2,13 +2,13 @@
 
 ## Netdata REST API
 
-The complete documentation of the netdata API is available at the **[Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/netdata/netdata/master/web/api/netdata-swagger.yaml)**.
+The complete documentation of the Netdata API is available at the **[Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/netdata/netdata/master/web/api/netdata-swagger.yaml)**.
 
 If your prefer it over the Swagger Editor, you can also use **[Swagger UI](https://registry.my-netdata.io/swagger/#!/default/get_data)**. This however does not provide all the information available.
 
 ## Google charts API
 
-netdata is a [Google Visualization API datatable and datasource provider](https://developers.google.com/chart/interactive/docs/reference), so it can directly be used with [Google Charts](https://developers.google.com/chart/interactive/docs/).
+Netdata is a [Google Visualization API datatable and datasource provider](https://developers.google.com/chart/interactive/docs/reference), so it can directly be used with [Google Charts](https://developers.google.com/chart/interactive/docs/).
 
 Check this [single chart, jsfiddle example](https://jsfiddle.net/ktsaou/ensu4uws/9/):
 
diff --git a/web/api/badges/README.md b/web/api/badges/README.md
index 6884cc11ad..60f12e545d 100644
--- a/web/api/badges/README.md
+++ b/web/api/badges/README.md
@@ -6,11 +6,11 @@ Netdata can generate badges for any chart and any dimension at any time-frame. B
 
 **Netdata badges are powerful**!
 
-Given that netdata collects from **1.000** to **5.000** metrics per server (depending on the number of network interfaces, disks, cpu cores, applications running, users logged in, containers running, etc) and that netdata already has data reduction/aggregation functions embedded, the badges can be quite powerful.
+Given that Netdata collects from **1.000** to **5.000** metrics per server (depending on the number of network interfaces, disks, cpu cores, applications running, users logged in, containers running, etc) and that Netdata already has data reduction/aggregation functions embedded, the badges can be quite powerful.
 
 For each metric/dimension and for arbitrary time-frames badges can show **min**, **max** or **average** value, but also **sum** or **incremental-sum** to have their **volume**.
 
-For example, there is [a chart in netdata that shows the current requests/s of nginx](http://london.my-netdata.io/#nginx_local_nginx). Using this chart alone we can show the following badges (we could add more time-frames, like **today**, **yesterday**, etc):
+For example, there is [a chart in Netdata that shows the current requests/s of nginx](http://london.my-netdata.io/#nginx_local_nginx). Using this chart alone we can show the following badges (we could add more time-frames, like **today**, **yesterday**, etc):
 
 <a href="https://registry.my-netdata.io/#nginx_local_nginx"><img src="https://registry.my-netdata.io/api/v1/badge.svg?chart=nginx_local.connections&dimensions=active&value_color=grey:null%7Cblue&label=nginx%20active%20connections%20now&units=null&precision=0"/></a>  <a href="https://registry.my-netdata.io/#nginx_local_nginx"><img src="https://registry.my-netdata.io/api/v1/badge.svg?chart=nginx_local.connections&dimensions=active&after=-3600&value_color=orange&label=last%20hour%20average&units=null&options=unaligned&precision=0"/></a> <a href="https://registry.my-netdata.io/#nginx_local_nginx"><img src="https://registry.my-netdata.io/api/v1/badge.svg?chart=nginx_local.connections&dimensions=active&group=max&after=-3600&value_color=red&label=last%20hour%20max&units=null&options=unaligned&precision=0"/></a>
 
@@ -18,9 +18,9 @@ Similarly, there is [a chart that shows outbound bandwidth per class](http://lon
 
 <a href="https://registry.my-netdata.io/#tc_eth0"><img src="https://registry.my-netdata.io/api/v1/badge.svg?chart=tc.world_out&dimensions=web_server&value_color=green&label=web%20server%20sends%20now&units=kbps"/></a> <a href="https://registry.my-netdata.io/#tc_eth0"><img src="https://registry.my-netdata.io/api/v1/badge.svg?chart=tc.world_out&dimensions=web_server&after=-86400&options=unaligned&group=sum&divide=8388608&value_color=blue&label=web%20server%20sent%20today&units=GB"/></a>
 
-The right one is a **volume** calculation. Netdata calculated the total of the last 86.400 seconds (a day) which gives `kilobits`, then divided it by 8 to make it KB, then by 1024 to make it MB and then by 1024 to make it GB. Calculations like this are quite accurate, since for every value collected, every second, netdata interpolates it to second boundary using microsecond calculations.
+The right one is a **volume** calculation. Netdata calculated the total of the last 86.400 seconds (a day) which gives `kilobits`, then divided it by 8 to make it KB, then by 1024 to make it MB and then by 1024 to make it GB. Calculations like this are quite accurate, since for every value collected, every second, Netdata interpolates it to second boundary using microsecond calculations.
 
-Let's see a few more badge examples (they come from the [netdata registry](../../../registry/)):
+Let's see a few more badge examples (they come from the [Netdata registry](../../../registry/)):
 
 - **cpu usage of user `root`** (you can pick any user; 100% = 1 core). This will be `green <10%`, `yellow <20%`, `orange <50%`, `blue <100%` (1 core), `red` otherwise (you define thresholds and colors on the URL).
 
@@ -36,7 +36,7 @@ Let's see a few more badge examples (they come from the [netdata registry](../..
 
 ---
 
-> So, every single line on the charts of a [netdata dashboard](http://london.my-netdata.io/), can become a badge and this badge can calculate **average**, **min**, **max**, or **volume** for any time-frame! And you can also vary the badge color using conditions on the calculated value.
+> So, every single line on the charts of a [Netdata dashboard](http://london.my-netdata.io/), can become a badge and this badge can calculate **average**, **min**, **max**, or **volume** for any time-frame! And you can also vary the badge color using conditions on the calculated value.
 
 ---
 
@@ -44,13 +44,13 @@ Let's see a few more badge examples (they come from the [netdata registry](../..
 
 The basic URL is `http://your.netdata:19999/api/v1/badge.svg?option1&option2&option3&...`.
 
-Here is what you can put for `options` (these are standard netdata API options):
+Here is what you can put for `options` (these are standard Netdata API options):
 
 - `chart=CHART.NAME`
 
   The chart to get the values from.
 
-  **This is the only parameter required** and with just this parameter, netdata will return the sum of the latest values of all chart dimensions.
+  **This is the only parameter required** and with just this parameter, Netdata will return the sum of the latest values of all chart dimensions.
 
   Example:
 
@@ -76,7 +76,7 @@ Here is what you can put for `options` (these are standard netdata API options):
 
 - `dimensions=DIMENSION1|DIMENSION2|...`
 
-  The dimensions of the chart to use. If you don't set any dimension, all will be used. When multiple dimensions are used, netdata will sum their values. You can append `options=absolute` if you want this sum to convert all values to positive before adding them.
+  The dimensions of the chart to use. If you don't set any dimension, all will be used. When multiple dimensions are used, Netdata will sum their values. You can append `options=absolute` if you want this sum to convert all values to positive before adding them.
 
   Pipes in HTML have to escaped with `%7C`.
 
@@ -132,7 +132,7 @@ Here is what you can put for `options` (these are standard netdata API options):
 
 - `group=min` or `group=max` or `group=average` (the default) or `group=sum` or `group=incremental-sum`
 
-  If netdata will have to reduce (aggregate) the data to calculate the value, which aggregation method to use.
+  If Netdata will have to reduce (aggregate) the data to calculate the value, which aggregation method to use.
 
   - `max` will find the max value for the timeframe. This works on both positive and negative dimensions. It will find the most extreme value.
 
@@ -156,7 +156,7 @@ Here is what you can put for `options` (these are standard netdata API options):
 
   - `min2max`, when multiple dimensions are given, do not sum them, but take their `max - min`.
 
-  - `unaligned`, when data are reduced / aggregated (e.g. the request is about the average of the last minute, or hour), netdata by default aligns them so that the charts will have a constant shape (so average per minute returns always XX:XX:00 - XX:XX:59). Setting the `unaligned` option, netdata will aggregate data without any alignment, so if the request is for 60 seconds, it will aggregate the latest 60 seconds of collected data.
+  - `unaligned`, when data are reduced / aggregated (e.g. the request is about the average of the last minute, or hour), Netdata by default aligns them so that the charts will have a constant shape (so average per minute returns always XX:XX:00 - XX:XX:59). Setting the `unaligned` option, Netdata will aggregate data without any alignment, so if the request is for 60 seconds, it will aggregate the latest 60 seconds of collected data.
 
 These are options dedicated to badges:
 
@@ -166,9 +166,9 @@ These are options dedicated to badges:
 
 - `units=TEXT`
 
-  The units of the badge. If you want to put a `/`, please put a `\`. This is because netdata allows badges parameters to be given as path in URL, instead of query string. You can also use `null` or `empty` to show it without any units.
+  The units of the badge. If you want to put a `/`, please put a `\`. This is because Netdata allows badges parameters to be given as path in URL, instead of query string. You can also use `null` or `empty` to show it without any units.
 
-  The units `seconds`, `minutes` and `hours` trigger special formatting. The value has to be in this unit, and netdata will automatically change it to show a more pretty duration.
+  The units `seconds`, `minutes` and `hours` trigger special formatting. The value has to be in this unit, and Netdata will automatically change it to show a more pretty duration.
 
 - `multiply=NUMBER`
 
@@ -180,7 +180,7 @@ These are options dedicated to badges:
 
 - `label_color=COLOR`
 
-  The color of the label (the left part). You can use any HTML color, include `#NNN` and `#NNNNNN`. The following colors are defined in netdata (and you can use them by name): `green`, `brightgreen`, `yellow`, `yellowgreen`, `orange`, `red`, `blue`, `grey`, `gray`, `lightgrey`, `lightgray`. These are taken from https://github.com/badges/shields so they are compatible with standard badges.
+  The color of the label (the left part). You can use any HTML color, include `#NNN` and `#NNNNNN`. The following colors are defined in Netdata (and you can use them by name): `green`, `brightgreen`, `yellow`, `yellowgreen`, `orange`, `red`, `blue`, `grey`, `gray`, `lightgrey`, `lightgray`. These are taken from https://github.com/badges/shields so they are compatible with standard badges.
 
 - `value_color=COLOR:null|COLOR<VALUE|COLOR>VALUE|COLOR>=VALUE|COLOR<=VALUE|...`
 
@@ -188,13 +188,13 @@ These are options dedicated to badges:
 
   Example: `value_color=grey:null|green<10|yellow<100|orange<1000|blue<10000|red`
 
-  The above will set `grey` if no value exists (not collected within the `gap when lost iterations above` in netdata.conf for the chart), `green` if the value is less than 10, `yellow` if the value is less than 100, etc up to `red` which will be used if no other conditions match.
+  The above will set `grey` if no value exists (not collected within the `gap when lost iterations above` in `netdata.conf` for the chart), `green` if the value is less than 10, `yellow` if the value is less than 100, etc up to `red` which will be used if no other conditions match.
 
   The supported operators are `<`, `>`, `<=`, `>=`, `=` (or `:`) and `!=` (or `<>`).
 
 - `precision=NUMBER`
 
-  The number of decimal digits of the value. By default netdata will add:
+  The number of decimal digits of the value. By default Netdata will add:
 
   - no decimal digits for values > 1000
   - 1 decimal digit for values > 100
@@ -217,7 +217,7 @@ These are options dedicated to badges:
 
 - `refresh=auto` or `refresh=SECONDS`
 
-  This option enables auto-refreshing of images. netdata will send the HTTP header `Refresh: SECONDS` to the web browser, thus requesting automatic refresh of the images at regular intervals.
+  This option enables auto-refreshing of images. Netdata will send the HTTP header `Refresh: SECONDS` to the web browser, thus requesting automatic refresh of the images at regular intervals.
 
   `auto` will calculate the proper `SECONDS` to avoid unnecessary refreshes. If `SECONDS` is zero, this feature is disabled (it is also disabled by default).
 
@@ -227,7 +227,7 @@ These are options dedicated to badges:
 <embed src="BADGE_URL" type="image/svg+xml" height="20" />
 ```
 
-  Another way is to use javascript to auto-refresh them. You can auto-refresh all the netdata badges on a page using javascript. You have to add a class to all the netdata badges, like this `<img class="netdata-badge" src="..."/>`. Then add this javascript code to your page (it requires jquery):
+  Another way is to use javascript to auto-refresh them. You can auto-refresh all the Netdata badges on a page using javascript. You have to add a class to all the Netdata badges, like this `<img class="netdata-badge" src="..."/>`. Then add this javascript code to your page (it requires jquery):
 
 ```html
 <script>
@@ -264,9 +264,9 @@ character|name|escape sequence
 ## FAQ
 
 #### Is it fast?
-On modern hardware, netdata can generate about **2.000 badges per second per core**, before noticing any delays. It generates a badge in about half a millisecond!
+On modern hardware, Netdata can generate about **2.000 badges per second per core**, before noticing any delays. It generates a badge in about half a millisecond!
 
-Of course these timing are for badges that use recent data. If you need badges that do calculations over long durations (a day, or more), timing will differ. netdata logs its timings at its `access.log`, so take a look there before adding a heavy badge on a busy web site. Of course, you can cache such badges or have a cron job get them from netdata and save them at your web server at regular intervals.
+Of course these timing are for badges that use recent data. If you need badges that do calculations over long durations (a day, or more), timing will differ. Netdata logs its timings at its `access.log`, so take a look there before adding a heavy badge on a busy web site. Of course, you can cache such badges or have a cron job get them from Netdata and save them at your web server at regular intervals.
 
 
 #### Embedding badges in github
diff --git a/web/api/exporters/prometheus/README.md b/web/api/exporters/prometheus/README.md
index 88e79ecd6a..8c4f2b4efe 100644
--- a/web/api/exporters/prometheus/README.md
+++ b/web/api/exporters/prometheus/README.md
@@ -1,5 +1,5 @@
 # prometheus exporter
 
-The prometheus exporter for netdata is located at the [backends section for prometheus](../../../../backends/prometheus).
+The prometheus exporter for Netdata is located at the [backends section for prometheus](../../../../backends/prometheus).
 
 [![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%2Fweb%2Fapi%2Fexporters%2Fprometheus%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()
diff --git a/web/api/exporters/shell/README.md b/web/api/exporters/shell/README.md
index ab412ebaaa..90ad915821 100644
--- a/web/api/exporters/shell/README.md
+++ b/web/api/exporters/shell/README.md
@@ -1,18 +1,18 @@
 # shell exporter
 
-Shell scripts can now query netdata:
+Shell scripts can now query Netdata:
 
 ```sh
 eval "$(curl -s 'http://localhost:19999/api/v1/allmetrics')"
 ```
 
-after this command, all the netdata metrics are exposed to shell. Check:
+after this command, all the Netdata metrics are exposed to shell. Check:
 
 ```sh
 # source the metrics
 eval "$(curl -s 'http://localhost:19999/api/v1/allmetrics')"
 
-# let's see if there are variables exposed by netdata for system.cpu
+# let's see if there are variables exposed by Netdata for system.cpu
 set | grep "^NETDATA_SYSTEM_CPU"
 
 NETDATA_SYSTEM_CPU_GUEST=0
@@ -50,7 +50,7 @@ user  0m0,000s
 sys   0m0,007s
 
 # it is...
-# 0.07 seconds for curl to be loaded, connect to netdata and fetch the response back...
+# 0.07 seconds for curl to be loaded, connect to Netdata and fetch the response back...
 ```
 
 The `_VISIBLETOTAL` variable sums up all the dimensions of each chart.
diff --git a/web/api/formatters/README.md b/web/api/formatters/README.md
index b4ce1e30db..4c361bb13f 100644
--- a/web/api/formatters/README.md
+++ b/web/api/formatters/README.md
@@ -59,9 +59,9 @@ This is such an object:
 ## Downloading data query result files
 
 Following the [Google Visualization Provider guidelines](https://developers.google.com/chart/interactive/docs/dev/implementing_data_source),
-netdata supports parsing `tqx` options.
+Netdata supports parsing `tqx` options.
 
-Using these options, any netdata data query can instruct the web browser to download
+Using these options, any Netdata data query can instruct the web browser to download
 the result and save it under a given filename.
 
 For example, to download a CSV file with CPU utilization of the last hour,
diff --git a/web/api/health/README.md b/web/api/health/README.md
index 0b4f79f387..b74fee5749 100644
--- a/web/api/health/README.md
+++ b/web/api/health/README.md
@@ -45,11 +45,11 @@ The following will return an SVG badge of the alarm named `NAME`, attached to th
 ## Health Management API
 
 Netdata v1.12 and beyond provides a command API to control health checks and notifications at runtime. The feature is especially useful for maintenance periods, during which you receive meaningless alarms.
-From Netdata v1.16.0 and beyond, the configuration controlled via the API commands is [persisted across netdata restarts](#persistence).
+From Netdata v1.16.0 and beyond, the configuration controlled via the API commands is [persisted across Netdata restarts](#persistence).
 
 Specifically, the API allows you to:
  - Disable health checks completely. Alarm conditions will not be evaluated at all and no entries will be added to the alarm log.
- - Silence alarm notifications. Alarm conditions will be evaluated, the alarms will appear in the log and the netdata UI will show the alarms as active, but no notifications will be sent.
+ - Silence alarm notifications. Alarm conditions will be evaluated, the alarms will appear in the log and the Netdata UI will show the alarms as active, but no notifications will be sent.
  - Disable or Silence specific alarms that match selectors on alarm/template name, chart, context, host and family.
 
 The API is available by default, but it is protected by an `api authorization token` that is stored in the file you will see in the following entry of `http://localhost:19999/netdata.conf`:
@@ -65,9 +65,9 @@ You can access the API via GET requests, by adding the bearer token to an `Autho
 curl "http://myserver/api/v1/manage/health?cmd=RESET" -H "X-Auth-Token: Mytoken"
 ```
 
-By default access to the health management API is only allowed from `localhost`. Accessing the API from anything else will return a 403 error with the message `You are not allowed to access this resource.`. You can change permissions by editing the `allow management from` variable in netdata.conf within the [web] section. See [web server access lists](../../server/#access-lists) for more information.
+By default access to the health management API is only allowed from `localhost`. Accessing the API from anything else will return a 403 error with the message `You are not allowed to access this resource.`. You can change permissions by editing the `allow management from` variable in `netdata.conf` within the [web] section. See [web server access lists](../../server/#access-lists) for more information.
 
-The command `RESET` just returns netdata to the default operation, with all health checks and notifications enabled.
+The command `RESET` just returns Netdata to the default operation, with all health checks and notifications enabled.
 If you've configured and entered your token correclty, you should see the plain text response `All health checks and notifications are enabled`.
 
 ### Disable or silence all alarms
@@ -85,7 +85,7 @@ If you want the health checks to be running but to not receive any notifications
 curl "http://myserver/api/v1/manage/health?cmd=SILENCE ALL" -H "X-Auth-Token: Mytoken"
 ```
 
-Alarms may then still be raised and logged in netdata, so you'll be able to see them via the UI.  
+Alarms may then still be raised and logged in Netdata, so you'll be able to see them via the UI.  
 
 Regardless of the option you choose, at the end of your maintenance period you revert to the normal state via the RESET command.
 
@@ -118,7 +118,7 @@ curl "http://myserver/api/v1/manage/health?cmd=SILENCE&context=load" -H "X-Auth-
 
 #### Selection criteria
 
-The `selection criteria` are key/value pairs, in the format `key : value`, where value is a netdata [simple pattern](../../../libnetdata/simple_pattern/). This means that you can create very powerful selectors (you will rarely need more than one or two).
+The `selection criteria` are key/value pairs, in the format `key : value`, where value is a Netdata [simple pattern](../../../libnetdata/simple_pattern/). This means that you can create very powerful selectors (you will rarely need more than one or two).
 
 The accepted keys for the `selection criteria` are the following:
 - `alarm`    : The expression provided will match both `alarm` and `template` names.
@@ -149,7 +149,7 @@ http://localhost/api/v1/manage/health?families=cpu1 cpu2
 
 ### List silencers
 
-The command `LIST` was added in netdata v1.16.0 and returns a JSON with the current status of the silencers.
+The command `LIST` was added in Netdata v1.16.0 and returns a JSON with the current status of the silencers.
 
 ```
  curl "http://myserver/api/v1/manage/health?cmd=LIST" -H "X-Auth-Token: Mytoken"
@@ -200,7 +200,7 @@ json
 
 ### Persistence
 
-From netdata v1.16.0 and beyond, the silencers configuration is persisted to disk and loaded when netdata starts.
+From Netdata v1.16.0 and beyond, the silencers configuration is persisted to disk and loaded when Netdata starts.
 The JSON string returned by the [LIST command](#list-silencers) is automatically saved to the `silencers file`, every time a command alters the silencers configuration.
 The file's location is configurable in `netdata.conf`. The default is shown below:
 
diff --git a/web/api/queries/README.md b/web/api/queries/README.md
index 6a55398aca..d48d6c8129 100644
--- a/web/api/queries/README.md
+++ b/web/api/queries/README.md
@@ -54,7 +54,7 @@ There are 2 uses that enable this feature:
   For example, for a time-frame of 10 minutes, the database has 600 points (1/sec),
   while the caller requested these 10 minutes to be expressed in 200 points.
   
-  This feature is used by netdata dashboards when you zoom-out the charts.
+  This feature is used by Netdata dashboards when you zoom-out the charts.
   The dashboard is requesting the number of points the user's screen has.
   This saves bandwidth and speeds up the browser (fewer points to evaluate for drawing the charts).
   
@@ -69,7 +69,7 @@ an integer. Keep in mind the query engine may shift `after` if required. See als
 
 #### Time-frame Alignment
 
-Alignment is a very important aspect of netdata queries. Without it, the animated
+Alignment is a very important aspect of Netdata queries. Without it, the animated
 charts on the dashboards would constantly [change shape](#example) during incremental updates.
 
 To provide consistent grouping through time, the query engine (by default) aligns
@@ -111,7 +111,7 @@ and they group the values every `group points`.
 - ![](https://registry.my-netdata.io/api/v1/badge.svg?chart=web_log_nginx.response_statuses&options=unaligned&dimensions=success&group=des&after=-60&label=des&value_color=blue) applies Holt-Winters double exponential smoothing
 - ![](https://registry.my-netdata.io/api/v1/badge.svg?chart=web_log_nginx.response_statuses&options=unaligned&dimensions=success&group=incremental_sum&after=-60&label=incremental_sum&value_color=red) finds the difference of the last vs the first value
 
-The examples shown above, are live information from the `successful` web requests of the global netdata registry.
+The examples shown above, are live information from the `successful` web requests of the global Netdata registry.
 
 ## Further processing
 
@@ -129,7 +129,7 @@ the result.
 
 ## Example
 
-When netdata is reducing metrics, it tries to return always the same boundaries. So, if we want 10s averages, it will always return points starting at a `unix timestamp % 10 = 0`.
+When Netdata is reducing metrics, it tries to return always the same boundaries. So, if we want 10s averages, it will always return points starting at a `unix timestamp % 10 = 0`.
 
 Let's see why this is needed, by looking at the error case.
 
@@ -143,7 +143,7 @@ Assume we have 5 points:
 | 00:04 | 4 |
 | 00:05 | 5 |
 
-At 00:04 you ask for 2 points for 4 seconds in the past. So `group = 2`. netdata would return:
+At 00:04 you ask for 2 points for 4 seconds in the past. So `group = 2`. Netdata would return:
 
 | point | time | value |
 | :-: | :-: | :-: |
@@ -159,9 +159,9 @@ A second later the chart is to be refreshed, and makes again the same request at
 
 **Wait a moment!** The chart was shifted just one point and it changed value! Point 2 was 3.5 and when shifted to point 1 is 2.5! If you see this in a chart, it's a mess. The charts change shape constantly.
 
-For this reason, netdata always aligns the data it returns to the `group`.
+For this reason, Netdata always aligns the data it returns to the `group`.
 
-When you request `points=1`, netdata understands that you need 1 point for the whole database, so `group = 3600`. Then it tries to find the starting point which would be `timestamp % 3600 = 0` Within a database of 3600 seconds, there is one such point for sure. Then it tries to find the average of 3600 points. But, most probably it will not find 3600 of them (for just 1 out of 3600 seconds this query will return something).
+When you request `points=1`, Netdata understands that you need 1 point for the whole database, so `group = 3600`. Then it tries to find the starting point which would be `timestamp % 3600 = 0` Within a database of 3600 seconds, there is one such point for sure. Then it tries to find the average of 3600 points. But, most probably it will not find 3600 of them (for just 1 out of 3600 seconds this query will return something).
 
 So, the proper way to query the database is to also set at least `after`. The following call will returns 1 point for the last complete 10-second duration (it starts at `timestamp % 10 = 0`):