Merge pull request #1477 from kehiy/jsonc

format(all): JSON formatting

1 files changed, 12 insertions, 10 deletions

diff --git a/89.md b/89.md
index 54aa30b..24aa3c5 100644
--- a/89.md
+++ b/89.md
@@ -27,7 +27,7 @@ There are three actors to this workflow:
 ## Events
 
 ### Recommendation event
-```json
+```jsonc
 {
   "kind": 31989,
   "pubkey": <recommender-user-pubkey>,
@@ -35,7 +35,8 @@ There are three actors to this workflow:
     ["d", <supported-event-kind>],
     ["a", "31990:app1-pubkey:<d-identifier>", "wss://relay1", "ios"],
     ["a", "31990:app2-pubkey:<d-identifier>", "wss://relay2", "web"]
-  ]
+  ],
+  // other fields...
 }
 ```
 
@@ -47,7 +48,7 @@ The second value of the tag SHOULD be a relay hint.
 The third value of the tag SHOULD be the platform where this recommendation might apply.
 
 ## Handler information
-```json
+```jsonc
 {
   "kind": 31990,
   "pubkey": "<application-pubkey>",
@@ -59,7 +60,8 @@ The third value of the tag SHOULD be the platform where this recommendation migh
     ["web", "https://..../p/<bech32>", "nprofile"],
     ["web", "https://..../e/<bech32>"],
     ["ios", ".../<bech32>"]
-  ]
+  ],
+  // other fields...
 }
 ```
 
@@ -77,13 +79,13 @@ A tag without a second value in the array SHOULD be considered a generic handler
 # Client tag
 When publishing events, clients MAY include a `client` tag. Identifying the client that published the note. This tag is a tuple of `name`, `address` identifying a handler event and, a relay `hint` for finding the handler event. This has privacy implications for users, so clients SHOULD allow users to opt-out of using this tag.
 
-```json
+```jsonc
 {
   "kind": 1,
   "tags": [
     ["client", "My Client", "31990:app1-pubkey:<d-identifier>", "wss://relay1"]
   ]
-  ...
+  // other fields...
 }
 ```
 
@@ -99,14 +101,14 @@ The client MIGHT query for the user's and the user's follows handler.
 ### User A recommends a `kind:31337`-handler
 User A might be a user of Zapstr, a `kind:31337`-centric client (tracks). Using Zapstr, user A publishes an event recommending Zapstr as a `kind:31337`-handler.
 
-```json
+```jsonc
 {
   "kind": 31989,
   "tags": [
     ["d", "31337"],
     ["a", "31990:1743058db7078661b94aaf4286429d97ee5257d14a86d6bfa54cb0482b876fb0:abcd", <relay-url>, "web"]
   ],
-  ...
+  // other fields...
 }
 ```
 
@@ -115,7 +117,7 @@ User B might see in their timeline an event referring to a `kind:31337` event (e
 
 User B's client, not knowing how to handle a `kind:31337` might display the event using its `alt` tag (as described in NIP-31). When the user clicks on the event, the application queries for a handler for this `kind`:
 
-```json
+```
 ["REQ", <id>, { "kinds": [31989], "#d": ["31337"], "authors": [<user>, <users-contact-list>] }]
 ```
 
@@ -126,6 +128,6 @@ User B's client sees the application's `kind:31990` which includes the informati
 ### Alternative query bypassing `kind:31989`
 Alternatively, users might choose to query directly for `kind:31990` for an event kind. Clients SHOULD be careful doing this and use spam-prevention mechanisms or querying high-quality restricted relays to avoid directing users to malicious handlers.
 
-```json
+```
 ["REQ", <id>, { "kinds": [31990], "#k": [<desired-event-kind>], "authors": [...] }]
 ```