Apply suggestions from code review

Co-Authored-By: Hennadii Stepanov <32963518+hebasto@users.noreply.github.com>
bitcoin · Mar 30, 2020 · 080eff6 · 080eff6
1 parent fae5d88
commit 080eff6
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/doc/reduce-memory.md b/doc/reduce-memory.md
@@ -26,7 +26,7 @@ The size of some in-memory caches can be reduced. As caches trade off memory usa
 
 - `-maxconnections=<n>` - the maximum number of connections, this defaults to 125. Each active connection takes up some
   memory. This option applies only if incoming connections are enabled, otherwise the number of connections will never
-  be more than 10. Of the 10 outbound peers, there can be 8 full-relay connections and 2 block-relay-only peers.
+  be more than 10. Of the 10 outbound peers, there can be 8 full-relay connections and 2 block-relay-only ones.
 
 ## Thread configuration
 

diff --git a/doc/reduce-traffic.md b/doc/reduce-traffic.md
@@ -5,8 +5,8 @@ Some node operators need to deal with bandwidth caps imposed by their ISPs.
 
 By default, Bitcoin Core allows up to 125 connections to different peers, 10 of
 which are outbound. You can therefore, have at most 115 inbound connections.
-Of the 10 outbound peers, there can be 8 full-relay connections and 2 with
-block-relay only.
+Of the 10 outbound peers, there can be 8 full-relay connections and 2
+block-relay-only ones.
 
 The default settings can result in relatively significant traffic consumption.