CVS difference for ai05s/ai05-0146-1.txt

--- ai05s/ai05-0146-1.txt	2010/10/16 06:24:40	1.10
+++ ai05s/ai05-0146-1.txt	2010/10/20 00:00:44	1.11
@@ -1,4 +1,4 @@
-!standard 13.3.3 (00)                                10-10-15  AI05-0146-1/07
+!standard 13.3.3 (00)                                10-10-19  AI05-0146-1/08
 !class amendment 09-02-15
 !status Amendment 2012 10-09-02
 !status ARG Approved  8-0-1  10-06-20
@@ -23,14 +23,14 @@
 invariants appeared on the specification of the types and packages rather
 than buried in the body, as it really represents part of the contract. In
 particular, one wants any implementation of a given package spec to conform
-to all of invariants specified, in the same way one wants any
+to all of the specified invariants, in the same way one wants any
 implementation of a package to conform to the constraints of the parameter
 and result subtypes of the visible subprograms of the package.
 
 Note that type invariants are not the same thing as constraints, as
 invariants apply to all values of a type, while constraints are
 generally used to identify a subset of the values of a type.  Invariants
-are only meaningful on private types, where there is a clear boundary
+are only meaningful for private types, where there is a clear boundary
 (the enclosing package) that separates where the invariant applies
 (outside) and where it need not be satisfied (inside). In some ways, an
 invariant is more like the range of values specified when declaring a