diff --git a/changelogs/client_server/newsfragments/2017.clarification b/changelogs/client_server/newsfragments/2017.clarification
new file mode 100644
index 000000000..a202eec32
--- /dev/null
+++ b/changelogs/client_server/newsfragments/2017.clarification
@@ -0,0 +1 @@
+Use `json` instead of `json5` for syntax highlighting.
diff --git a/content/client-server-api/modules/event_replacements.md b/content/client-server-api/modules/event_replacements.md
index 50109d073..11e755de0 100644
--- a/content/client-server-api/modules/event_replacements.md
+++ b/content/client-server-api/modules/event_replacements.md
@@ -309,7 +309,7 @@ for re-notifying if the sending client feels a large enough revision was made).
 
 For example, if there is an event mentioning Alice:
 
-```json5
+```json
 {
     "event_id": "$original_event",
     "type": "m.room.message",
@@ -324,7 +324,7 @@ For example, if there is an event mentioning Alice:
 
 And an edit to also mention Bob:
 
-```json5
+```json
 {
   "content": {
     "body": "* Hello Alice & Bob!",
diff --git a/content/client-server-api/modules/rich_replies.md b/content/client-server-api/modules/rich_replies.md
index ef07b6972..6445dc4bb 100644
--- a/content/client-server-api/modules/rich_replies.md
+++ b/content/client-server-api/modules/rich_replies.md
@@ -31,7 +31,7 @@ the `rel_type` and `event_id` properties of `m.relates_to` become *optional*.
 
 An example reply would be:
 
-```json5
+```json
 {
   "content": {
     "m.relates_to": {
@@ -187,7 +187,7 @@ of the replied to event and any users mentioned in that event. See
 
 An example including mentioning the original sender and other users:
 
-```json5
+```json
 {
   "content": {
     "m.relates_to": {