From 44c6071d186f9ec45f25512ae89d5a1fd46647c7 Mon Sep 17 00:00:00 2001
From: Hiroki Gondo <39823612+nayuta-gondo@users.noreply.github.com>
Date: Mon, 29 Jul 2019 16:31:07 +0900
Subject: [PATCH] BOLT 2: correct `next_remote_revocation_number` to
 `next_revocation_number` (#652)

---
 02-peer-protocol.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/02-peer-protocol.md b/02-peer-protocol.md
index ee4a3cf..43e3847 100644
--- a/02-peer-protocol.md
+++ b/02-peer-protocol.md
@@ -1167,7 +1167,7 @@ The sending node:
   - MUST set `next_revocation_number` to the commitment number of the
   next `revoke_and_ack` message it expects to receive.
   - if it supports `option_data_loss_protect`:
-    - if `next_remote_revocation_number` equals 0:
+    - if `next_revocation_number` equals 0:
       - MUST set `your_last_per_commitment_secret` to all zeroes
     - otherwise:
       - MUST set `your_last_per_commitment_secret` to the last `per_commitment_secret`