[pull] master from netdata:master

README.md

@@ -233,7 +233,7 @@ By default, Netdata will send e-mail notifications if there is a configured MTA
 
 ### 4. **Configure Netdata Parents** :family:
 
-Optionally, configure one or more Netdata Parents. A Netdata Parent is a Netdata Agent that has been configured to accept [streaming connections](https://learn.netdata.cloud/docs/streaming/streaming-configuration-reference) from other Netdata agents.
+Optionally, configure one or more Netdata Parents. A Netdata Parent is a Netdata Agent that has been configured to accept [streaming connections](https://learn.netdata.cloud/docs/streaming/streaming-configuration-reference) from other Netdata Agents.
 
 Netdata Parents provide:
 
@@ -264,8 +264,8 @@ If you connect your Netdata Parents, there is no need to connect your Netdata Ag
 
 When your Netdata nodes are connected to Netdata Cloud, you can (on top of the above):
 
-- Access your Netdata agents from anywhere
-- Access sensitive Netdata agent features (like "Netdata Functions": processes, systemd-journal)
+- Access your Netdata Agents from anywhere
+- Access sensitive Netdata Agent features (like "Netdata Functions": processes, systemd-journal)
 - Organize your infra in spaces and Rooms
 - Create, manage, and share **custom dashboards**
 - Invite your team and assign roles to them (Role-Based Access Control)
@@ -573,7 +573,7 @@ Here are some suggestions on how to manage and navigate this wealth of informati
    If you're looking for specific information, you can use the search feature to find the relevant metrics or charts. This can help you avoid scrolling through all the data.
 
 3. **Customize your Dashboards**<br/>
-   Netdata allows you to create custom dashboards, which can help you focus on the metrics that are most important to you. Sign-in to Netdata and there you can have your custom dashboards. (coming soon to the agent dashboard too)
+   Netdata allows you to create custom dashboards, which can help you focus on the metrics that are most important to you. Sign-in to Netdata and there you can have your custom dashboards. (coming soon to the Agent dashboard too)
 
 4. **Leverage Netdata's Anomaly Detection**<br/>
    Netdata uses machine learning to detect anomalies in your metrics. This can help you identify potential issues before they become major problems. We have added an `AR` button above the dashboard table of contents to reveal the anomaly rate per section so that you can spot what could need your attention.
@@ -633,7 +633,7 @@ We are aware that for privacy or regulatory reasons, not all environments can al
 
 These steps will disable the anonymous telemetry for your Netdata installation.
 
-Please note, even with telemetry disabled, Netdata still requires a [Netdata Registry](https://learn.netdata.cloud/docs/configuring/securing-netdata-agents/registry) for alert notifications' Call To Action (CTA) functionality. When you click an alert notification, it redirects you to the Netdata Registry, which then directs your web browser to the specific Netdata Agent that issued the alert for further troubleshooting. The Netdata Registry learns the URLs of your agents when you visit their dashboards.
+Please note, even with telemetry disabled, Netdata still requires a [Netdata Registry](https://learn.netdata.cloud/docs/configuring/securing-netdata-agents/registry) for alert notifications' Call To Action (CTA) functionality. When you click an alert notification, it redirects you to the Netdata Registry, which then directs your web browser to the specific Netdata Agent that issued the alert for further troubleshooting. The Netdata Registry learns the URLs of your Agents when you visit their dashboards.
 
 Any Netdata Agent can act as a Netdata Registry. Designate one Netdata Agent as your registry, and our global Netdata Registry will no longer be in use. For further information on this, please refer to [this guide](https://learn.netdata.cloud/docs/configuring/securing-netdata-agents/registry).
 

docs/alerts-and-notifications/notifications/README.md

@@ -6,4 +6,4 @@ This section includes the documentation of the integrations for both of Netdata'
 
 - Netdata Cloud provides centralized alert notifications, utilizing the health status data already sent to Netdata Cloud from connected nodes to send alerts to configured integrations. [Supported integrations](/docs/alerts-&-notifications/notifications/centralized-cloud-notifications) include Amazon SNS, Discord, Slack, Splunk, and others.
 
-- The Netdata Agent offers a [wider range of notification options](/docs/alerts-&-notifications/notifications/agent-dispatched-notifications) directly from the agent itself. You can choose from over a dozen services, including email, Slack, PagerDuty, Twilio, and others, for more granular control over notifications on each node.
+- The Netdata Agent offers a [wider range of notification options](/docs/alerts-&-notifications/notifications/agent-dispatched-notifications) directly from the Agent itself. You can choose from over a dozen services, including email, Slack, PagerDuty, Twilio, and others, for more granular control over notifications on each node.

docs/dashboards-and-charts/README.md

@@ -25,7 +25,7 @@ The Netdata dashboard consists of the following main sections:
 
 > **Note**
 >
-> Some sections of the dashboard, when accessed through the agent, may require the user to be signed in to Netdata Cloud or have the Agent claimed to Netdata Cloud for their full functionality. Examples include saving visualization settings on charts or custom dashboards, claiming the node to Netdata Cloud, or executing functions on an Agent.
+> Some sections of the dashboard, when accessed through the Agent, may require the user to be signed in to Netdata Cloud or have the Agent claimed to Netdata Cloud for their full functionality. Examples include saving visualization settings on charts or custom dashboards, claiming the node to Netdata Cloud, or executing functions on an Agent.
 
 ## How to access the dashboards?
 

docs/dashboards-and-charts/events-feed.md

@@ -49,8 +49,8 @@ At a high-level view, these are the domains from which the Events feed will prov
 | Node Removed        | The node was removed from the Space, for example by using the `Delete` action on the node. This is a soft delete in that the node gets marked as deleted, but retains the association with this space. If it becomes live again, it will be restored (see `Node Restored` below) and reappear in this space as before. | Node `ip-xyz.ec2.internal` was **deleted (soft)**                                                               |
 | Node Restored       | The node was restored. See `Node Removed` above.                                                                                                                                                                                                                                                                       | Node `ip-xyz.ec2.internal` was **restored**                                                                     |
 | Node Deleted        | The node was deleted from the Space. This is a hard delete and no information on the node is retained.                                                                                                                                                                                                                 | Node `ip-xyz.ec2.internal` was **deleted (hard)**                                                               |
-| Agent Connected     | The agent connected to the Cloud MQTT server (Agent-Cloud Link established).<br/>These events can only be seen on _All nodes_  Room.                                                                                                                                                                                   | Agent with claim ID `7d87bqs9-cv42-4823-8sd4-3614548850c7` has connected to Cloud.                              |
-| Agent Disconnected  | The agent disconnected from the Cloud MQTT server (Agent-Cloud Link severed).<br/>These events can only be seen on _All nodes_ Room.                                                                                                                                                                                   | Agent with claim ID `7d87bqs9-cv42-4823-8sd4-3614548850c7` has disconnected from Cloud: **Connection Timeout**. |
+| Agent Connected     | The Agent connected to the Cloud MQTT server (Agent-Cloud Link established).<br/>These events can only be seen on _All nodes_  Room.                                                                                                                                                                                   | Agent with claim ID `7d87bqs9-cv42-4823-8sd4-3614548850c7` has connected to Cloud.                              |
+| Agent Disconnected  | The Agent disconnected from the Cloud MQTT server (Agent-Cloud Link severed).<br/>These events can only be seen on _All nodes_ Room.                                                                                                                                                                                   | Agent with claim ID `7d87bqs9-cv42-4823-8sd4-3614548850c7` has disconnected from Cloud: **Connection Timeout**. |
 | Space Statistics    | Daily snapshot of space node statistics.<br/>These events can only be seen on _All nodes_ Room.                                                                                                                                                                                                                        | Space statistics. Nodes: **22 live**, **21 stale**, **18 removed**, **61 total**.                               |
 
 ### Alert events

docs/dashboards-and-charts/netdata-charts.md

@@ -274,7 +274,7 @@ Finally, you can reset everything to its defaults by clicking the green "Reset"
 
 ## Anomaly Rate ribbon
 
-Netdata's unsupervised machine learning algorithm creates a unique model for each metric collected by your agents, using exclusively the metric's past data.
+Netdata's unsupervised machine learning algorithm creates a unique model for each metric collected by your Agents, using exclusively the metric's past data.
 It then uses these unique models during data collection to predict the value that should be collected and check if the collected value is within the range of acceptable values based on past patterns and behavior.
 
 If the value collected is an outlier, it is marked as anomalous.

docs/developer-and-contributor-corner/style-guide.md

@@ -160,8 +160,7 @@ capitalization. In summary:
   Docker, Apache, NGINX)
 - Avoid camel case (NetData) or all caps (NETDATA).
 
-Whenever you refer to the company Netdata, Inc., or the open-source monitoring agent the company develops, capitalize
-**Netdata**.
+Whenever you refer to the company Netdata, Inc., or the open-source monitoring Agent the company develops, capitalize both words.
 
 However, if you are referring to a process, user, or group on a Linux system, use lowercase and fence the word in an
 inline code block: `` `netdata` ``.

docs/glossary.md

@@ -128,7 +128,7 @@ metrics, troubleshoot complex performance problems, and make data interoperable
 
 ## S
 
-- [**Single Node Dashboard**](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md): A dashboard pre-configured with every installation of the Netdata agent, with thousand of metrics and hundreds of interactive charts that requires no set up.
+- [**Single Node Dashboard**](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md): A dashboard pre-configured with every installation of the Netdata Agent, with thousand of metrics and hundreds of interactive charts that requires no set up.
 
 - [**Space**](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces): A high-level container and virtual collaboration area where you can organize team members, access levels,and the nodes you want to monitor.
 

docs/netdata-agent/README.md

@@ -59,7 +59,7 @@ stateDiagram-v2
 6. **Check**: a health engine, triggering alerts and sending notifications. Netdata comes with hundreds of alert configurations that are automatically attached to metrics when they get collected, detecting errors, common configuration errors and performance issues.
 7. **Query**: a query engine for querying time-series data.
 8. **Score**: a scoring engine for comparing and correlating metrics.
-9. **Stream**: a mechanism to connect Netdata agents and build Metrics Centralization Points (Netdata Parents).
+9. **Stream**: a mechanism to connect Netdata Agents and build Metrics Centralization Points (Netdata Parents).
 10. **Visualize**: Netdata's fully automated dashboards for all metrics.
 11. **Export**: export metric samples to 3rd party time-series databases, enabling the use of 3rd party tools for visualization, like Grafana.
 
@@ -77,8 +77,8 @@ stateDiagram-v2
 
 ## Dashboard Versions
 
-The Netdata agents (Standalone, Children and Parents) **share the dashboard** of Netdata Cloud. However, when the user is logged in and the Netdata agent is connected to Netdata Cloud, the following are enabled (which are otherwise disabled):
+The Netdata Agents (Standalone, Children and Parents) **share the dashboard** of Netdata Cloud. However, when the user is logged in and the Agent is connected to the Cloud, the following are enabled (which are otherwise disabled):
 
-1. **Access to Sensitive Data**: Some data, like systemd-journal logs and several [Top Monitoring](/docs/top-monitoring-netdata-functions.md) features expose sensitive data, like IPs, ports, process command lines and more. To access all these when the dashboard is served directly from a Netdata agent, Netdata Cloud is required to verify that the user accessing the dashboard has the required permissions.
+1. **Access to Sensitive Data**: Some data, like systemd-journal logs and several [Top Monitoring](/docs/top-monitoring-netdata-functions.md) features expose sensitive data, like IPs, ports, process command lines and more. To access all these when the dashboard is served directly from an Agent, Netdata Cloud is required to verify that the user accessing the dashboard has the required permissions.
 
-2. **Dynamic Configuration**: Netdata agents are configured via configuration files, manually or through some provisioning system. The latest Netdata includes a feature to allow users to change some configurations (collectors, alerts) via the dashboard. This feature is only available to users of paid Netdata Cloud plan.
+2. **Dynamic Configuration**: Netdata Agents are configured via configuration files, manually or through some provisioning system. The latest Netdata includes a feature to allow users to change some configurations (collectors, alerts) via the dashboard. This feature is only available to users of paid Netdata Cloud plan.

docs/netdata-agent/backup-and-restore-an-agent.md

@@ -34,18 +34,18 @@ In this standard scenario, you’re backing up your Netdata Agent in case of a n
    sudo tar -cvpzf netdata_backup.tar.gz /etc/netdata/ /var/cache/netdata /var/lib/netdata
    ```
 
-   Stopping the Netdata agent is typically necessary to back up the database files of the Netdata Agent.
+   Stopping the Netdata Agent is typically necessary to back up the database files of the Netdata Agent.
 
 If you want to minimize the gap in metrics caused by stopping the Netdata Agent, consider implementing a backup job or script that follows this sequence:
 
 - Backup the Agent configuration Identity directories
 - Stop the Netdata service
 - Backup up the database files
-- Restart the netdata agent.
+- Restart the Netdata Agent.
 
 ### Restoring Netdata
 
-1. Ensure that the Netdata agent is installed and is [stopped](/docs/netdata-agent/start-stop-restart.md)
+1. Ensure that the Netdata Agent is installed and is [stopped](/docs/netdata-agent/start-stop-restart.md)
 
    If you plan to deploy the Agent and restore a backup on top of it, then you might find it helpful to use the [`--dont-start-it`](/packaging/installer/methods/kickstart.md#other-options) option upon installation.
 
@@ -66,4 +66,4 @@ If you want to minimize the gap in metrics caused by stopping the Netdata Agent,
     sudo tar -xvpzf /path/to/netdata_backup.tar.gz -C /
     ```
 
-3. [Start the Netdata agent](/docs/netdata-agent/start-stop-restart.md)
+3. [Start the Netdata Agent](/docs/netdata-agent/start-stop-restart.md)

docs/netdata-agent/configuration/anonymous-telemetry-events.md

@@ -1,7 +1,6 @@
 # Anonymous telemetry events
 
-By default, Netdata collects anonymous usage information from the open-source monitoring agent. For agent events like start, stop, crash, etc. we use our own cloud function in GCP. For frontend telemetry (page views etc.) on the agent dashboard itself, we use the open-source
-product analytics platform [PostHog](https://github.com/PostHog/posthog).
+By default, Netdata collects anonymous usage information from the open-source monitoring Agent. For events like start, stop, crash, etc. we use our own cloud function in GCP. For frontend telemetry (page views etc.) on the dashboard itself, we use the open-source product analytics platform [PostHog](https://github.com/PostHog/posthog).
 
 We are strongly committed to your [data privacy](https://netdata.cloud/privacy/).
 
@@ -10,7 +9,7 @@ We use the statistics gathered from this information for two purposes:
 1. **Quality assurance**, to help us understand if Netdata behaves as expected, and to help us classify repeated
    issues with certain distributions or environments.
 
-2. **Usage statistics**, to help us interpret how people use the Netdata agent in real-world environments, and to help
+2. **Usage statistics**, to help us interpret how people use the Netdata Agent in real-world environments, and to help
    us identify how our development/design decisions influence the community.
 
 Netdata collects usage information via two different channels:
@@ -59,7 +58,7 @@ filename and source code line number of the fatal error.
 Starting with v1.21, we additionally collect information about:
 
 - Failures to build the dependencies required to use Cloud features.
-- Unavailability of Cloud features in an agent.
+- Unavailability of Cloud features in an Agent.
 - Failures to connect to the Cloud in case the [connection process](/src/claim/README.md) has been completed. This includes error codes
   to inform the Netdata team about the reason why the connection failed.