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

--- ai05s/ai05-0228-1.txt	2011/05/07 00:35:51	1.8
+++ ai05s/ai05-0228-1.txt	2011/11/01 05:32:53	1.9
@@ -69,7 +69,7 @@
 
 Modify 3.3.1(21):
 
-There is no implicit initial value for a scalar subtype{ unless the
+There is no implicit initial value defined for a scalar subtype{ unless the
 Default_Value aspect has been specified for the type}. In the absence of an
 explicit initialization{ or the specification of the Default_Value
 aspect}, a newly created scalar object might have a value that does
@@ -227,7 +227,7 @@
 @dinst
 @xbullet<The implicit initial value for a scalar subtype that has the Default_Value
 aspect specified is the value of that aspect converted to the nominal subtype
-(which might raise Constraint_Error @emdash see 4.6, “Type Conversions”);>
+(which might raise Constraint_Error @emdash see 4.6, "Type Conversions");>
 
 !corrigendum 3.3.1(13)
 
@@ -242,7 +242,7 @@
 @dby
 For a (definite) composite subtype, the implicit initial value of each component
 with a @fa<default_expression> is obtained by evaluation of this expression and
-onversion to the component's nominal subtype (which might raise Constraint_Error),
+conversion to the component's nominal subtype (which might raise Constraint_Error),
 unless the component is a discriminant of a constrained subtype (the previous case),
 or is in an excluded @fa<variant> (see 3.8.1).
 For each component that does not have a @fa<default_expression>, if the composite
@@ -258,7 +258,7 @@
 an explicit initialization, a newly created scalar object might have a value that
 does not belong to its subtype (see 13.9.1 and H.1). 
 @dby
-There is no implicit initial value for a scalar subtype unless the
+There is no implicit initial value defined for a scalar subtype unless the
 Default_Value aspect has been specified for the type. In the absence of an
 explicit initialization or the specification of the Default_Value
 aspect, a newly created scalar object might have a value that does