deploy: 63c10a51fc

api/basic_json/number_integer_t.md

@@ -29,18 +29,18 @@ to use.
 
 ## Notes
 
-#### Default type
+### Default type
 
 With the default values for `NumberIntegerType` (`std::int64_t`), the default value for `number_integer_t` is
 `#!cpp std::int64_t`.
 
-#### Default behavior
+### Default behavior
 
 - The restrictions about leading zeros are not enforced in C++. Instead, leading zeros in integer literals lead to an
   interpretation as an octal number. Internally, the value will be stored as a decimal number. For instance, the C++
   integer literal `010` will be serialized to `8`. During deserialization, leading zeros yield an error.
 
-#### Limits
+### Limits
 
 [RFC 8259](https://tools.ietf.org/html/rfc8259) specifies:
 > An implementation may set limits on the range and precision of numbers.
@@ -57,7 +57,7 @@ will automatically be stored as [`number_unsigned_t`](number_unsigned_t.md) or [
 As this range is a subrange of the exactly supported range [INT64_MIN, INT64_MAX], this class's integer type is
 interoperable.
 
-#### Storage
+### Storage
 
 Integer number values are stored directly inside a `basic_json` type.
 
@@ -77,6 +77,13 @@ Integer number values are stored directly inside a `basic_json` type.
     --8<-- "examples/number_integer_t.output"
     ```
 
+## See also
+
+- [number_unsigned_t](number_unsigned_t.md) the type used to store JSON unsigned integer numbers
+- [number_float_t](number_float_t.md) the type used to store JSON floating-point numbers
+- [is_number_integer](is_number_integer.md) checks whether the JSON value is a signed integer number
+- [Number Handling](../../features/types/number_handling.md) - the article on number handling
+
 ## Version history
 
 - Added in version 1.0.0.