reformat a bunch of json things and small nitpicks.

1 files changed, 12 insertions, 12 deletions

diff --git a/40.md b/40.md
index b8a0336..909747f 100644
--- a/40.md
+++ b/40.md
@@ -2,7 +2,7 @@ NIP-40
 ======
 
 Expiration Timestamp
------------------------------------
+--------------------
 
 `draft` `optional`
 
@@ -20,14 +20,14 @@ values:
 
 ```json
 {
-    "pubkey": "<pub-key>",
-    "created_at": 1000000000,
-    "kind": 1,
-    "tags": [
-      ["expiration", "1600000000"]
-    ],
-    "content": "This message will expire at the specified timestamp and be deleted by relays.\n",
-    "id": "<event-id>"
+  "pubkey": "<pub-key>",
+  "created_at": 1000000000,
+  "kind": 1,
+  "tags": [
+    ["expiration", "1600000000"]
+  ],
+  "content": "This message will expire at the specified timestamp and be deleted by relays.\n",
+  "id": "<event-id>"
 }
 ```
 
@@ -43,9 +43,9 @@ Clients SHOULD ignore events that have expired.
 Relay Behavior
 --------------
 
-Relays MAY NOT delete expired messages immediately on expiration and MAY persist them indefinitely.  
-Relays SHOULD NOT send expired events to clients, even if they are stored.  
-Relays SHOULD drop any events that are published to them if they are expired.  
+Relays MAY NOT delete expired messages immediately on expiration and MAY persist them indefinitely.
+Relays SHOULD NOT send expired events to clients, even if they are stored.
+Relays SHOULD drop any events that are published to them if they are expired.
 An expiration timestamp does not affect storage of ephemeral events.
 
 Suggested Use Cases