deploy: a47170346a

api/basic_json_view/number_token/index.md

@@ -8,7 +8,7 @@ Returns the number exactly as it appears in the source text, without parsing or
 
 ## Return value
 
-The number's token text, as a [`string_view_t`](https://json.nlohmann.me/api/basic_json_view/#member-types) into the document's [`source()`](https://json.nlohmann.me/api/basic_json_document/source/index.md) text -- for example `"1.50"`, `"1E2"`, `"-0"`, or an integer literal with more digits than any number type holds (such as a 30-digit integer, which [`get<T>()`](https://json.nlohmann.me/api/basic_json_view/get/index.md) and [`materialize()`](https://json.nlohmann.me/api/basic_json_view/materialize/index.md) can only represent approximately, as a `number_float_t`).
+The number's token text, as a [`string_view_t`](https://json.nlohmann.me/api/basic_json_view/#member-types) into the document's [`source()`](https://json.nlohmann.me/api/basic_json_document/source/index.md) text — for example `"1.50"`, `"1E2"`, `"-0"`, or an integer literal with more digits than any number type holds (such as a 30-digit integer, which [`get<T>()`](https://json.nlohmann.me/api/basic_json_view/get/index.md) and [`materialize()`](https://json.nlohmann.me/api/basic_json_view/materialize/index.md) can only represent approximately, as a `number_float_t`).
 
 ## Exception safety
 
@@ -26,15 +26,15 @@ Constant.
 
 ## Notes
 
-`BasicJsonType` has no counterpart to this function: once a number is parsed into `number_integer_t`, `number_unsigned_t`, or `number_float_t`, its original textual form (leading zeros aside, which are already rejected by the grammar; trailing zeros in the fraction; the case and sign of the exponent; ...) is gone. `number_token()` is useful precisely where that form must survive -- a price or an identifier that must be reproduced exactly, or a number too large for any of `BasicJsonType`'s number types to hold without loss.
+`BasicJsonType` has no counterpart to this function: once a number is parsed into `number_integer_t`, `number_unsigned_t`, or `number_float_t`, its original textual form (leading zeros aside, which are already rejected by the grammar; trailing zeros in the fraction; the case and sign of the exponent; ...) is gone. `number_token()` is useful precisely where that form must survive — a price or an identifier that must be reproduced exactly, or a number too large for any of `BasicJsonType`'s number types to hold without loss.
 
-The returned [`string_view_t`](https://json.nlohmann.me/api/basic_json_view/#member-types) always points into the document's [`source()`](https://json.nlohmann.me/api/basic_json_document/source/index.md) text -- numbers are never decoded into the document's separate string buffer -- and is valid exactly as long as that text is, see the [validity rules](https://json.nlohmann.me/api/basic_json_view/index.md) of `basic_json_view`.
+The returned [`string_view_t`](https://json.nlohmann.me/api/basic_json_view/#member-types) always points into the document's [`source()`](https://json.nlohmann.me/api/basic_json_document/source/index.md) text — numbers are never decoded into the document's separate string buffer — and is valid exactly as long as that text is, see the [validity rules](https://json.nlohmann.me/api/basic_json_view/index.md) of `basic_json_view`.
 
 ## Examples
 
 Example
 
-The example below keeps a price and an order ID exactly as they were written in an incoming order, where converting them with [`get<T>()`](https://json.nlohmann.me/api/basic_json_view/get/index.md) would lose information: the price picks up floating-point rounding, and the order ID -- more digits than a 64-bit integer holds -- can only be approximated as a `double` once `materialize()`d.
+The example below keeps a price and an order ID exactly as they were written in an incoming order, where converting them with [`get<T>()`](https://json.nlohmann.me/api/basic_json_view/get/index.md) would lose information: the price picks up floating-point rounding, and the order ID — more digits than a 64-bit integer holds — can only be approximated as a `double` once `materialize()`d.
 
 ```
 #include <iostream>
@@ -80,9 +80,10 @@ Output:
 
 ## See also
 
-- [get](https://json.nlohmann.me/api/basic_json_view/get/index.md) - convert the value to a given type
-- [get_string](https://json.nlohmann.me/api/basic_json_view/get_string/index.md) - the string, without a copy
+- [`get`](https://json.nlohmann.me/api/basic_json_view/get/index.md) - convert the value to a given type
+- [`get_string`](https://json.nlohmann.me/api/basic_json_view/get_string/index.md) - the string, without a copy
 - [`BasicJsonType::number_integer_t`](https://json.nlohmann.me/api/basic_json/number_integer_t/index.md), [`number_unsigned_t`](https://json.nlohmann.me/api/basic_json/number_unsigned_t/index.md), [`number_float_t`](https://json.nlohmann.me/api/basic_json/number_float_t/index.md) - the number types `get<T>()` and `materialize()` convert into
+- [Zero-copy JSON views](https://json.nlohmann.me/features/json_view/#getting-values-out-without-copying) - reading a number exactly as written
 
 ## Version history