fix typos

02-peer-protocol.md

@@ -430,7 +430,7 @@ along with the `scriptpubkey` it wants to be paid to.
 A sending node:
   - if it hasn't sent a `funding_created` (if it is a funder) or a `funding_signed` (if it is a fundee):
     - MUST NOT send a `shutdown`
-  - MAY send a `shutdown` before a `funding_locked`, i.e. before the funding transaction has reached `min_depth`.
+  - MAY send a `shutdown` before a `funding_locked`, i.e. before the funding transaction has reached `minimum_depth`.
   - if there are updates pending on the receiving node's commitment transaction:
     - MUST NOT send a `shutdown`.
   - MUST NOT send an `update_add_htlc` after a `shutdown`.

04-onion-routing.md

@@ -813,7 +813,7 @@ A _forwarding node_ MAY, but a _final node_ MUST NOT:
     - return an `invalid_onion_hmac` error.
   - if the ephemeral key in the onion is unparsable:
     - return an `invalid_onion_key` error.
-  - if, during forwarding to its receiving peer, an otherwise unspecified,
+  - if during forwarding to its receiving peer, an otherwise unspecified,
   transient error occurs in the outgoing channel (e.g. channel capacity reached,
   too many in-flight HTLCs, etc.):
     - return a `temporary_channel_failure` error.

07-routing-gossip.md

@@ -553,7 +553,7 @@ are unique 8-byte values, no more than 14 bytes can be duplicated
 across the stream: as each duplicate takes at least 2 bits, no valid
 contents could decompress to more then 3669960 bytes.
 
-### The `query_short_channel_ids`/`reply_short_channel_ids_done` Messages
+### The `query_short_channel_ids`/`reply_short_channel_ids_end` Messages
 
 1. type: 261 (`query_short_channel_ids`) (`gossip_queries`)
 2. data: