From 5289f92290cfd9471608c64180251ad8f165ea93 Mon Sep 17 00:00:00 2001
From: Alisdair Meredith <alisdairm@me.com>
Date: Tue, 4 Nov 2025 15:07:50 -1000
Subject: [PATCH] [lex.pptoken] Turn non-normative text into a note

The last part of this paragraph is non-normative, so turn it
into a note.  Also, the preceding sentence defining whitespace
characters is mostly unrelated to the precedingd defintion of
preprocessing tokens, so start a new paragraph to more clearly
show the comment assoication.
---
 source/lex.tex | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/source/lex.tex b/source/lex.tex
index 8005b33374..0d4e5fc923 100644
--- a/source/lex.tex
+++ b/source/lex.tex
@@ -562,6 +562,8 @@
 If a \unicode{0027}{apostrophe}, a \unicode{0022}{quotation mark},
 or any character not in the basic character set
 matches the last category, the program is ill-formed.
+
+\pnum
 Preprocessing tokens can be separated by
 \indextext{whitespace}%
 whitespace;
@@ -572,12 +574,14 @@
 new-line,
 \unicode{000b}{line tabulation}, and
 \unicode{000c}{form feed}), or both.
+\begin{note}
 As described in \ref{cpp}, in certain
 circumstances during translation phase 4, whitespace (or the absence
 thereof) serves as more than preprocessing token separation. Whitespace
 can appear within a preprocessing token only as part of a header name or
 between the quotation characters in a character literal or
 string literal.
+\end{note}
 
 \pnum
 Each preprocessing token that is converted to a token\iref{lex.token}