Clean netdata naming (#11484)

* replace "NetData" with "Netdata"

* replace "NetData" with "Netdata"

21 files changed, 68 insertions, 68 deletions

diff --git a/.github/scripts/pkg-test.sh b/.github/scripts/pkg-test.sh
index e54882beaf..7124d7b82a 100755
--- a/.github/scripts/pkg-test.sh
+++ b/.github/scripts/pkg-test.sh
@@ -6,7 +6,7 @@ install_debian_like() {
 
   apt-get update
 
-  # Install NetData
+  # Install Netdata
   apt-get install -y /netdata/artifacts/netdata_"${VERSION}"_*.deb || exit 1
 
   # Install testing tools
@@ -21,7 +21,7 @@ install_fedora_like() {
 
   pkg_version="$(echo "${VERSION}" | tr - .)"
 
-  # Install NetData
+  # Install Netdata
   "$PKGMGR" install -y /netdata/artifacts/netdata-"${pkg_version}"-*.rpm
 
   # Install testing tools
@@ -39,7 +39,7 @@ install_centos() {
   # Install EPEL (needed for `jq`
   "$PKGMGR" install -y epel-release || exit 1
 
-  # Install NetData
+  # Install Netdata
   "$PKGMGR" install -y /netdata/artifacts/netdata-"${pkg_version}"-*.rpm
 
   # Install testing tools
@@ -52,7 +52,7 @@ install_suse_like() {
 
   pkg_version="$(echo "${VERSION}" | tr - .)"
 
-  # Install NetData
+  # Install Netdata
   zypper install -y --allow-unsigned-rpm /netdata/artifacts/netdata-"${pkg_version}"-*.rpm
 
   # Install testing tools
diff --git a/backends/WALKTHROUGH.md b/backends/WALKTHROUGH.md
index 76dd62f834..12eea2ee1a 100644
--- a/backends/WALKTHROUGH.md
+++ b/backends/WALKTHROUGH.md
@@ -176,14 +176,14 @@ Prometheus’s homepage and begin to type ‘netdata\_’ Prometheus should auto
 
 ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.13.43%20PM.png)
 
-Let’s now start exploring how we can graph some metrics. Back in our NetData container lets get the CPU spinning with a
+Let’s now start exploring how we can graph some metrics. Back in our Netdata container lets get the CPU spinning with a
 pointless busy loop. On the shell do the following:
 
 ```sh
 [root@netdata /]# while true; do echo "HOT HOT HOT CPU"; done
 ```
 
-Our NetData cpu graph should be showing some activity. Let’s represent this in Prometheus. In order to do this let’s
+Our Netdata cpu graph should be showing some activity. Let’s represent this in Prometheus. In order to do this let’s
 keep our metrics page open for reference: <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes>  We are
 setting out to graph the data in the CPU chart so let’s search for “system.cpu”in the metrics page above. We come across
 a section of metrics with the first comments  `# COMMENT homogeneous chart "system.cpu", context "system.cpu", family
@@ -209,18 +209,18 @@ query the dimension also. Place this into our query text box.
 
 ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.54.40%20PM.png)
 
-Awesome, this is exactly what we wanted. If you haven’t caught on yet we can emulate entire charts from NetData by using
+Awesome, this is exactly what we wanted. If you haven’t caught on yet we can emulate entire charts from Netdata by using
 the `chart` dimension. If you’d like you can combine the ‘chart’ and ‘instance’ dimension to create per-instance charts.
 Let’s give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}`
 
-This is the basics of using Prometheus to query NetData. I’d advise everyone at this point to read [this
-page](../backends/prometheus/#using-netdata-with-prometheus). The key point here is that NetData can export metrics from
+This is the basics of using Prometheus to query Netdata. I’d advise everyone at this point to read [this
+page](../backends/prometheus/#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from
 its internal DB or can send metrics “as-collected” by specifying the ‘source=as-collected’ url parameter like so.
 <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use
 this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to
 obtain useful metrics as you are now dealing with raw counters from the system. For example you will have to use the
 `irate()` function over a counter to get that metric's rate per second. If your graphing needs are met by using the
-metrics returned by NetData's internal database (not specifying any source= url parameter) then use that. If you find
+metrics returned by Netdata's internal database (not specifying any source= url parameter) then use that. If you find
 limitations then consider re-writing your queries using the raw data and using Prometheus functions to get the desired
 chart.
 
diff --git a/backends/prometheus/README.md b/backends/prometheus/README.md
index 28147b2ddd..a0460d1d8e 100644
--- a/backends/prometheus/README.md
+++ b/backends/prometheus/README.md
@@ -125,7 +125,7 @@ scrape_configs:
 
 #### Install nodes.yml
 
-The following is completely optional, it will enable Prometheus to generate alerts from some NetData sources. Tweak the
+The following is completely optional, it will enable Prometheus to generate alerts from some Netdata sources. Tweak the
 values to your own needs. We will use the following `nodes.yml` file below. Save it at `/opt/prometheus/nodes.yml`, and
 add a _- "nodes.yml"_ entry under the _rule_files:_ section in the example prometheus.yml file above.
 
diff --git a/build_external/scenarios/aclk-testing/agent_netdata.conf b/build_external/scenarios/aclk-testing/agent_netdata.conf
index d13e51453a..774005f76e 100644
--- a/build_external/scenarios/aclk-testing/agent_netdata.conf
+++ b/build_external/scenarios/aclk-testing/agent_netdata.conf
@@ -1124,7 +1124,7 @@
 	# context = netdata.statsd_cpu

 	# priority = 132001

 	# name = netdata.plugin_statsd_charting_cpu

-	# title = NetData statsd charting thread CPU usage

+	# title = Netdata statsd charting thread CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -1145,7 +1145,7 @@
 	# context = netdata.statsd_cpu

 	# priority = 132002

 	# name = netdata.plugin_statsd_collector1_cpu

-	# title = NetData statsd collector thread No 1 CPU usage

+	# title = Netdata statsd collector thread No 1 CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -1955,7 +1955,7 @@
 	# context = netdata.plugin_cgroups_cpu

 	# priority = 132000

 	# name = netdata.plugin_cgroups_cpu

-	# title = NetData CGroups Plugin CPU usage

+	# title = Netdata CGroups Plugin CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -1976,7 +1976,7 @@
 	# context = netdata.plugin_diskspace

 	# priority = 132020

 	# name = netdata.plugin_diskspace

-	# title = NetData Disk Space Plugin CPU usage

+	# title = Netdata Disk Space Plugin CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -1997,7 +1997,7 @@
 	# context = netdata.plugin_diskspace_dt

 	# priority = 132021

 	# name = netdata.plugin_diskspace_dt

-	# title = NetData Disk Space Plugin Duration

+	# title = Netdata Disk Space Plugin Duration

 	# dim duration name = duration

 	# dim duration algorithm = absolute

 	# dim duration multiplier = 1

@@ -4844,7 +4844,7 @@
 	# context = netdata.plugin_proc_modules

 	# priority = 132001

 	# name = netdata.plugin_proc_modules

-	# title = NetData Proc Plugin Modules Durations

+	# title = Netdata Proc Plugin Modules Durations

 	# dim stat name = stat

 	# dim stat algorithm = absolute

 	# dim stat multiplier = 1

@@ -4949,7 +4949,7 @@
 	# context = netdata.plugin_proc_cpu

 	# priority = 132000

 	# name = netdata.plugin_proc_cpu

-	# title = NetData Proc Plugin CPU usage

+	# title = Netdata Proc Plugin CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -4970,7 +4970,7 @@
 	# context = netdata.server_cpu

 	# priority = 130000

 	# name = netdata.server_cpu

-	# title = NetData CPU usage

+	# title = Netdata CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -4991,7 +4991,7 @@
 	# context = netdata.clients

 	# priority = 130200

 	# name = netdata.clients

-	# title = NetData Web Clients

+	# title = Netdata Web Clients

 	# dim clients name = clients

 	# dim clients algorithm = absolute

 	# dim clients multiplier = 1

@@ -5008,7 +5008,7 @@
 	# context = netdata.requests

 	# priority = 130300

 	# name = netdata.requests

-	# title = NetData Web Requests

+	# title = Netdata Web Requests

 	# dim requests name = requests

 	# dim requests algorithm = incremental

 	# dim requests multiplier = 1

@@ -5025,7 +5025,7 @@
 	# context = netdata.net

 	# priority = 130000

 	# name = netdata.net

-	# title = NetData Network Traffic

+	# title = Netdata Network Traffic

 	# dim in name = in

 	# dim in algorithm = incremental

 	# dim in multiplier = 8

@@ -5046,7 +5046,7 @@
 	# context = netdata.response_time

 	# priority = 130400

 	# name = netdata.response_time

-	# title = NetData API Response Time

+	# title = Netdata API Response Time

 	# dim average name = average

 	# dim average algorithm = absolute

 	# dim average multiplier = 1

@@ -5067,7 +5067,7 @@
 	# context = netdata.compression_ratio

 	# priority = 130500

 	# name = netdata.compression_ratio

-	# title = NetData API Responses Compression Savings Ratio

+	# title = Netdata API Responses Compression Savings Ratio

 	# dim savings name = savings

 	# dim savings algorithm = absolute

 	# dim savings multiplier = 1

@@ -5084,7 +5084,7 @@
 	# context = netdata.dbengine_compression_ratio

 	# priority = 130502

 	# name = netdata.dbengine_compression_ratio

-	# title = NetData DB engine data extents' compression savings ratio

+	# title = Netdata DB engine data extents' compression savings ratio

 	# dim savings name = savings

 	# dim savings algorithm = absolute

 	# dim savings multiplier = 1

@@ -5101,7 +5101,7 @@
 	# context = netdata.page_cache_hit_ratio

 	# priority = 130503

 	# name = netdata.page_cache_hit_ratio

-	# title = NetData DB engine page cache hit ratio

+	# title = Netdata DB engine page cache hit ratio

 	# dim ratio name = ratio

 	# dim ratio algorithm = absolute

 	# dim ratio multiplier = 1

@@ -5118,7 +5118,7 @@
 	# context = netdata.page_cache_stats

 	# priority = 130504

 	# name = netdata.page_cache_stats

-	# title = NetData dbengine page cache statistics

+	# title = Netdata dbengine page cache statistics

 	# dim descriptors name = descriptors

 	# dim descriptors algorithm = absolute

 	# dim descriptors multiplier = 1

@@ -5155,7 +5155,7 @@
 	# context = netdata.dbengine_long_term_page_stats

 	# priority = 130505

 	# name = netdata.dbengine_long_term_page_stats

-	# title = NetData dbengine long-term page statistics

+	# title = Netdata dbengine long-term page statistics

 	# dim total name = total

 	# dim total algorithm = absolute

 	# dim total multiplier = 1

@@ -5184,7 +5184,7 @@
 	# context = netdata.dbengine_io_throughput

 	# priority = 130506

 	# name = netdata.dbengine_io_throughput

-	# title = NetData DB engine I/O throughput

+	# title = Netdata DB engine I/O throughput

 	# dim reads name = reads

 	# dim reads algorithm = incremental

 	# dim reads multiplier = 1

@@ -5205,7 +5205,7 @@
 	# context = netdata.dbengine_io_operations

 	# priority = 130507

 	# name = netdata.dbengine_io_operations

-	# title = NetData DB engine I/O operations

+	# title = Netdata DB engine I/O operations

 	# dim reads name = reads

 	# dim reads algorithm = incremental

 	# dim reads multiplier = 1

@@ -5226,7 +5226,7 @@
 	# context = netdata.dbengine_global_errors

 	# priority = 130508

 	# name = netdata.dbengine_global_errors

-	# title = NetData DB engine errors

+	# title = Netdata DB engine errors

 	# dim io_errors name = io_errors

 	# dim io_errors algorithm = incremental

 	# dim io_errors multiplier = 1

@@ -5251,7 +5251,7 @@
 	# context = netdata.dbengine_global_file_descriptors

 	# priority = 130509

 	# name = netdata.dbengine_global_file_descriptors

-	# title = NetData DB engine File Descriptors

+	# title = Netdata DB engine File Descriptors

 	# dim current name = current

 	# dim current algorithm = absolute

 	# dim current multiplier = 1

@@ -5272,7 +5272,7 @@
 	# context = netdata.dbengine_ram

 	# priority = 130510

 	# name = netdata.dbengine_ram

-	# title = NetData DB engine RAM usage

+	# title = Netdata DB engine RAM usage

 	# dim cache name = cache

 	# dim cache algorithm = absolute

 	# dim cache multiplier = 1

@@ -5297,7 +5297,7 @@
 	# context = netdata.web_cpu

 	# priority = 132003

 	# name = netdata.web_thread4_cpu

-	# title = NetData web server thread No 4 CPU usage

+	# title = Netdata web server thread No 4 CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -5318,7 +5318,7 @@
 	# context = netdata.web_cpu

 	# priority = 132000

 	# name = netdata.web_thread1_cpu

-	# title = NetData web server thread No 1 CPU usage

+	# title = Netdata web server thread No 1 CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -5339,7 +5339,7 @@
 	# context = netdata.web_cpu

 	# priority = 132005

 	# name = netdata.web_thread6_cpu

-	# title = NetData web server thread No 6 CPU usage

+	# title = Netdata web server thread No 6 CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -5360,7 +5360,7 @@
 	# context = netdata.web_cpu

 	# priority = 132002

 	# name = netdata.web_thread3_cpu

-	# title = NetData web server thread No 3 CPU usage

+	# title = Netdata web server thread No 3 CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -5381,7 +5381,7 @@
 	# context = netdata.web_cpu

 	# priority = 132001

 	# name = netdata.web_thread2_cpu

-	# title = NetData web server thread No 2 CPU usage

+	# title = Netdata web server thread No 2 CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

@@ -5520,7 +5520,7 @@
 	# context = netdata.web_cpu

 	# priority = 132004

 	# name = netdata.web_thread5_cpu

-	# title = NetData web server thread No 5 CPU usage

+	# title = Netdata web server thread No 5 CPU usage

 	# dim user name = user

 	# dim user algorithm = incremental

 	# dim user multiplier = 1

diff --git a/collectors/statsd.plugin/statsd.c b/collectors/statsd.plugin/statsd.c
index 66be7f02e1..f17d65753f 100644
--- a/collectors/statsd.plugin/statsd.c
+++ b/collectors/statsd.plugin/statsd.c
@@ -2441,7 +2441,7 @@ void *statsd_main(void *ptr) {
         char title[100 + 1];
 
         snprintfz(id, 100, "plugin_statsd_collector%d_cpu", i + 1);
-        snprintfz(title, 100, "NetData statsd collector thread No %d CPU usage", i + 1);
+        snprintfz(title, 100, "Netdata statsd collector thread No %d CPU usage", i + 1);
 
         statsd.collection_threads_status[i].st_cpu = rrdset_create_localhost(
                 "netdata"
diff --git a/exporting/WALKTHROUGH.md b/exporting/WALKTHROUGH.md
index ac17129164..24afd20972 100644
--- a/exporting/WALKTHROUGH.md
+++ b/exporting/WALKTHROUGH.md
@@ -178,14 +178,14 @@ Prometheus's homepage and begin to type `netdata\_` Prometheus should auto compl
 
 ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.13.43%20PM.png)
 
-Let's now start exploring how we can graph some metrics. Back in our NetData container lets get the CPU spinning with a
+Let's now start exploring how we can graph some metrics. Back in our Netdata container lets get the CPU spinning with a
 pointless busy loop. On the shell do the following:
 
 ```sh
 [root@netdata /]# while true; do echo "HOT HOT HOT CPU"; done
 ```
 
-Our NetData cpu graph should be showing some activity. Let's represent this in Prometheus. In order to do this let's
+Our Netdata cpu graph should be showing some activity. Let's represent this in Prometheus. In order to do this let's
 keep our metrics page open for reference: <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes>. We are
 setting out to graph the data in the CPU chart so let's search for `system.cpu` in the metrics page above. We come
 across a section of metrics with the first comments  `# COMMENT homogeneous chart "system.cpu", context "system.cpu",
@@ -211,18 +211,18 @@ query the dimension also. Place this into our query text box.
 
 ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.54.40%20PM.png)
 
-Awesome, this is exactly what we wanted. If you haven't caught on yet we can emulate entire charts from NetData by using
+Awesome, this is exactly what we wanted. If you haven't caught on yet we can emulate entire charts from Netdata by using
 the `chart` dimension. If you'd like you can combine the `chart` and `instance` dimension to create per-instance charts.
 Let's give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}`
 
-This is the basics of using Prometheus to query NetData. I'd advise everyone at this point to read [this
-page](/exporting/prometheus/#using-netdata-with-prometheus). The key point here is that NetData can export metrics from
+This is the basics of using Prometheus to query Netdata. I'd advise everyone at this point to read [this
+page](/exporting/prometheus/#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from
 its internal DB or can send metrics _as-collected_ by specifying the `source=as-collected` URL parameter like so.
 <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use
 this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to
 obtain useful metrics as you are now dealing with raw counters from the system. For example you will have to use the
 `irate()` function over a counter to get that metric's rate per second. If your graphing needs are met by using the
-metrics returned by NetData's internal database (not specifying any source= URL parameter) then use that. If you find
+metrics returned by Netdata's internal database (not specifying any source= URL parameter) then use that. If you find
 limitations then consider re-writing your queries using the raw data and using Prometheus functions to get the desired
 chart.
 
diff --git a/exporting/prometheus/README.md b/exporting/prometheus/README.md
index 27f4b10d44..ef6f613580 100644
--- a/exporting/prometheus/README.md
+++ b/exporting/prometheus/README.md
@@ -128,7 +128,7 @@ scrape_configs:
 
 #### Install nodes.yml
 
-The following is completely optional, it will enable Prometheus to generate alerts from some NetData sources. Tweak the
+The following is completely optional, it will enable Prometheus to generate alerts from some Netdata sources. Tweak the
 values to your own needs. We will use the following `nodes.yml` file below. Save it at `/opt/prometheus/nodes.yml`, and
 add a _- "nodes.yml"_ entry under the _rule_files:_ section in the example prometheus.yml file above.
 
diff --git a/health/notifications/alarm-notify.sh.in b/health/notifications/alarm-notify.sh.in
index ed423fb4e8..15fd0908e7 100755
--- a/health/notifications/alarm-notify.sh.in
+++ b/health/notifications/alarm-notify.sh.in
@@ -2137,12 +2137,12 @@ send_dynatrace() {
   [ "${SEND_DYNATRACE}" != "YES" ] && return 1
 
   local dynatrace_url="${DYNATRACE_SERVER}/e/${DYNATRACE_SPACE}/api/v1/events"
-  local description="NetData Notification for: ${host} ${chart}.${name} is ${status}"
+  local description="Netdata Notification for: ${host} ${chart}.${name} is ${status}"
   local payload=""
 
   payload=$(cat <<EOF
 {
-  "title": "NetData Alarm from ${host}",
+  "title": "Netdata Alarm from ${host}",
   "source" : "${DYNATRACE_ANNOTATION_TYPE}",
   "description" : "${description}",
   "eventType": "${DYNATRACE_EVENT}",
diff --git a/health/notifications/health_alarm_notify.conf b/health/notifications/health_alarm_notify.conf
index e851a530ca..873c7c353f 100755
--- a/health/notifications/health_alarm_notify.conf
+++ b/health/notifications/health_alarm_notify.conf
@@ -253,13 +253,13 @@ DYNATRACE_TOKEN=""
 DYNATRACE_SPACE=""
 
 # Generate a Server Tag. On the Dynatrace Server go to Settings --> Tags --> Manually applied tags create the Tag
-# The NetData alarm will be sent as a Dynatrace Event to be correlated with all those hosts tagged with this Tag 
+# The Netdata alarm will be sent as a Dynatrace Event to be correlated with all those hosts tagged with this Tag
 # you created.
 # Required
 DYNATRACE_TAG_VALUE=""
 
 # Change this to what you want
-DYNATRACE_ANNOTATION_TYPE="NetData Alarm"
+DYNATRACE_ANNOTATION_TYPE="Netdata Alarm"
 
 # This can be CUSTOM_INFO, CUSTOM_ANNOTATION, CUSTOM_CONFIGURATION, CUSTOM_DEPLOYMENT
 # Applying default value
diff --git a/web/api/netdata-swagger.json b/web/api/netdata-swagger.json
index 2beaee92f5..5c2bba9a85 100644
--- a/web/api/netdata-swagger.json
+++ b/web/api/netdata-swagger.json
@@ -1,7 +1,7 @@
 {
   "openapi": "3.0.0",
   "info": {
-    "title": "NetData API",
+    "title": "Netdata API",
     "description": "Real-time performance and health monitoring.",
     "version": "1.11.1_rolling"
   },
@@ -1343,7 +1343,7 @@
           },
           "priority": {
             "type": "number",
-            "description": "The relative priority of the chart. NetData does not care about priorities. This is just an indication of importance for the chart viewers to sort charts of higher priority (lower number) closer to the top. Priority sorting should only be used among charts of the same type or family."
+            "description": "The relative priority of the chart. Netdata does not care about priorities. This is just an indication of importance for the chart viewers to sort charts of higher priority (lower number) closer to the top. Priority sorting should only be used among charts of the same type or family."
           },
           "enabled": {
             "type": "boolean",
diff --git a/web/api/netdata-swagger.yaml b/web/api/netdata-swagger.yaml
index ebade7991b..062aa7ce5f 100644
--- a/web/api/netdata-swagger.yaml
+++ b/web/api/netdata-swagger.yaml
@@ -1,6 +1,6 @@
 openapi: 3.0.0
 info:
-  title: NetData API
+  title: Netdata API
   description: Real-time performance and health monitoring.
   version: 1.11.1_rolling
 paths:
@@ -1082,7 +1082,7 @@ components:
           description: The title of the chart.
         priority:
           type: number
-          description: The relative priority of the chart. NetData does not care about
+          description: The relative priority of the chart. Netdata does not care about
             priorities. This is just an indication of importance for the chart
             viewers to sort charts of higher priority (lower number) closer to
             the top. Priority sorting should only be used among charts of the
diff --git a/web/gui/dashboard/dashboard.html b/web/gui/dashboard/dashboard.html
index d843fc5cb3..c550db390e 100644
--- a/web/gui/dashboard/dashboard.html
+++ b/web/gui/dashboard/dashboard.html
@@ -2,7 +2,7 @@
 <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
 <html lang="en">
 <head>
-    <title>NetData Dashboard</title>
+    <title>Netdata Dashboard</title>
     <meta name="application-name" content="netdata">
 
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -25,7 +25,7 @@
 
 <div class="container-fluid">
 
-<h1>NetData Custom Dashboard <div data-netdata="system.cpu" data-chart-library="sparkline" data-height="30" data-after="-600" data-sparkline-linecolor="#888"></div></h1>
+<h1>Netdata Custom Dashboard <div data-netdata="system.cpu" data-chart-library="sparkline" data-height="30" data-after="-600" data-sparkline-linecolor="#888"></div></h1>
 
 This is a template for building custom dashboards. To build a dashboard you just do this:
 
@@ -518,8 +518,8 @@ Sparklines using dygraphs
 
 <hr>
 <h1>Google Charts</h1>
-NetData was originaly developed with Google Charts.
-NetData is a complete Google Visualization API provider.
+Netdata was originaly developed with Google Charts.
+Netdata is a complete Google Visualization API provider.
 <br/>
 <div style="width: 33%; display: inline-block;">
     <div data-netdata="system.processes"
diff --git a/web/gui/dashboard/demo.html b/web/gui/dashboard/demo.html
index b096bef336..642742a55e 100644
--- a/web/gui/dashboard/demo.html
+++ b/web/gui/dashboard/demo.html
@@ -2,7 +2,7 @@
 <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
 <html lang="en">
 <head>
-    <title>NetData Dashboard</title>
+    <title>Netdata Dashboard</title>
     <meta name="application-name" content="netdata">
 
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
diff --git a/web/gui/dashboard/demo2.html b/web/gui/dashboard/demo2.html
index 05ca72084b..9a77fdde53 100644
--- a/web/gui/dashboard/demo2.html
+++ b/web/gui/dashboard/demo2.html
@@ -2,7 +2,7 @@
 <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
 <html lang="en">
 <head>
-    <title>NetData Dashboard</title>
+    <title>Netdata Dashboard</title>
     <meta name="application-name" content="netdata">
 
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
diff --git a/web/gui/dashboard/demosites.html b/web/gui/dashboard/demosites.html
index b75e15e07a..59435c2b2d 100644
--- a/web/gui/dashboard/demosites.html
+++ b/web/gui/dashboard/demosites.html
@@ -4,7 +4,7 @@
 <head>
     <meta http-equiv="Refresh" content="0; url=https://www.netdata.cloud">
     <meta charset=utf-8>
-    <title>NetData: Get control of your Linux Servers. Simple. Effective. Awesome.</title>
+    <title>Netdata: Get control of your Linux Servers. Simple. Effective. Awesome.</title>
     <meta name=author content="Costa Tsaousis">
     <meta name=description content="Unparalleled insights, in real-time, of everything happening on your Linux systems and applications, with stunning, interactive web dashboards and powerful performance and health alarms.">
 
diff --git a/web/gui/dashboard/demosites2.html b/web/gui/dashboard/demosites2.html
index fe35cfb6d0..4b2be5c269 100644
--- a/web/gui/dashboard/demosites2.html
+++ b/web/gui/dashboard/demosites2.html
@@ -2,7 +2,7 @@
 <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
 <html lang="en">
 <head>
-    <title>NetData - Real-time performance monitoring, done right!</title>
+    <title>Netdata - Real-time performance monitoring, done right!</title>
     <meta name="application-name" content="netdata">
 
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
diff --git a/web/gui/dashboard/index-node-view.html b/web/gui/dashboard/index-node-view.html
index 6b3cdec3af..8483892ecb 100644
--- a/web/gui/dashboard/index-node-view.html
+++ b/web/gui/dashboard/index-node-view.html
@@ -2,7 +2,7 @@
 <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
 <html lang="en">
 <head>
-  <title>NetData TV Dashboard</title>
+  <title>Netdata TV Dashboard</title>
   <meta name="application-name" content="netdata">
 
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
diff --git a/web/gui/dashboard/infographic.html b/web/gui/dashboard/infographic.html
index 24ff8f4e6a..0d3f563754 100644
--- a/web/gui/dashboard/infographic.html
+++ b/web/gui/dashboard/infographic.html
@@ -3,7 +3,7 @@
 <html lang=en-us>
 <head>
     <meta charset=utf-8>
-    <title>NetData: Get control of your Linux Servers. Simple. Effective. Awesome.</title>
+    <title>Netdata: Get control of your Linux Servers. Simple. Effective. Awesome.</title>
     <meta name=author content="Costa Tsaousis">
     <meta name=description content="Unparalleled insights, in real-time, of everything happening on your Linux systems and applications, with stunning, interactive web dashboards and powerful performance and health alarms.">
 
diff --git a/web/gui/dashboard/tv-react.html b/web/gui/dashboard/tv-react.html
index 75a9a464ae..6d33e78c08 100644
--- a/web/gui/dashboard/tv-react.html
+++ b/web/gui/dashboard/tv-react.html
@@ -2,7 +2,7 @@
 <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
 <html lang="en">
 <head>
-    <title>NetData TV Dashboard</title>
+    <title>Netdata TV Dashboard</title>
     <meta name="application-name" content="netdata">
 
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
diff --git a/web/gui/dashboard/tv.html b/web/gui/dashboard/tv.html
index e15fb2e272..fa0aa51867 100644
--- a/web/gui/dashboard/tv.html
+++ b/web/gui/dashboard/tv.html
@@ -2,7 +2,7 @@
 <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
 <html lang="en">
 <head>
-    <title>NetData TV Dashboard</title>
+    <title>Netdata TV Dashboard</title>
     <meta name="application-name" content="netdata">
 
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
diff --git a/web/server/web_client.c b/web/server/web_client.c
index 5e3de38d5b..e4c6a0c89b 100644
--- a/web/server/web_client.c
+++ b/web/server/web_client.c
@@ -1177,7 +1177,7 @@ void web_client_build_http_header(struct web_client *w) {
         buffer_sprintf(w->response.header_output,
                        "HTTP/1.1 %d %s\r\n"
                        "Connection: %s\r\n"
-                       "Server: NetData Embedded HTTP Server %s\r\n"
+                       "Server: Netdata Embedded HTTP Server %s\r\n"
                        "Access-Control-Allow-Origin: %s\r\n"
                        "Access-Control-Allow-Credentials: true\r\n"
                        "Content-Type: %s\r\n"