From 21c6c12c524cb71f18e068c9bcf223cda0214b5f Mon Sep 17 00:00:00 2001
From: Vic <88121568+vicariousdrama@users.noreply.github.com>
Date: Wed, 11 Oct 2023 00:57:12 -0400
Subject: [PATCH] Update 57.md (#808)

Clarify how multiple relays should be included in the zap request event
---
 57.md | 4 ++--
 1 file 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