CWG2937 Grammar for preprocessing-file has no normative effect

Author: burblebee

source/lex.tex

@@ -162,7 +162,8 @@
 directive\iref{cpp.include}.
 \end{example}
 
-\item Preprocessing directives\iref{cpp} are executed, macro invocations are
+\item The source file is analyzed as a \grammarterm{preprocessing-file}\iref{cpp.pre}.
+Preprocessing directives\iref{cpp} are executed, macro invocations are
 expanded\iref{cpp.replace}, and \tcode{_Pragma} unary operator expressions are executed\iref{cpp.pragma.op}.
 A \tcode{\#include} preprocessing directive\iref{cpp.include} causes the named header or
 source file to be processed from phase 1 through phase 4, recursively.
@@ -183,7 +184,8 @@
 token\iref{lex.token}. The resulting tokens
 constitute a \defn{translation unit} and
 are syntactically and
-semantically analyzed and translated.
+semantically analyzed as a \grammarterm{translation-unit}\iref{basic.link} and
+translated.
 \begin{note}
 The process of analyzing and translating the tokens can occasionally
 result in one token being replaced by a sequence of other