1 files changed, 3 insertions, 1 deletions
diff --git a/91.md b/91.md
index f18ef15..9029216 100644
--- a/91.md
+++ b/91.md
@@ -34,7 +34,9 @@ The first entry MUST be an object, with the keys being protocol names, and the v
 A protocol offer can be sent multiple times in a connection, such as to update availability based off of their [NIP-42](./42.md) authentication status.
-Clients SHOULD be able to handle protocol offers being able to be withdrawn. The removal of a protocol from a `PN-OFFER` does not affect existing active protocols, a `PN-SHUTDOWN` must be sent if that is required. 
+Clients SHOULD be able to handle protocol offers being able to be withdrawn, and should treat them as if it was a `PN-SHUTDOWN` if they were in use. 
+Certain protocols, such as extensions to REQs, may not need negotiation. This is up to the specification of the specific protocol.
 ## Protocol Requests

diff --git a/91.md b/91.md index f18ef15..9029216 100644 --- a/91.md +++ b/91.md
@@ -34,7 +34,9 @@ The first entry MUST be an object, with the keys being protocol names, and the v
34		34
35	A protocol offer can be sent multiple times in a connection, such as to update availability based off of their [NIP-42](./42.md) authentication status.	35	A protocol offer can be sent multiple times in a connection, such as to update availability based off of their [NIP-42](./42.md) authentication status.
36		36
37	Clients SHOULD be able to handle protocol offers being able to be withdrawn. The removal of a protocol from a `PN-OFFER` does not affect existing active protocols, a `PN-SHUTDOWN` must be sent if that is required.	37	Clients SHOULD be able to handle protocol offers being able to be withdrawn, and should treat them as if it was a `PN-SHUTDOWN` if they were in use.
		38
		39	Certain protocols, such as extensions to REQs, may not need negotiation. This is up to the specification of the specific protocol.
38		40
39	## Protocol Requests	41	## Protocol Requests
40		42