From 3581a439574818c4fefaa94041de18e6ff0ecf59 Mon Sep 17 00:00:00 2001
From: Vitor Pamplona <vitor@vitorpamplona.com>
Date: Thu, 28 Mar 2024 18:36:10 -0400
Subject: [PATCH] slight changes to the text.

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

diff --git a/59.md b/59.md
index d8690d26..8277c8b8 100644
--- a/59.md
+++ b/59.md
@@ -78,7 +78,7 @@ Relays MAY choose not to store Gift-wrapped events due to them not being publicl
 to attach a certain amount of proof-of-work to the wrapper event per [NIP-13](13.md) in a bid to demonstrate that
 the event is not spam or a denial-of-service attack.
 
-# Most Private Protocol
+# Privacy-first Protocol
 
 In cases of elevated privacy needs, the 3 primitives can be used together, one after another. In this scheme, even if all of the decrypted payloads leak, the sender and receiver are not publicly connected in a verifiable event and none of the inner event's information can be publicly verified.
 
@@ -107,7 +107,7 @@ In pseudo-code:
     "tags": [],
     "content": nip44Encrypt(rumor, pubkeyB, privkeyA),
     "sig": "<signed by pubkey-A>"
-  }, pubkeyB, privkeyRandom)
+  }, pubkeyB, privkeyRandom),
   "sig": "<random, one-time-use pubkey signature>"
 }
 ```
@@ -129,7 +129,7 @@ For instance, to send an event through a push notification stack without the sta
   "created_at": randomTimeUpTo2DaysInThePast()
   "kind": 1059,
   "tags": [
-    ["token", "<destination push notification token>"],
+    ["token", "<destination's push notification token>"],
   ],
   "content": nip44Encrypt(notificationEvent, pubkeyB, privkeyRandom)
   "sig": "<random, one-time-use pubkey signature>"