diff --git a/README.md b/README.md
index b3e8e06a..bc22285c 100644
--- a/README.md
+++ b/README.md
@@ -69,10 +69,12 @@ Single-thread CPU performance will determine the max throughput of a single HTB
 | Customer Max Plan   | Passmark Single-Thread   |
 | --------------------| ------------------------ |
 | 100 Mbps            | 1000                     |
-| 250 Mbps            | 1500                     |
-| 500 Mbps            | 2000                     |
-| 1 Gbps              | 2500                     |
-| 2 Gbps              | 3000                     |
+| 250 Mbps            | 1250                     |
+| 500 Mbps            | 1500                     |
+| 1 Gbps              | 1750                     |
+| 2 Gbps              | 2000                     |
+| 3 Gbps              | 2500                     |
+| 4 Gbps              | 3000                     |
 
 Below is a table of approximate aggregate throughput capacity, assuming a a CPU with a [single thread](https://www.cpubenchmark.net/singleThread.html#server-thread) performance of 2700 or greater:
 
diff --git a/src/ispConfig.example.py b/src/ispConfig.example.py
index f9af8115..f3206383 100644
--- a/src/ispConfig.example.py
+++ b/src/ispConfig.example.py
@@ -17,6 +17,7 @@ upstreamBandwidthCapacityUploadMbps = 1000
 # Devices in ShapedDevices.csv without a defined ParentNode (such as if you have a flat {} network)
 # will be placed under one of these generated parent node, evenly spread out across CPU cores.
 # This defines the bandwidth limit for each of those generated parent nodes.
+# If you are not sure what values to use, simply use the same values as upstreamBandwidthCapacityDownloadMbps and upstreamBandwidthCapacityUploadMbps
 generatedPNDownloadMbps = 1000
 generatedPNUploadMbps = 1000