📝 update documentation after merging #4590

Signed-off-by: Niels Lohmann <[email protected]>

Author: nlohmann

docs/mkdocs/docs/features/binary_formats/bson.md

@@ -32,11 +32,8 @@ The library uses the following mapping from JSON values types to BSON types:
 
 !!! warning "Incomplete mapping"
 
-    The mapping is **incomplete**, since only JSON-objects (and things
-    contained therein) can be serialized to BSON.
-    Also, integers larger than 9223372036854775807 cannot be serialized to BSON,
-    and the keys may not contain U+0000, since they are serialized a
-    zero-terminated c-strings.
+    The mapping is **incomplete**, since only JSON-objects (and things contained therein) can be serialized to BSON.
+    Also, keys may not contain U+0000, since they are serialized a zero-terminated c-strings.
 
 ??? example
 
@@ -82,6 +79,10 @@ The library maps BSON record types to JSON value types as follows:
 
     The mapping is **incomplete**. The unsupported mappings are indicated in the table above.
 
+!!! note "Handling of BSON type 0x11"
+
+    BSON type 0x11 is used to represent uint64 numbers. This library treats these values purely as uint64 numbers 
+    and does not parse them into date-related formats.
 
 ??? example
 
@@ -94,8 +95,3 @@ The library maps BSON record types to JSON value types as follows:
     ```json
     --8<-- "examples/from_bson.output"
     ```
-
-!!! note "Handling of BSON type 0x11"
-
-    BSON type 0x11 is used to represent uint64 numbers. This library treats these values purely as uint64 numbers 
-    and does not parse them into date-related formats.

docs/mkdocs/docs/home/exceptions.md

@@ -839,17 +839,14 @@ A parsed number could not be stored as without changing it to NaN or INF.
 
 ### json.exception.out_of_range.407
 
-UBJSON only support integer numbers up to 9223372036854775807.
+This exception previously indicated that the UBJSON and BSON binary formats did not support integer numbers greater than
+9223372036854775807 due to limitations in the implemented mapping. However, these limitations have since been resolved,
+and this exception no longer occurs.
 
-!!! failure "Example message"
-
-    ```
-    number overflow serializing '9223372036854775808'
-    ```
-
-!!! note
+!!! success "Exception cannot occur any more"
 
-    Since version 3.9.0, integer numbers beyond int64 are serialized as high-precision UBJSON numbers, and this exception does not further occur. 
+    - Since version 3.9.0, integer numbers beyond int64 are serialized as high-precision UBJSON numbers.
+    - Since version 3.12.0, integer numbers beyond int64 are serialized as uint64 BSON numbers.
 
 ### json.exception.out_of_range.408