CVS difference for ai12s/ai12-0444-1.txt

--- ai12s/ai12-0444-1.txt	2022/06/14 23:39:33	1.4
+++ ai12s/ai12-0444-1.txt	2022/06/21 03:14:39	1.5
@@ -1954,4 +1954,117 @@
 
 ****************************************************************
 
+From: Randy Brukardt
+Sent: Saturday, June 11, 2022  2:01 AM
+
+Following are some fixes to the approved changed wording of the various FDIS 
+AI. There also were a few typos in the AIs (stray brackets, missing words in
+Editor's notes) that I won't bother to explain.
+
+I'm not quite done applying the new wording, so there might be another item
+or two on Monday, but I'm sending this now so that you can review it and
+highlight any issues before I button this up.
+
+[Editor's note: only issues relevant to this AI are shown here; others
+are recorded in other relevant AIs.]
+
+---------------
+
+In AI12-0444-1, G.3.1(157/2) reads:
+
+Modify G.3.1(157/2): 
+
+    Although many operations are defined in terms of operations from
+    numerics.generic_complex_types, they [need not]{can} be implemented by
+    [calling those operations provided that the]{other operations that have
+    the same} effect[ is the same].
+
+It is bizarre that the package name is in all lower case; we never do that.
+I've fixed that to "Numerics.Generic_Complex_Types".
+
+****************************************************************
+
+From: Tucker Taft
+Sent: Saturday, June 11, 2022  8:14 AM
+
+All look good to me.
+
+****************************************************************
+
+From: Randy Brukardt
+Sent: Tuesday, June 14, 2022  8:36 PM
+
+Having finally finished applying all of the wording changes, I was able to
+check the result for words we're not supposed to be using. And surprise,
+there still were a dozen or so uses of words we were trying to eliminate.
+Some of those were errors applying changes (often cases where there were
+two changes in a paragraph, but only one change was applied). The rest are
+detailed below.
+
+Please read and comment (if needed) on these ASAP as I will be finishing 
+this project in the next few days (I hope!!).
+
+[Editor's note: only issues relevant to this AI are shown here; others
+are recorded in other relevant AIs.]
+
+----------------
+
+In AI12-0444-1, 13.3(30.1/3) replaces a "need not" with "is not required to".
+But there is a second "need not" in the paragraph; we replace that the same way.
+
+-----------------
+
+In AI12-0444-1, all of the paragraph numbers associated with 13.3 are wrong 
+(they were taken from a normative-only version of the RM, but this clause has
+interspersed notes whose paragraph numbers were not counted). The text and 
+wording changes are unaffected. These have been corrected.
+
+-----------------
+
+13.1(13/5) says:
+
+The specification of certain language-defined aspects need not be supported by
+all implementations; in such an implementation, the specification for such an
+aspect is illegal or raises an exception at run time.
+
+The "need not" needs to be replaced. The usual fix in Chapter 13 is:
+
+The specification of certain language-defined aspects {is not required 
+to}[need not] be supported by all implementations; in such an implementation, 
+the specification for such an aspect is illegal or raises an exception at
+run time.
+
+I added this to AI12-0444-1.
+
+----------------
+
+A number of Annex M (summary of Implementation-Defined and Implementation
+Advice) items contain banned words (as the original text did). I've fixed
+these  similarly to the base text (and did not otherwise document them, as
+is usual as they are considered non-normative).
+
+****************************************************************
+
+From: Jeff Cousins
+Sent: Wednesday, June 15, 2022  2:35 AM
+
+Thanks Randy, looks good.
+
+****************************************************************
+
+From: Tucker Taft
+Sent: Wednesday, June 15, 2022  5:05 PM
+
+Most seem fine.  I have one comment on some awkward wording below.
+[Not relevant to this AI and thus omitted - Editor.]
+
+****************************************************************
+
+From: Randy Brukardt
+Sent: Tuesday, June 14, 2022  8:36 PM
+****************************************************************
+
+From: Randy Brukardt
+Sent: Tuesday, June 14, 2022  8:36 PM
+****************************************************************