From cf73589155b5db5fbaedac65bfd17172b6112992 Mon Sep 17 00:00:00 2001
From: Vitor Pamplona <vitor@vitorpamplona.com>
Date: Fri, 16 Feb 2024 10:22:03 -0500
Subject: [PATCH] minor text adjusments

---
 22.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/22.md b/22.md
index 9b65df46..094a6291 100644
--- a/22.md
+++ b/22.md
@@ -6,11 +6,11 @@ Key Migration
 
 `draft` `optional`
 
-Kind 18 informs the network that the owner of the pubkey is migrating to a new key. The event MUST contain a single `p` tag with the new pubkey to be used to communicate with the owner. 
+Kind 18 informs the network that the owner of the pubkey is migrating to a new key. The event MUST contain a single `p` tag with the new pubkey owner will be using. 
 
 ```js
 {
-  "kind": 18,
+  "kind": 18,   
   "tags": [
     ["p", "<pubkey>", "<relay_url>"],
   ],
@@ -48,4 +48,4 @@ It's ok to delay verification until trusted keys start informing their assessmen
 Upon verification, Clients SHOULD offer transition to the new key by: 
 1. Changing the contact list accordingly
 2. Changing any NIP-51 list accordingly 
-3. Adding the key to the Mute List
+3. Adding the old key to the Mute List