aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar Sebastian Kuipers <[email protected]>2021-02-01 18:41:09 +0100
committerGravatar Sebastian Kuipers <[email protected]>2021-02-01 18:41:09 +0100
commitdc8a5d4084e124f9a7d6e0d31658b6eb0637bccc (patch)
treedbfce7b77d62a37e0d4b88ef375801560ba15739
parentRemoved extra whitespace line in last example (diff)
Changed some wording
-rw-r--r--bot/resources/tags/empty_json.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/bot/resources/tags/empty_json.md b/bot/resources/tags/empty_json.md
index d5e0f843f..45df3fd54 100644
--- a/bot/resources/tags/empty_json.md
+++ b/bot/resources/tags/empty_json.md
@@ -2,16 +2,16 @@ When creating a new JSON file you might run into the following error.
`JSONDecodeError: Expecting value: line 1 column 1 (char 0)`
-In short, this means that your JSON is invalid in its current state. This could very well happen because the file is just new and empty.
-A JSON may never be completely empty. It is recommended to have at least one of the following in your json:
+In short, this means that your JSON is invalid in its current state. This could very well happen because the file is just new and completely empty.
+Whilst the JSON data may be empty, the .json file must not. It is recommended to have at least one of the following data types in your .json file:
```
object
array
```
-To resolve this issue, you create one of the above values in your JSON. It is very common to use `{}` to make an object, which is similar to a dictionary in python.
-When this is added to your JSON, it will look like this:
+To resolve this issue, you create one of the above data types in your .json file. It is very common to use `{}` to make an object, which works similar to a dictionary in python.
+When this is added to your .json file, it will look like this:
```json
{