1 files changed, 1 insertions, 1 deletions
diff --git a/57.md b/57.md
index 5414135..cb1f126 100644
--- a/57.md
+++ b/57.md
@@ -102,7 +102,7 @@ The lnurl server will need some additional pieces of information so that clients
 ### Appendix D: LNURL Server Zap Request Validation
-When a client sends a `zap request` event to a server's lnurl-pay callback URL, there will be a `nostr` query parameter where the contents of the event are URI- and JSON-encoded. If present, the `zap request` event must be validated in the following ways:
+When a client sends a `zap request` event to a server's lnurl-pay callback URL, there will be a `nostr` query parameter whose value is that event which is URI- and JSON-encoded. If present, the `zap request` event must be validated in the following ways:
 1. It MUST have a valid nostr signature
 2. It MUST have tags

diff --git a/57.md b/57.md index 5414135..cb1f126 100644 --- a/57.md +++ b/57.md
@@ -102,7 +102,7 @@ The lnurl server will need some additional pieces of information so that clients
102		102
103	### Appendix D: LNURL Server Zap Request Validation	103	### Appendix D: LNURL Server Zap Request Validation
104		104
105	When a client sends a `zap request` event to a server's lnurl-pay callback URL, there will be a `nostr` query parameter where the contents of the event are URI- and JSON-encoded. If present, the `zap request` event must be validated in the following ways:	105	When a client sends a `zap request` event to a server's lnurl-pay callback URL, there will be a `nostr` query parameter whose value is that event which is URI- and JSON-encoded. If present, the `zap request` event must be validated in the following ways:
106		106
107	1. It MUST have a valid nostr signature	107	1. It MUST have a valid nostr signature
108	2. It MUST have tags	108	2. It MUST have tags