From 913dd3a018bb739b0a52e3976afc95d57e6af159 Mon Sep 17 00:00:00 2001
From: sandwich <299465+dskvr@users.noreply.github.com>
Date: Tue, 16 Jan 2024 17:17:28 +0000
Subject: [PATCH] Fix formatting

---
 66.md | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/66.md b/66.md
index 6098d251..62647120 100644
--- a/66.md
+++ b/66.md
@@ -13,7 +13,7 @@ An event that contains data about a relay. These events are self-reported by rel
 ### Purpose
 An event that makes relays discoverable.
 
-## Schema 
+### Schema 
 
 #### `event.content`
 **Should** be empty. 
@@ -89,8 +89,8 @@ Tags should be used to represent the Relay's abilities and meta at any given poi
 - String values from `NIP-11` using dot notation, for example
   ```
   [ "L", "nip11.tags" ]
-  [ "l", "sfw-only" ]
-  [ "l", "bitcoin-only" ]
+  [ "l", "sfw-only", "nip11.tags"  ]
+  [ "l", "bitcoin-only", "nip11.tags"  ]
   [ "L", "nip11.language_tags" ]
   [ "l", "en", "nip11.language_tags"  ]
   [ "l", "en-419", "nip11.language_tags" ]
@@ -162,10 +162,6 @@ _**It adds some additional tags**_
   ["rtt", "write", "701", "497", "508"]
   ```
 
-- `"e" === tagE[0]` An association to another standard nostr event (`0/1/2/4-9999` kind-range). An example would be an event containing the most recent check log or an archival event representing the check. Such a reference may contain duplicate or ommitted tags from a `30066` event.
-
-- `"a" === tagE[0]` An association to another replaceable nostr event. An example would be an event containing the most recent check log or an archival event representing the check. Such a reference may contain duplicate or ommitted tags from a `30066` event. 
-
 
 #### Methodology 
 A Relay Monitor publishes `30066`` events exclusively when a relay is operational. This approach ensures that the last known active state of the relay is maintained and recorded. Based on this data, several inferences can be drawn about the relay's status and characteristics