fixup! WIP: BOLT 7: Onion message support.

lightning · Mar 3, 2021 · 5551ab8 · 5551ab8
1 parent 1f00905
commit 5551ab8
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/04-onion-routing.md b/04-onion-routing.md
@@ -414,7 +414,7 @@ The writer:
 - For the non-final nodes' `onionmsg_payload`:
   - MUST include exactly one of `next_short_channel_id`, `next_node_id`
     or `enctlv` indicating the next node.
-- For the the final node's `onionmsg_payload`:
+- For the final node's `onionmsg_payload`:
   - if the final node is permitted to reply:
     - MUST set `reply_path` `blinding` to the initial blinding factor for the `next_node_id`
     - For the first `reply_path` `path`:

diff --git a/07-routing-gossip.md b/07-routing-gossip.md
@@ -1130,7 +1130,7 @@ end-to-end encryption.
 
 Onion messages are unreliable: in particular, they are designed to
 be cheap to process and require no storage to forward.  As a result,
-there is no error return from intermediary nodes.
+there is no error returned from intermediary nodes.
 
 To enable messaging via blinded paths, there is an optional `blinding`
 parameter which allows decryption of the `enctlv` field inside the
@@ -1141,7 +1141,7 @@ parameter which allows decryption of the `enctlv` field inside the
 1. type: 385 (`onion_message`) (`option_onion_messages`)
 2. data:
     * [`1366*byte`:`onionmsg`]
-	* [`onion_message_tlvs`:`onion_message_tlvs`]
+    * [`onion_message_tlvs`:`onion_message_tlvs`]
 
 1. tlvs: `onion_message_tlvs`
 2. types: