…0657f2

 * [stream.iterators]: move out [iterator.range] and make it its own clause (thanks Jonathan Wakely)
 * [syserr.syserr.members]: fix typeface for inline code (thanks Jonathan Wakely)

[dcl.spec.auto] Replace "have an initializer" with "be followed by an
initializer", to match the change from "init-declarator" to
"declarator".

[dcl.type.class.deduct] Add paragraph break between new paragraph and
example (the example is for the entire section, not for the new para).

[expr.new] Rename placeholder from I to init to improve appearance of
following code snippet.

This is NOT editorial!

The two blanket wordings triggered by this diff are

https://eel.is/c++draft/associative.reqmts#15.2

> A deduction guide for an associative container shall not participate
> in overload resolution if any of the following are true: [...]
>
> - It has an `Allocator` template parameter and a type that does not
>     qualify as an allocator is deduced for that parameter.

https://eel.is/c++draft/container.adaptors.general#4.4
https://eel.is/c++draft/container.adaptors.general#4.5

> A deduction guide for a container adaptor shall not participate
> in overload resolution if any of the following are true: [...]
>
> - It has an `Allocator` template parameter and a type that does not
>     qualify as an allocator is deduced for that parameter.
>
> - It has both `Container` and `Allocator` template parameters,
>     and `uses_allocator_v<Container, Allocator>` is `false`.

On the latter topic (`Container` parameters), see issue cplusplus#5.

Chapter19

Importable C++ library headers can be imported as header units.
This currently says "as module units".
[module.unit]cplusplus#1 says that
"A _module unit_ is a translation unit that contains a _module-declaration_."
[module.import]cplusplus#5 says that the synthetized header unit from an `import <H>;`
is a translation unit that contains no _module-declaration_.