6 files changed, 17 insertions, 17 deletions

diff --git a/11.md b/11.md
index 8efd0f0..8af4f31 100644
--- a/11.md
+++ b/11.md
@@ -262,7 +262,7 @@ processed by appropriate client software.
 
 Relays that require payments may want to expose their fee schedules.
 
-```json
+```jsonc
 {
   "payments_url": "https://my-relay/payments",
   "fees": {
@@ -270,7 +270,7 @@ Relays that require payments may want to expose their fee schedules.
     "subscription": [{ "amount": 5000000, "unit": "msats", "period": 2592000 }],
     "publication": [{ "kinds": [4], "amount": 100, "unit": "msats" }],
   },
-  ...
+  // other fields...
 }
 ```
 
diff --git a/17.md b/17.md
index 4b96bce..72f40c4 100644
--- a/17.md
+++ b/17.md
@@ -47,7 +47,7 @@ An optional `subject` tag defines the current name/topic of the conversation. An
 
 Following [NIP-59](59.md), the **unsigned** `kind:14` chat message must be sealed (`kind:13`) and then gift-wrapped (`kind:1059`) to each receiver and the sender individually.
 
-```js
+```jsonc
 {
   "id": "<usual hash>",
   "pubkey": randomPublicKey,
diff --git a/22.md b/22.md
index 3706aec..f11925f 100644
--- a/22.md
+++ b/22.md
@@ -13,7 +13,7 @@ It uses `kind:1111` with plaintext `.content` (no HTML, Markdown, or other forma
 Comments MUST point to the root scope using uppercase tag names (e.g. `K`, `E`, `A` or `I`)
 and MUST point to the parent item with lowercase ones (e.g. `k`, `e`, `a` or `i`).
 
-```js
+```jsonc
 {
   kind: 1111,
   content: '<comment>',
@@ -56,7 +56,7 @@ If the parent item is an event, a `p` tag set to the parent event's author SHOUL
 
 A comment on a blog post looks like this:
 
-```js
+```jsonc
 {
   kind: 1111,
   content: 'Great blog post!',
@@ -79,7 +79,7 @@ A comment on a blog post looks like this:
 
 A comment on a [NIP-94](94.md) file looks like this:
 
-```js
+```jsonc
 {
   kind: 1111,
   content: 'Great file!',
@@ -100,7 +100,7 @@ A comment on a [NIP-94](94.md) file looks like this:
 
 A reply to a comment looks like this:
 
-```js
+```jsonc
 {
   kind: 1111,
   content: 'This is a reply to "Great file!"',
@@ -121,7 +121,7 @@ A reply to a comment looks like this:
 
 A comment on a website's url looks like this:
 
-```js
+```jsonc
 {
   kind: 1111,
   content: 'Nice article!',
@@ -142,7 +142,7 @@ A comment on a website's url looks like this:
 
 A podcast comment example:
 
-```js
+```jsonc
 {
   id: "80c48d992a38f9c445b943a9c9f1010b396676013443765750431a9004bdac05",
   pubkey: "252f10c83610ebca1a059c0bae8255eba2f95be4d1d7bcfa89d7248a82d9f111",
@@ -164,7 +164,7 @@ A podcast comment example:
 
 A reply to a podcast comment:
 
-```js
+```jsonc
 {
   kind: 1111,
   content: "I'm replying to the above comment.",
diff --git a/29.md b/29.md
index f0ba8ab..a116433 100644
--- a/29.md
+++ b/29.md
@@ -141,7 +141,7 @@ These are events expected to be sent by the relay master key or by group admins
 
 Clients can send these events to a relay in order to accomplish a moderation action. Relays must check if the pubkey sending the event is capable of performing the given action based on its role and the relay's internal policy (see also the description of `kind:39003`).
 
-```json
+```jsonc
 {
   "kind": 90xx,
   "content": "optional reason",
diff --git a/46.md b/46.md
index 60850aa..ce6764d 100644
--- a/46.md
+++ b/46.md
@@ -58,7 +58,7 @@ _user_ passes this token to _remote-signer_, which then sends `connect` *respons
 
 ## Request Events `kind: 24133`
 
-```js
+```jsonc
 {
     "kind": 24133,
     "pubkey": <local_keypair_pubkey>,
@@ -136,7 +136,7 @@ The `content` field is a JSON-RPC-like message that is [NIP-04](04.md) encrypted
 
 ### Signature request
 
-```js
+```jsonc
 {
     "kind": 24133,
     "pubkey": "eff37350d839ce3707332348af4549a96051bd695d3223af4aabce4993531d86",
@@ -156,7 +156,7 @@ The `content` field is a JSON-RPC-like message that is [NIP-04](04.md) encrypted
 
 ### Response event
 
-```js
+```jsonc
 {
     "kind": 24133,
     "pubkey": "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
@@ -196,7 +196,7 @@ _client_ should display (in a popup or new tab) the URL from the `error` field a
 ### Announcing _remote-signer_ metadata
 
 _remote-signer_ MAY publish it's metadata by using [NIP-05](05.md) and [NIP-89](89.md). With NIP-05, a request to `<remote-signer>/.well-known/nostr.json?name=_` MAY return this:
-```
+```jsonc
 {
     "names":{
         "_": <remote-signer-app-pubkey>,
diff --git a/96.md b/96.md
index 05c1b18..3828e76 100644
--- a/96.md
+++ b/96.md
@@ -323,8 +323,8 @@ Note: HTTP File Storage Server developers may skip this section. This is meant f
 A File Server Preference event is a kind 10096 replaceable event meant to select one or more servers the user wants
 to upload files to. Servers are listed as `server` tags:
 
-```json
-{.
+```jsonc
+{
   "kind": 10096,
   "content": "",
   "tags": [