Merge bitcoin/bitcoin#22080: doc: add maxuploadtarget to bitcoin.conf example

947f973 doc: add maxuploadtarget to bitcoin.conf example (apitko)

Pull request description:

  picking up #21499, author has stated they [can't squash](bitcoin/bitcoin#21499 (comment)).

  This adds the maxuploadtarget option to the `bitcoin.conf` example file. This is useful for those looking to configure their bandwidth utilization.

  **Changes from Original PR:**
  - squash commits
  - fix typo in commit message + reword commit message to be more appropriate
  - Implement review suggestions ([1](bitcoin/bitcoin#21499 (comment)), [2](bitcoin/bitcoin#21499 (comment)), [3](bitcoin/bitcoin#21499 (review)))
  - Fix spacing

ACKs for top commit:
  jonatack:
    ACK 947f973
  theStack:
    re-ACK 947f973

Tree-SHA512: 658ce6e1f204cd1c1c6f8977fd46ba1631f417d3f492e6d777b0ca49ffecc2ecfa4fbd86ca0e08c0dd5d6df4e32f0b56693e0a71bd7eafafd019e93bbcf9420f

Author: MarcoFalke

share/examples/bitcoin.conf

@@ -71,6 +71,12 @@
 # configuration option or the addnode RPC, which have a separate limit of 8 connections.
 #maxconnections=
 
+# Maximum upload bandwidth target in MiB per day (e.g. 'maxuploadtarget=1024' is 1 GiB per day).
+# This limits the upload bandwidth for those with bandwidth limits. 0 = no limit (default: 0).
+# -maxuploadtarget does not apply to peers with 'download' permission.
+# For more information on reducing bandwidth utilization, see: doc/reduce-traffic.md.
+#maxuploadtarget=
+
 #
 # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
 #