1 files changed, 1 insertions, 1 deletions
diff --git a/70.md b/70.md
index 219e6a4..043d5fb 100644
--- a/70.md
+++ b/70.md
@@ -12,7 +12,7 @@ A protected event is an event that can only be published to relays by its author
 The default behavior of a relay MUST be to reject any event that contains `["-"]`.
-Relays that want to accept such events MUST first require that the client perform the [NIP-42](https://github.com/nostr-protocol/nips/blob/master/42.md) `AUTH` flow and then check if the authenticated client has the same pubkey as the event being published and only accept the event in that case.
+Relays that want to accept such events MUST first require that the client perform the [NIP-42](42.md) `AUTH` flow and then check if the authenticated client has the same pubkey as the event being published and only accept the event in that case.
 ## The tag

diff --git a/70.md b/70.md index 219e6a4..043d5fb 100644 --- a/70.md +++ b/70.md
@@ -12,7 +12,7 @@ A protected event is an event that can only be published to relays by its author
12		12
13	The default behavior of a relay MUST be to reject any event that contains `["-"]`.	13	The default behavior of a relay MUST be to reject any event that contains `["-"]`.
14		14
15	Relays that want to accept such events MUST first require that the client perform the [NIP-42](https://github.com/nostr-protocol/nips/blob/master/42.md) `AUTH` flow and then check if the authenticated client has the same pubkey as the event being published and only accept the event in that case.	15	Relays that want to accept such events MUST first require that the client perform the [NIP-42](42.md) `AUTH` flow and then check if the authenticated client has the same pubkey as the event being published and only accept the event in that case.
16		16
17	## The tag	17	## The tag
18		18