--- a/docs/Writerside/topics/json.h.md Sat Oct 11 15:42:48 2025 +0200
+++ b/docs/Writerside/topics/json.h.md Sun Oct 12 20:21:56 2025 +0200
@@ -29,7 +29,7 @@
Specifying `NULL` as `allocator` is allowed, in which case the `cxDefaultAllocator` will be used.
The actual parsing is an interleaving invocation of the `cxJsonFill()` (or `cxJsonFilln()`) and `cxJsonNext()` functions.
-The `cxJsonFill()` function is a convenience function, that accepts UCX strings and normal zero-terminated C strings.
+The `cxJsonFill()` function is a convenience function that accepts UCX strings and normal zero-terminated C strings.
Calling `cxJsonNext()` will return with `CX_JSON_NO_ERROR` (= zero) for each JSON value that is successfully parsed,
and stores the pointer to the allocated value in the variable pointed to by `value`.
@@ -117,7 +117,7 @@
The `cxJsonIsXYZ()` family functions check the type of the specified JSON value.
-The JSON specification only defines numbers, therefore `cxJsonIsNumber()` returns true for both floating point and integer numbers.
+The JSON specification only defines numbers, therefore `cxJsonIsNumber()` returns true for both floating-point and integer numbers.
On the other hand, `cxJsonIsInteger()` only returns true for integral numbers.
The function `cxJsonIsBool()` returns true if `cxJsonIsLiteral()` returns true, but `cxJsonIsNull()` does not.
@@ -125,7 +125,7 @@
> Since a literal can be `true`, `false`, or `null`, note carefully that `!cxJsonIsTrue(v)`
> is in general _not_ equivalent to `cxJsonIsFalse(v)`.
>
-> Additionally, UCX does implement the Javascript concept of a "falsy" value, meaning that
+> Additionally, UCX does implement the JavaScript concept of a "falsy" value, meaning that
> `cxJsonIsFalse()` _only_ returns true, if the value is a literal `false`.
>{style="note"}
@@ -148,7 +148,7 @@
>
> This is **not** the case for `cxJsonArrRemove()` and `cxJsonObjRemove()`, which return `NULL` in that case.
-> If you don't have full control over the JSON data, you should always check the datatype of a value first, before accessing it.
+> If you don't have full control over the JSON data, you should always check the datatype of a value first before accessing it.
>{style="note"}
## Deallocate Memory