From 3b065c3c0467def35f5d38a688a1adf98d944183 Mon Sep 17 00:00:00 2001
From: Josua Schmid <josua.schmid@renuo.ch>
Date: Tue, 26 Dec 2023 20:54:06 +0100
Subject: [PATCH] Reword REQ for multiple filters

---
 01.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/01.md b/01.md
index 0cf03ed8..eed20a5c 100644
--- a/01.md
+++ b/01.md
@@ -101,12 +101,12 @@ Relays expose a websocket endpoint to which clients can connect. Clients SHOULD
 Clients can send 3 types of messages, which must be JSON arrays, according to the following patterns:
 
   * `["EVENT", <event JSON as defined above>]`, used to publish events.
-  * `["REQ", <subscription_id>, <filters JSON>, ...]`, used to request events and subscribe to new updates.
+  * `["REQ", <subscription_id>, <filters1>, <filters2>, ...]`, used to request events and subscribe to new updates.
   * `["CLOSE", <subscription_id>]`, used to stop previous subscriptions.
 
 `<subscription_id>` is an arbitrary, non-empty string of max length 64 chars, that should be used to represent a subscription. Relays should manage `<subscription_id>`s independently for each WebSocket connection; even if `<subscription_id>`s are the same string, they should be treated as different subscriptions for different connections.
 
-`<filters>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes:
+`<filtersX>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes:
 
 ```json
 {