From fa73074f9eda2486d6ed2252da4ee22353391152 Mon Sep 17 00:00:00 2001
From: Sandwich <299465+dskvr@users.noreply.github.com>
Date: Fri, 13 Sep 2024 03:25:06 +0200
Subject: [PATCH] content SHOULD contain stringified NIP-11

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

diff --git a/66.md b/66.md
index 532ce58c..325a80e3 100644
--- a/66.md
+++ b/66.md
@@ -48,7 +48,7 @@ Discovery of relays over nostr.
 ### Schema 
 
 #### Content 
-`30166` content fields **MAY** include the stringified JSON of the relay's NIP-11 informational document. This data **MAY** be provided for informational purposes only. 
+`30166` content fields **SHOULD** include the stringified JSON of the relay's NIP-11 informational document. This data **MAY** be provided for informational purposes only. 
 
 #### `created_at`
 The `created_at` field in a NIP-66 event should reflect the time when the relay liveness (and potentially other data points) was checked.
@@ -247,4 +247,4 @@ _Any pubkey that publishes `30166` events **SHOULD** at a minimum be checking th
 
 - When a client implements `NIP-66` events, the client should have a fallback if `NIP-66` events cannot be located.
 
-- A `Monitor` or `Ad-hoc Monitor` may publish erroneous `30166` events, intentionally or otherwise. Therefor, it's important to program defensively to limit the impact of such events. This can be achieved with web-of-trust, reviews, fallbacks and/or data-aggregation for example.
\ No newline at end of file
+- A `Monitor` or `Ad-hoc Monitor` may publish erroneous `30166` events, intentionally or otherwise. Therefor, it's important to program defensively to limit the impact of such events. This can be achieved with web-of-trust, reviews, fallbacks and/or data-aggregation for example.