deploy: 94fe31eb9b

features/parsing/untrusted_input/index.md

@@ -12,7 +12,7 @@ By default, [`parse()`](https://json.nlohmann.me/api/basic_json/parse/index.md)
 - Use [`accept()`](https://json.nlohmann.me/api/basic_json/accept/index.md) to only check whether the input is valid JSON, without building a value.
 - Implement the [SAX interface](https://json.nlohmann.me/features/parsing/sax_interface/index.md) and override `parse_error()` to react to an error yourself, with the byte position and the exception that would otherwise have been thrown; see the [example](https://json.nlohmann.me/features/parsing/parse_exceptions/#user-defined-sax-interface) that overrides it to print instead of throw.
 
-If exceptions are unavailable entirely (`-fno-exceptions`, or [`JSON_NOEXCEPTION`](https://json.nlohmann.me/api/macros/json_noexception/index.md) defined), every `throw` in the library becomes a call to `std::abort()` -- there is no way to recover from a parse error of untrusted input in that configuration; see [Switch off exceptions](https://json.nlohmann.me/home/exceptions/#switch-off-exceptions) for the details and for overriding this with `JSON_THROW_USER`.
+If exceptions are unavailable entirely (`-fno-exceptions`, or [`JSON_NOEXCEPTION`](https://json.nlohmann.me/api/macros/json_noexception/index.md) defined), every `throw` in the library becomes a call to `std::abort()`. The alternatives above do not throw, so `parse()` with `allow_exceptions` set to `false` (and likewise `accept()` and the `from_*` functions with `allow_exceptions` set to `false`) can still reject invalid input in that configuration; a plain `parse()` call aborts on invalid input. See [Working without exceptions](https://json.nlohmann.me/features/no_exceptions/index.md) and [Switch off exceptions](https://json.nlohmann.me/home/exceptions/#switch-off-exceptions) for the details and for overriding the abort with `JSON_THROW_USER`.
 
 ## Nesting depth