From b09becc78aeafec7a703cb4336ea6be831d66d9c Mon Sep 17 00:00:00 2001 From: kaichao Date: Fri, 5 Jul 2024 11:39:26 +0800 Subject: [PATCH] Update standards/application/relay-reliability.md Co-authored-by: Hanno Cornelius <68783915+jm-clius@users.noreply.github.com> --- standards/application/relay-reliability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standards/application/relay-reliability.md b/standards/application/relay-reliability.md index 70e9898..18c8de4 100644 --- a/standards/application/relay-reliability.md +++ b/standards/application/relay-reliability.md @@ -16,7 +16,7 @@ However, there is no guarantee that a message broadcast in a Waku network will r For example, the receiver in a chat application using Waku as p2p transport may miss messages when a network issue happens at either the sender or the receiver side. -In general, a message in Waku network includes 3 status from sender's perspective: +In general, a message in a Waku network may be in one of 3 states from the sender's perspective: - **outgoing**, the message is posted by its creator but no confirmations from other nodes yet - **sent**, the message is received by any other node in the network