Fix JSON comments

sadortun · sadortun · commit b9834387e705 · 2021-08-01T16:01:42.000-04:00
diff --git a/_includes/js/objects.md b/_includes/js/objects.md
@@ -145,8 +145,14 @@ gameScore.save()
 After this code runs, you will probably be wondering if anything really happened. To make sure the data was saved, you can look at the Data Browser in your app on Parse. You should see something like this:
 
 ```json
-objectId: "xWMyZ4YEGZ", score: 1337, playerName: "Sean Plott", cheatMode: false,
-createdAt:"2011-06-10T18:33:42Z", updatedAt:"2011-06-10T18:33:42Z"
+{
+  objectId: "xWMyZ4YEGZ",
+  score: 1337,
+  playerName: "Sean Plott",
+  cheatMode: false,
+  createdAt: "2011-06-10T18:33:42Z",
+  updatedAt: "2011-06-10T18:33:42Z"
+}
 ```
 
 There are two things to note here. You didn't have to configure or set up a new Class called `GameScore` before running this code. Your Parse app lazily creates this Class for you when it first encounters it.
diff --git a/_includes/php/objects.md b/_includes/php/objects.md
@@ -36,8 +36,14 @@ try {
 After this code runs, you will probably be wondering if anything really happened. To make sure the data was saved, you can look at the Data Browser in your app on Parse. You should see something like this:
 
 ```json
-objectId: "xWMyZ4YEGZ", score: 1337, playerName: "Sean Plott", cheatMode: false,
-createdAt:"2011-06-10T18:33:42Z", updatedAt:"2011-06-10T18:33:42Z"
+{
+  objectId: "xWMyZ4YEGZ",
+  score: 1337,
+  playerName: "Sean Plott",
+  cheatMode: false,
+  createdAt: "2011-06-10T18:33:42Z",
+  updatedAt: "2011-06-10T18:33:42Z"
+}
 ```
 
 There are two things to note here. You didn't have to configure or set up a new Class called `GameScore` before running this code. Your Parse app lazily creates this Class for you when it first encounters it.
diff --git a/_includes/php/setup.md b/_includes/php/setup.md
@@ -62,13 +62,15 @@ Note that it is _not_ guaranteed that 'response' will be a parsable json array.
 
 A couple examples of bad health responses could include an incorrect mount path, port or domain.
 
-```json
+```json5
 // ParseClient::setServerURL('http://localhost:1337', 'not-good');
 {
     "status": 404,
     "response": "<!DOCTYPE html>...Cannot GET \/not-good\/health..."
 }
+```
 
+```json5
 // ParseClient::setServerURL('http://__uh__oh__.com', 'parse');
 {
     "status": 0,
diff --git a/_includes/rest/hooks.md b/_includes/rest/hooks.md
@@ -220,7 +220,7 @@ and perform a `parse deploy` the usual way.
 To create a new function webhook post to <code class="highlighter-rouge"><span class="custom-parse-server-mount">/parse/</span>hooks/functions</code> with payload in the format
 
 ```json
-{"functionName" : x, "url" : y}
+{"functionName" : "baz", "url" : "https://api.example.com/baz"}
 ```
 
 Post example:
diff --git a/_includes/rest/users.md b/_includes/rest/users.md
@@ -600,6 +600,7 @@ The ACL is formatted as a JSON object where the keys are either object ids or th
 For example, if you want the user with id `"3KmCvT7Zsb"` to have read and write access to an object, plus the object should be publicly readable, that corresponds to an ACL of:
 
 ```json
+{
 	"ACL": {
 		"3KmCvT7Zsb": {
 			"read": true,
diff --git a/_includes/unity/objects.md b/_includes/unity/objects.md
@@ -6,8 +6,8 @@ Storing data on Parse is built around the `ParseObject`. Each `ParseObject` cont
 
 For example, let's say you're tracking high scores for a game. A single `ParseObject` could contain:
 
-```json
-score: 1337, playerName: "Sean Plott", cheatMode: false
+```json5
+{score: 1337, playerName: "Sean Plott", cheatMode: false }
 ```
 
 Keys must start with a letter, and can contain alphanumeric characters and underscores. Values can be strings, numbers, booleans, or even arrays and dictionaries - anything that can be JSON-encoded.

Original file line number	Diff line number	Diff line change
`@@ -62,13 +62,15 @@ Note that it is _not_ guaranteed that 'response' will be a parsable json array.`
`62`	`62`
`63`	`63`	`A couple examples of bad health responses could include an incorrect mount path, port or domain.`
`64`	`64`
`65`		-```json
	`65`	+```json5
`66`	`66`	`// ParseClient::setServerURL('http://localhost:1337', 'not-good');`
`67`	`67`	`{`
`68`	`68`	`"status": 404,`
`69`	`69`	`"response": "<!DOCTYPE html>...Cannot GET \/not-good\/health..."`
`70`	`70`	`}`
	`71`	+```
`71`	`72`
	`73`	+```json5
`72`	`74`	`// ParseClient::setServerURL('http://__uh__oh__.com', 'parse');`
`73`	`75`	`{`
`74`	`76`	`"status": 0,`