1 files changed, 2 insertions, 2 deletions
diff --git a/57.md b/57.md
index 8e2be1b..849c869 100644
--- a/57.md
+++ b/57.md
@@ -45,7 +45,7 @@ Example:
  "kind": 9734,
  "content": "Zap!",
  "tags": [
-    ["relays", "wss://nostr-pub.wellorder.com"],
+    ["relays", "wss://nostr-pub.wellorder.com", "wss://anotherrelay.example.com"],
    ["amount", "21000"],
    ["lnurl", "lnurl1dp68gurn8ghj7um5v93kketj9ehx2amn9uh8wetvdskkkmn0wahz7mrww4excup0dajx2mrv92x9xp"],
    ["p", "04c915daefee38317fa734444acee390a8269fe5810b2241e5e6dd343dfbecc9"],
@@ -66,7 +66,7 @@ A signed `zap request` event is not published, but is instead sent using a HTTP
 - `nostr` is the `9734` `zap request` event, JSON encoded then URI encoded
 - `lnurl` is the lnurl pay url of the recipient, encoded using bech32 with the prefix `lnurl`
-This request should return a JSON response with a `pr` key, which is the invoice the sender must pay to finalize his zap. Here is an example flow:
+This request should return a JSON response with a `pr` key, which is the invoice the sender must pay to finalize his zap. Here is an example flow in javascript:
 ```javascript
 const senderPubkey // The sender's pubkey

diff --git a/57.md b/57.md index 8e2be1b..849c869 100644 --- a/57.md +++ b/57.md
@@ -45,7 +45,7 @@ Example:
45	"kind": 9734,	45	"kind": 9734,
46	"content": "Zap!",	46	"content": "Zap!",
47	"tags": [	47	"tags": [
48	["relays", "wss://nostr-pub.wellorder.com"],	48	["relays", "wss://nostr-pub.wellorder.com", "wss://anotherrelay.example.com"],
49	["amount", "21000"],	49	["amount", "21000"],
50	["lnurl", "lnurl1dp68gurn8ghj7um5v93kketj9ehx2amn9uh8wetvdskkkmn0wahz7mrww4excup0dajx2mrv92x9xp"],	50	["lnurl", "lnurl1dp68gurn8ghj7um5v93kketj9ehx2amn9uh8wetvdskkkmn0wahz7mrww4excup0dajx2mrv92x9xp"],
51	["p", "04c915daefee38317fa734444acee390a8269fe5810b2241e5e6dd343dfbecc9"],	51	["p", "04c915daefee38317fa734444acee390a8269fe5810b2241e5e6dd343dfbecc9"],
@@ -66,7 +66,7 @@ A signed `zap request` event is not published, but is instead sent using a HTTP
66	- `nostr` is the `9734` `zap request` event, JSON encoded then URI encoded	66	- `nostr` is the `9734` `zap request` event, JSON encoded then URI encoded
67	- `lnurl` is the lnurl pay url of the recipient, encoded using bech32 with the prefix `lnurl`	67	- `lnurl` is the lnurl pay url of the recipient, encoded using bech32 with the prefix `lnurl`
68		68
69	This request should return a JSON response with a `pr` key, which is the invoice the sender must pay to finalize his zap. Here is an example flow:	69	This request should return a JSON response with a `pr` key, which is the invoice the sender must pay to finalize his zap. Here is an example flow in javascript:
70		70
71	```javascript	71	```javascript
72	const senderPubkey // The sender's pubkey	72	const senderPubkey // The sender's pubkey