Merge pull request #2113 from ehuss/unwrap-lexical

Unwrap all of the lexical chapters

Author: traviscross

src/comments.md

@@ -39,8 +39,7 @@ OUTER_BLOCK_DOC ->
 r[comments.normal]
 ## Non-doc comments
 
-Comments follow the general C++ style of line (`//`) and
-block (`/* ... */`) comment forms. Nested block comments are supported.
+Comments follow the general C++ style of line (`//`) and block (`/* ... */`) comment forms. Nested block comments are supported.
 
 r[comments.normal.tokenization]
 Non-doc comments are interpreted as a form of whitespace.
@@ -49,25 +48,16 @@ r[comments.doc]
 ## Doc comments
 
 r[comments.doc.syntax]
-Line doc comments beginning with exactly _three_ slashes (`///`), and block
-doc comments (`/** ... */`), both outer doc comments, are interpreted as a
-special syntax for [`doc` attributes].
+Line doc comments beginning with exactly _three_ slashes (`///`), and block doc comments (`/** ... */`), both outer doc comments, are interpreted as a special syntax for [`doc` attributes].
 
 r[comments.doc.attributes]
-That is, they are equivalent to writing
-`#[doc="..."]` around the body of the comment, i.e., `/// Foo` turns into
-`#[doc="Foo"]` and `/** Bar */` turns into `#[doc="Bar"]`. They must therefore
-appear before something that accepts an outer attribute.
+That is, they are equivalent to writing `#[doc="..."]` around the body of the comment, i.e., `/// Foo` turns into `#[doc="Foo"]` and `/** Bar */` turns into `#[doc="Bar"]`. They must therefore appear before something that accepts an outer attribute.
 
 r[comments.doc.inner-syntax]
-Line comments beginning with `//!` and block comments `/*! ... */` are
-doc comments that apply to the parent of the comment, rather than the item
-that follows.
+Line comments beginning with `//!` and block comments `/*! ... */` are doc comments that apply to the parent of the comment, rather than the item that follows.
 
 r[comments.doc.inner-attributes]
-That is, they are equivalent to writing `#![doc="..."]` around
-the body of the comment. `//!` comments are usually used to document
-modules that occupy a source file.
+That is, they are equivalent to writing `#![doc="..."]` around the body of the comment. `//!` comments are usually used to document modules that occupy a source file.
 
 r[comments.doc.bare-crs]
 The character `U+000D` (CR) is not allowed in doc comments.

src/identifiers.md

@@ -64,12 +64,10 @@ r[ident.raw]
 ## Raw identifiers
 
 r[ident.raw.intro]
-A raw identifier is like a normal identifier, but prefixed by `r#`. (Note that
-the `r#` prefix is not included as part of the actual identifier.)
+A raw identifier is like a normal identifier, but prefixed by `r#`. (Note that the `r#` prefix is not included as part of the actual identifier.)
 
 r[ident.raw.allowed]
-Unlike a normal identifier, a raw identifier may be any strict or reserved
-keyword except the ones listed above for `RAW_IDENTIFIER`.
+Unlike a normal identifier, a raw identifier may be any strict or reserved keyword except the ones listed above for `RAW_IDENTIFIER`.
 
 r[ident.raw.reserved]
 It is an error to use the [RESERVED_RAW_IDENTIFIER] token.

src/input-format.md

@@ -30,8 +30,7 @@ If the first character in the sequence is `U+FEFF` ([BYTE ORDER MARK]), it is re
 r[input.crlf]
 ## CRLF normalization
 
-Each pair of characters `U+000D` (CR) immediately followed by `U+000A` (LF) is replaced by a single `U+000A` (LF).
-This happens once, not repeatedly, so after the normalization, there can still exist `U+000D` (CR) immediately followed by `U+000A` (LF) in the input (e.g. if the raw input contained "CR CR LF LF").
+Each pair of characters `U+000D` (CR) immediately followed by `U+000A` (LF) is replaced by a single `U+000A` (LF). This happens once, not repeatedly, so after the normalization, there can still exist `U+000D` (CR) immediately followed by `U+000A` (LF) in the input (e.g. if the raw input contained "CR CR LF LF").
 
 Other occurrences of the character `U+000D` (CR) are left in place (they are treated as [whitespace]).
 
@@ -53,8 +52,7 @@ fn main() {
 ```
 
 r[input.shebang.inner-attribute]
-As an exception, if the `#!` characters are followed (ignoring intervening [comments] or [whitespace]) by a `[` token, nothing is removed.
-This prevents an [inner attribute] at the start of a source file being removed.
+As an exception, if the `#!` characters are followed (ignoring intervening [comments] or [whitespace]) by a `[` token, nothing is removed. This prevents an [inner attribute] at the start of a source file being removed.
 
 > [!NOTE]
 > The standard library [`include!`] macro applies byte order mark removal, CRLF normalization, and shebang removal to the file it reads. The [`include_str!`] and [`include_bytes!`] macros do not.

src/keywords.md

@@ -11,8 +11,7 @@ r[lex.keywords.strict]
 ## Strict keywords
 
 r[lex.keywords.strict.intro]
-These keywords can only be used in their correct contexts. They cannot
-be used as the names of:
+These keywords can only be used in their correct contexts. They cannot be used as the names of:
 
 * [Items]
 * [Variables] and function parameters
@@ -78,10 +77,7 @@ r[lex.keywords.reserved]
 ## Reserved keywords
 
 r[lex.keywords.reserved.intro]
-These keywords aren't used yet, but they are reserved for future use. They have
-the same restrictions as strict keywords. The reasoning behind this is to make
-current programs forward compatible with future versions of Rust by forbidding
-them to use these keywords.
+These keywords aren't used yet, but they are reserved for future use. They have the same restrictions as strict keywords. The reasoning behind this is to make current programs forward compatible with future versions of Rust by forbidding them to use these keywords.
 
 r[lex.keywords.reserved.list]
 - `abstract`
@@ -111,8 +107,7 @@ r[lex.keywords.weak]
 ## Weak keywords
 
 r[lex.keywords.weak.intro]
-These keywords have special meaning only in certain contexts. For example, it
-is possible to declare a variable or method with the name `union`.
+These keywords have special meaning only in certain contexts. For example, it is possible to declare a variable or method with the name `union`.
 
 - `'static`
 - `macro_rules`
@@ -124,12 +119,10 @@ r[lex.keywords.weak.macro_rules]
 * `macro_rules` is used to create custom [macros].
 
 r[lex.keywords.weak.union]
-* `union` is used to declare a [union] and is only a keyword when used in a
-  union declaration.
+* `union` is used to declare a [union] and is only a keyword when used in a union declaration.
 
 r[lex.keywords.weak.lifetime-static]
-* `'static` is used for the static lifetime and cannot be used as a [generic
-  lifetime parameter] or [loop label]
+* `'static` is used for the static lifetime and cannot be used as a [generic lifetime parameter] or [loop label]
 
   ```compile_fail
   // error[E0262]: invalid lifetime parameter name: `'static`