[uaxid] Replace 'C++' with 'this document'

Fixes ISO/CS comment (C++23 proof)

Author: jensmaurer

source/uax31.tex

@@ -6,14 +6,14 @@
 \pnum
 This Annex describes the choices made in application of
 \UAX{31} (``Unicode Identifier and Pattern Syntax'')
-to \Cpp{} in terms of the requirements from \UAX{31} and
-how they do or do not apply to \Cpp{}.
+to this document in terms of the requirements from \UAX{31} and
+how they do or do not apply to this document.
 In terms of \UAX{31},
-\Cpp{} conforms by meeting the requirements
+this document conforms by meeting the requirements
 R1 ``Default Identifiers'' and
 R4 ``Equivalent Normalized Identifiers''.
 The other requirements, also listed below,
-are either alternatives not taken or do not apply to \Cpp{}.
+are either alternatives not taken or do not apply to this document.
 
 \rSec1[uaxid.def]{R1 Default identifiers}
 
@@ -29,7 +29,7 @@
 where \tcode{<Start>} has the XID_Start property,
 \tcode{<Continue>} has the XID_Continue property, and
 \tcode{<Medial>} is a list of characters permitted between continue characters.
-For \Cpp{} we add the character \unicode{005f}{low line}, or \tcode{_},
+This document adds the character \unicode{005f}{low line}, or \tcode{_},
 to the set of permitted \tcode{<Start>} characters,
 the \tcode{<Medial>} set is empty, and
 the \tcode{<Continue>} characters are unmodified.
@@ -41,7 +41,7 @@
 \end{codeblock}
 
 \pnum
-This is described in the \Cpp{} grammar in \ref{lex.name},
+This is described in \ref{lex.name},
 where \grammarterm{identifier} is formed from
 \grammarterm{identifier-start} or
 \grammarterm{identifier} followed by \grammarterm{identifier-continue}.
@@ -55,7 +55,7 @@
 describe precisely which combinations are permitted.
 
 \pnum
-\Cpp{} does not allow format characters in identifiers, so this does not apply.
+This document does not allow format characters in identifiers, so this does not apply.
 
 \rSec2[uaxid.def.stable]{R1b Stable identifiers}
 
@@ -65,7 +65,7 @@
 Once a string qualifies as an identifier it does so in all future versions.
 
 \pnum
-\Cpp{} does not make this guarantee,
+This document does not make this guarantee,
 except to the extent that \UAX{31} guarantees
 the stability of the XID_Start and XID_Continue properties.
 
@@ -77,7 +77,7 @@
 by fixing the set of code points allowed in identifiers forever.
 
 \pnum
-\Cpp{} does not choose to make this guarantee.
+This document does not choose to make this guarantee.
 As scripts are added to Unicode,
 additional characters in those scripts may become available
 for use in identifiers.
@@ -91,7 +91,7 @@
 during the processes of lexing and parsing.
 
 \pnum
-\Cpp{} does not claim conformance with this requirement.
+This document does not claim conformance with this requirement.
 
 \rSec1[uaxid.eqn]{R4 Equivalent normalized identifiers}
 
@@ -100,16 +100,16 @@
 how identifiers are compared and considered equivalent.
 
 \pnum
-\Cpp{} requires that identifiers be in Normalization Form C and
+This document requires that identifiers be in Normalization Form C and
 therefore identifiers that compare the same under NFC are equivalent.
 This is described in \ref{lex.name}.
 
 \rSec1[uaxid.eqci]{R5 Equivalent case-insensitive identifiers}
 
 \pnum
-\Cpp{} considers case to be significant in identifier comparison, and
+This document considers case to be significant in identifier comparison, and
 does not do any case folding.
-This requirement does not apply to \Cpp{}.
+This requirement does not apply to this document.
 
 \rSec1[uaxid.filter]{R6 Filtered normalized identifiers}
 
@@ -118,15 +118,15 @@
 \UAX{31} requires a precise specification of those exclusions.
 
 \pnum
-\Cpp{} does not make any such exclusions.
+This document does not make any such exclusions.
 
 \rSec1[uaxid.filterci]{R7 Filtered case-insensitive identifiers}
 
 \pnum
-\Cpp{} identifiers are case sensitive, and
+In this document, identifiers are case sensitive, and
 therefore this requirement does not apply.
 
 \rSec1[uaxid.hashtag]{R8 Hashtag identifiers}
 
 \pnum
-There are no hashtags in \Cpp{}, so this requirement does not apply.
+There are no hashtags in this document, so this requirement does not apply.