Adding upstream version 2.0.0.upstream/2.0.0upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 6 insertions, 6 deletions

diff --git a/docs/netdata-agent/sizing-netdata-agents/bandwidth-requirements.md b/docs/netdata-agent/sizing-netdata-agents/bandwidth-requirements.md
index 092c8da1..fbbc279d 100644
--- a/docs/netdata-agent/sizing-netdata-agents/bandwidth-requirements.md
+++ b/docs/netdata-agent/sizing-netdata-agents/bandwidth-requirements.md
@@ -1,16 +1,16 @@
 # Bandwidth Requirements
 
-## On Production Systems, Standalone Netdata
+## Production Systems: Standalone Netdata
 
 Standalone Netdata may use network bandwidth under the following conditions:
 
-1. You configured data collection jobs that are fetching data from remote systems. There is no such jobs enabled by default.
+1. You configured data collection jobs that are fetching data from remote systems. There are no such jobs enabled by default.
 2. You use the dashboard of the Netdata.
 3. [Netdata Cloud communication](#netdata-cloud-communication) (see below).
 
-## On Metrics Centralization Points, between Netdata Children & Parents
+## Metrics Centralization Points: Between Netdata Children & Parents
 
-Netdata supports multiple compression algorithms for streaming communication. Netdata Children offer all their compression algorithms when connecting to a Netdata Parent, and the Netdata Parent decides which one to use based on algorithms availability and user configuration.
+Netdata supports multiple compression algorithms for streaming communication. Netdata Children offer all their compression algorithms when connecting to a Netdata Parent, and the Netdata Parent decides which one to use based on algorithm availability and user configuration.
 
 | Algorithm |                                                              Best for                                                               |
 |:---------:|:-----------------------------------------------------------------------------------------------------------------------------------:|
@@ -23,7 +23,7 @@ The expected bandwidth consumption using `zstd` for 1 million samples per second
 
 The order compression algorithms is selected is configured in `stream.conf`, per `[API KEY]`, like this:
 
-```
+```text
     compression algorithms order = zstd lz4 brotli gzip
 ```
 
@@ -42,6 +42,6 @@ The information transferred to Netdata Cloud is:
 3. Information about the **metrics available and their retention**.
 4. Information about the **configured alerts and their transitions**.
 
-This is not a constant stream of information. Netdata Agents update Netdata Cloud only about status changes on all the above (e.g. an alert being triggered, or a metric stopped being collected). So, there is an initial handshake and exchange of information when Netdata starts, and then there only updates when required.
+This is not a constant stream of information. Netdata Agents update Netdata Cloud only about status changes on all the above (e.g., an alert being triggered, or a metric stopped being collected). So, there is an initial handshake and exchange of information when Netdata starts, and then there only updates when required.
 
 Of course, when you view Netdata Cloud dashboards that need to query the database a Netdata agent maintains, this query is forwarded to an agent that can satisfy it. This means that Netdata Cloud receives metric samples only when a user is accessing a dashboard and the samples transferred are usually aggregations to allow rendering the dashboards.