From e2d167c45f2e0f1f06cfa7cca378268915042481 Mon Sep 17 00:00:00 2001 From: HAOYUatHZ Date: Sat, 22 Feb 2020 17:03:27 +0800 Subject: [PATCH] fix typos --- communications_protocol.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/communications_protocol.asciidoc b/communications_protocol.asciidoc index ccaf8e1..67ee5ab 100644 --- a/communications_protocol.asciidoc +++ b/communications_protocol.asciidoc @@ -32,7 +32,7 @@ Lightning Messages follows two forethoughtful rules: "it's OK to be odd" rule an === "It's OK to be odd" rule -Lightning Message type follows the _it's ok to be odd_ rule. A node is allowed to send a message of an _odd_-numbered type, but not _even_-numbered type without prior negotiation. Once a node receives a _oddly_-but-unknown-typed message, it should ignore it. However, if it receives a _evenly_-but-unknown-typed message, it is expected to fail the channels. +Lightning Message type follows the _it's ok to be odd_ rule. A node is allowed to send a message of an _odd_-numbered type, but not _even_-numbered type without prior negotiation. Once a node receives an _oddly_-but-unknown-typed message, it should ignore it. However, if it receives an _evenly_-but-unknown-typed message, it is expected to fail the channels. === "Ignore additional data" rule