diff --git a/01.md b/01.md
index 1f56427448..b257f6f54d 100644
--- a/01.md
+++ b/01.md
@@ -158,7 +158,7 @@ Relays can send 5 types of messages, which must also be JSON arrays, according t
 
 This NIP defines no rules for how `NOTICE` messages should be sent or treated.
 
-- `EVENT` messages MUST be sent only with a subscription ID related to a subscription previously initiated by the client (using the `REQ` message above).
+- `EVENT` messages MUST be sent for each event that matches the latest `REQ` message with the same subscription id. When receiving an updated `REQ` for the same subscription id, relays MUST stop the stream of events related to the old subscription and start a new stream.
 - `OK` messages MUST be sent in response to `EVENT` messages received from clients, they must have the 3rd parameter set to `true` when an event has been accepted by the relay, `false` otherwise. The 4th parameter MUST always be present, but MAY be an empty string when the 3rd is `true`, otherwise it MUST be a string formed by a machine-readable single-word prefix followed by a `:` and then a human-readable message. Some examples:
   * `["OK", "b1a649ebe8...", true, ""]`
   * `["OK", "b1a649ebe8...", true, "pow: difficulty 25>=24"]`