📡 update documentation (#4723)

Signed-off-by: Niels Lohmann <mail@nlohmann.me>

docs/mkdocs/docs/features/binary_formats/bjdata.md

@@ -5,12 +5,12 @@ The [BJData format](https://neurojson.org) was derived from and improved upon
 array container for efficient storage of N-dimensional packed arrays (**ND-arrays**); it also adds 5 new type markers -
 `[u] - uint16`, `[m] - uint32`, `[M] - uint64`, `[h] - float16` and `[B] - byte` - to unambiguously map common binary
 numeric types; furthermore, it uses little-endian (LE) to store all numerics instead of big-endian (BE) as in UBJSON to
-avoid  unnecessary conversions on commonly available platforms.
+avoid unnecessary conversions on commonly available platforms.
 
 Compared to other binary JSON-like formats such as MessagePack and CBOR, both BJData and UBJSON demonstrate a rare
 combination of being both binary and **quasi-human-readable**. This is because all semantic elements in BJData and
-UBJSON, including the data-type markers and name/string types are directly human-readable. Data stored in the
-BJData/UBJSON format are not only compact in size, fast to read/write, but also can be directly searched or read using
+UBJSON, including the data-type markers and name/string types, are directly human-readable. Data stored in the
+BJData/UBJSON format is not only compact in size, fast to read/write, but also can be directly searched or read using
 simple processing.
 
 !!! abstract "References"

docs/mkdocs/docs/features/binary_formats/index.md

@@ -1,6 +1,6 @@
 # Binary Formats
 
-Though JSON is a ubiquitous data format, it is not a very compact format suitable for data exchange, for instance over
+Though JSON is a ubiquitous data format, it is not a very compact format suitable for data exchange, for instance, over
 a network. Hence, the library supports
 
 - [BJData](bjdata.md) (Binary JData),