1 files changed, 1 insertions, 1 deletions
diff --git a/01.md b/01.md
index 99c991a..0cf03ed 100644
--- a/01.md
+++ b/01.md
@@ -101,7 +101,7 @@ 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>, <filters JSON>, ...]`, 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.

diff --git a/01.md b/01.md index 99c991a..0cf03ed 100644 --- a/01.md +++ b/01.md
@@ -101,7 +101,7 @@ Relays expose a websocket endpoint to which clients can connect. Clients SHOULD
101	Clients can send 3 types of messages, which must be JSON arrays, according to the following patterns:	101	Clients can send 3 types of messages, which must be JSON arrays, according to the following patterns:
102		102
103	* `["EVENT", <event JSON as defined above>]`, used to publish events.	103	* `["EVENT", <event JSON as defined above>]`, used to publish events.
104	* `["REQ", <subscription_id>, <filters JSON>...]`, used to request events and subscribe to new updates.	104	* `["REQ", <subscription_id>, <filters JSON>, ...]`, used to request events and subscribe to new updates.
105	* `["CLOSE", <subscription_id>]`, used to stop previous subscriptions.	105	* `["CLOSE", <subscription_id>]`, used to stop previous subscriptions.
106		106
107	`<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.	107	`<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.