From 82989a5c2bf10218e7c9a4b52db8528462dcc952 Mon Sep 17 00:00:00 2001
From: ok300 <106775972+ok300@users.noreply.github.com>
Date: Sun, 18 Jun 2023 19:56:12 +0200
Subject: [PATCH] NIP-47: Clarify `relay` usage

---
 47.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/47.md b/47.md
index c884b97..de5fe13 100644
--- a/47.md
+++ b/47.md
@@ -82,7 +82,7 @@ If the command was succesful, the `error` field must be null.
 
 The **wallet service** generates this connection URI with protocol `nostr+walletconnect:` and base path it's hex-encoded `pubkey` with the following query string parameters: 
 
-- `relay` Required. URL of the relay where the **wallet service** is connected and will be listening for events. May be more than one.
+- `relay` Required. URL of the relay where the **wallet service** is connected and will be listening for events. The URL should have no trailing slash. Multiple relays can be specified by repeating the `relay` parameter.
 - `secret` Required. 32-byte randomly generated hex encoded string. The **client** MUST use this to sign events and encrypt payloads when communicating with the **wallet service**.
     - Authorization does not require passing keys back and forth.
     - The user can have different keys for different applications. Keys can be revoked and created at will and have arbitrary constraints (eg. budgets).