From 5980907797231b3efb7fc1c43c4206fd11fbd947 Mon Sep 17 00:00:00 2001
From: emeceve <emeceve@outlook.com>
Date: Mon, 20 Jun 2022 22:08:36 -0300
Subject: [PATCH] Fix some typos and adds json type to code blocks

---
 01.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/01.md b/01.md
index 3fd1cdcb..e0def1ea 100644
--- a/01.md
+++ b/01.md
@@ -14,7 +14,7 @@ Each user has a keypair. Signatures, public key and encodings are done according
 
 The only object type that exists is the `event`, which has the following format on the wire:
 
-```
+```json
 {
   "id": <32-bytes sha256 of the the serialized event data>
   "pubkey": <32-bytes hex-encoded public key of the event creator>,
@@ -24,15 +24,15 @@ The only object type that exists is the `event`, which has the following format
     ["e", <32-bytes hex of the id of another event>, <recommended relay URL>],
     ["p", <32-bytes hex of the key>, <recommended relay URL>],
     ... // other kinds of tags may be included later
-  ]
+  ],
   "content": <arbitrary string>,
-  "sig": <64-bytes signature of the sha256 hash of the serialized event data, which is the same as the "id" field>,
+  "sig": <64-bytes signature of the sha256 hash of the serialized event data, which is the same as the "id" field>
 }
 ```
 
 To obtain the `event.id`, we `sha256` the serialized event. The serialization is done over the UTF-8 JSON-serialized string (with no indentation or extra spaces) of the following structure:
 
-```
+```json
 [
   0,
   <pubkey, as a (lowercase) hex string>,
@@ -51,15 +51,15 @@ Relays expose a websocket endpoint to which clients can connect.
 
 Clients can send 3 types of messages, which must be JSON arrays, according to the following patterns:
 
-  * `["EVENT", <event JSON as defined above>`], used to publish events.
-  * `["REQ", <subscription_id>, <filters JSON>...`], used to request events and subscribe to new updates.
+  * `["EVENT", <event JSON as defined above>]`, used to publish events.
+  * `["REQ", <subscription_id>, <filters JSON>...]`, used to request events and subscribe to new updates.
   * `["CLOSE", <subscription_id>]`, used to stop previous subscriptions.
 
 `<subscription_id>` is a random string that should be used to represent a subscription.
 
 `<filters>` is a JSON object that determines what events will be sent in that subscription, it can have the following attributes:
 
-```
+```json
 {
   "ids": <a list of event ids or prefixes>,
   "authors": <a list of pubkeys or prefixes, the pubkey of an event must be one of these>,