deploy: a47170346a

features/conversions.md

@@ -247,7 +247,7 @@ which forces the explicit `get` form and can catch unintended conversions at com
     `std::optional<T>` from delegating to `get<T>()`, to avoid a constructor ambiguity with
     `std::optional<T>`'s own converting constructor from `basic_json`. As a result,
     `static_cast<std::optional<T>>(json_value)` goes through `std::optional<T>`'s own converting
-    constructor rather than through `get<std::optional<T>>()`, which can behave differently -- for example,
+    constructor rather than through `get<std::optional<T>>()`, which can behave differently — for example,
     with a custom `adl_serializer<std::optional<T>>` specialization. Prefer `get<std::optional<T>>()`/`get_to()`
     over `static_cast` for optional types.
 
@@ -263,7 +263,7 @@ which forces the explicit `get` form and can catch unintended conversions at com
     - The JSON array has **too many** elements: the surplus is **silently discarded**, and no exception is
       thrown.
     - The JSON array has **too few** elements: `at` throws
-      [`out_of_range.401`](../home/exceptions.md#jsonexceptionout_of_range401) for the first missing index --
+      [`out_of_range.401`](../home/exceptions.md#jsonexceptionout_of_range401) for the first missing index —
       an out-of-range error, not a [`type_error`](../home/exceptions.md#type-errors), even though the cause
       is a shape mismatch.
 
@@ -281,7 +281,7 @@ which forces the explicit `get` form and can catch unintended conversions at com
 
 ## Omitting a field when serializing `std::optional`
 
-By default, `to_json` for `std::optional<T>` writes either the value or `#!json null` -- there is no built-in way
+By default, `to_json` for `std::optional<T>` writes either the value or `#!json null` — there is no built-in way
 to make a field disappear from the serialized object entirely when the `std::optional` is `std::nullopt`. Because
 a specialization of `adl_serializer<std::optional<T>>` only controls how the *value* is converted (it cannot
 prevent the containing object's `to_json` from inserting the key in the first place), omission has to be
@@ -313,7 +313,7 @@ json j = numbers;   // [1,2,3]
 !!! info "Constructing from a C++20 range view"
 
     A `json` array can also be constructed directly from a C++20 range view (`std::ranges::view`), such as the result
-    of `std::views::filter` or `std::views::transform` -- no intermediate container is needed:
+    of `std::views::filter` or `std::views::transform` — no intermediate container is needed:
 
     ```cpp
     std::vector<int> nums{1, 2, 37, 42, 21};
@@ -336,7 +336,12 @@ The conversions above are built in for standard types. To make the same syntax w
 
 - [`get`](../api/basic_json/get.md) - get a copy converted to a given type
 - [`get_to`](../api/basic_json/get_to.md) - convert into an existing variable
-- [`get_ref`](../api/basic_json/get_ref.md) / [`get_ptr`](../api/basic_json/get_ptr.md) - access the stored value without copying
+- [`get_ref`](../api/basic_json/get_ref.md) - / [`get_ptr`](../api/basic_json/get_ptr.md) - access the stored value without copying
 - [Arbitrary types conversions](arbitrary_types.md) - support your own types
 - [`JSON_USE_IMPLICIT_CONVERSIONS`](../api/macros/json_use_implicit_conversions.md) - toggle implicit conversions
 - [Zero-copy JSON views](json_view.md) - get values out of a document or a view
+- [`adl_serializer`](../api/adl_serializer/index.md) - the default serializer behind the conversions
+- [`type`](../api/basic_json/type.md) - query the type of a value
+- [`JSON_DISABLE_TUPLE_REFERENCE_CONVERSION`](../api/macros/json_disable_tuple_reference_conversion.md) - toggle conversion to tuples of references
+- [`JSON_HAS_RANGE_VIEW_CONVERSION`](../api/macros/json_has_range_view_conversion.md) - toggle conversion from ranges
+