lncfg: update docs about msg-rate-bytes and msg-burst-bytes

sample-lnd.conf

@@ -1763,16 +1763,20 @@
 ; The number of confirmations required before processing channel announcements.
 ; gossip.announcement-conf=6
 
-; The allotted bandwidth rate expressed in bytes/second that will be allocated
-; towards outbound gossip messages. Realized rates above this value will be 
-; throttled. This value is shared across all peers.
-; gossip.msg-rate-bytes=102400
+; The total rate of outbound gossip messages, expressed in bytes per second.
+; This setting controls the long-term average speed of gossip traffic sent from
+; your node. The rate limit is applied globally across all peers, not per-peer.
+; If the rate of outgoing messages exceeds this value, lnd will start to queue
+; and delay messages to stay within the limit.
+; gossip.msg-rate-bytes=1024000
 
-; The amount of bytes of gossip messages that can be sent at a given time. This
-; is used as the amount of tokens in the token bucket algorithm. This value
-; MUST be set to something about 65 KB, otherwise a single max sized message
-; can never be sent.
-; gossip.msg-burst-bytes=204800
+; The maximum burst of outbound gossip data, in bytes, that can be sent at once.
+; This works in conjunction with `gossip.msg-rate-bytes` as part of a token
+; bucket rate-limiting scheme. This value represents the size of the token
+; bucket. It allows for short, high-speed bursts of traffic, with the long-term
+; rate controlled by `gossip.msg-rate-bytes`. This value must be larger than the
+; maximum lightning message size (~65KB) to allow sending large gossip messages.
+; gossip.msg-burst-bytes=2048000
 
 [invoices]