From c6c672aa15bdf3d1f80d34d7a8840edb2fe5e184 Mon Sep 17 00:00:00 2001
From: Bastien Teinturier <31281497+t-bast@users.noreply.github.com>
Date: Mon, 20 Jun 2022 21:32:00 +0200
Subject: [PATCH] Zero-conf typos and clarifications (#998)

A typo wasn't fixed before merging, and there was a confusion between
public and private channels in the rationale for `alias`.
---
 02-peer-protocol.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/02-peer-protocol.md b/02-peer-protocol.md
index afc63fd..d2063e5 100644
--- a/02-peer-protocol.md
+++ b/02-peer-protocol.md
@@ -549,10 +549,11 @@ to broadcast the commitment transaction to get his funds back and open a new
 channel. To avoid this, the funder should ensure the funding transaction
 confirms in the next 2016 blocks.
 
-The `alias` here is both required for routing (since there real
-short_channel_id is unknown until confirmation), and useful to provide
-one or more aliases, even once there is a real `short_channel_id` for
-a public channel.
+The `alias` here is required for two distinct use cases. The first one is
+for routing payments through channels that are not confirmed yet (since
+the real `short_channel_id` is unknown until confirmation). The second one
+is to provide one or more aliases to use for private channels (even once
+a real `short_channel_id` is available).
 
 While a node can send multiple `alias`, it must remember all of the
 ones it has sent so it can use them should they be requested by