CVS difference for ai22s/ai22-0031-1.txt

--- ai22s/ai22-0031-1.txt	2022/01/28 07:06:50	1.2
+++ ai22s/ai22-0031-1.txt	2022/02/04 03:54:24	1.3
@@ -1,4 +1,4 @@
-!standard 4.3.5(44/5)                                    22-01-27  AI22-0031-1/02
+!standard 4.3.5(44/5)                                    22-02-03  AI22-0031-1/03
 !standard 4.3.5(46/5)
 !standard 4.3.5(53/5)
 !class binding interpretation 22-01-26
@@ -19,12 +19,12 @@
 The expressions of a named container aggregate that are an indexed aggregate
 or have Add_Named are evaluated once for each value covered by each choice.
 
-!question
+!issue
 
 (1) The key type, element type, and container type of a container aggregate
 are given by the required profiles of the subprograms specified in an
 Aggregate aspect. However, there are no limitations on the subtypes of those
-types in those subprograms. Clearly, we want any contraints and/or predicates
+types in those subprograms. Clearly, we want any constraints and/or predicates
 of the parameter types to be enforced. But there is no wording about
 converting values to the appropriate subtype. Should we add such 
 wording? (Yes.)
@@ -67,7 +67,7 @@
   * for a positional_container_aggregate that is an indexed aggregate, each 
     expression is evaluated in an arbitrary order, and the Assign_Indexed 
     procedure is invoked [in sequence]{once for each expression of the 
-    aggregate with the anonymous object A as the first parameter, the key value
+    aggregate} with the anonymous object A as the first parameter, the key value
     as the second parameter, computed by starting with the low bound of the
     subtype of the key formal parameter of the Assign_Indexed procedure and
     taking the successor of this value for each successive expression{ of the
@@ -82,7 +82,7 @@
     by the key_choice (in an arbitrary order), with the anonymous object A as
     the first parameter, the value from the key_choice as the second parameter,
     and the result of evaluating the expression of the
-    container_element_assocation as the third parameter;
+    container_element_association as the third parameter;
 
 !discussion
 
@@ -98,7 +98,7 @@
 
 We used a blanket rule as the subtypes in question don't have names. So one
 would have to say something like "converted to the subtype of the second
-formal paramete of Add_Unnamed" in each place. There are 17 such places in
+formal parameter of Add_Unnamed" in each place. There are 17 such places in
 4.3.5(31-53/5), so that would add a lot of wording which would distract from
 the actual meaning.
 
@@ -107,7 +107,7 @@
 made in parallel (a capability not yet supported in Ada 2022). The only 
 requirement is that the index be increasing for each expression. We add
 "of the aggregate" to the wording to try to clarify that the index value isn't
-related to the order in which the the calls are made, just to the order of the
+related to the order in which the calls are made, just to the order of the
 expressions in the aggregate.
 
 (3) The proposed wording requires that the key_choice be evaluated before the