From dd754e22a1f253eb751df714cef6a37aa27b0853 Mon Sep 17 00:00:00 2001
From: Jeff Gardner <202880+erskingardner@users.noreply.github.com>
Date: Tue, 26 Nov 2024 11:11:15 +0100
Subject: [PATCH] Smalll clarification on application messages

---
 104.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/104.md b/104.md
index 5f573a4..874f0b1 100644
--- a/104.md
+++ b/104.md
@@ -270,7 +270,7 @@ Application messages are the messages that are sent within the group by members.
 
 This means that once the application message has been decrypted and deserialized, clients can store those events and treat them as any other Nostr event, effectively creating a private Nostr feed of the group's activity and taking advantage of all the features of Nostr.
 
-The Nostr event MUST use the member's Nostr identity key for the `pubkey` field and clients MUST check that the identity of them member who sent the message matches the pubkey of the inner Nostr event.
+These inner unsigned Nostr events MUST use the member's Nostr identity key for the `pubkey` field and clients MUST check that the identity of them member who sent the message matches the pubkey of the inner Nostr event.
 
 These Nostr events MUST remain **unsigned** to ensure that if they were to leak to relays they would not be published publicly. These Nostr events MUST not include any "h" tags or other tags that would identify the group that they belong to.