CVS difference for ais/ai-00360.txt

--- ais/ai-00360.txt	2004/04/06 19:57:16	1.5
+++ ais/ai-00360.txt	2004/05/29 00:38:41	1.6
@@ -1,4 +1,4 @@
-!standard 07.06(09)                                    04-03-25  AI95-00360/04
+!standard 07.06(09)                                    04-05-27  AI95-00360/05
 !standard D.07(04)
 !standard A.4.5(72)
 !standard A.5.2(15)
@@ -28,7 +28,7 @@
 types. However, there are a number of language-defined types which, while not
 visibly controlled, might well be implemented using controlled types by some
 implementations. Are such types affected by No_Nested_Finalization? (Yes, see
-list in the !wording section.) Furthermore, the definition of
+list in the wording section.) Furthermore, the definition of
 No_Nested_Finalization doesn't take into account access discriminants, which
 can cause nested finalization to happen. Is this intended? (No.)
 
@@ -86,7 +86,7 @@
 
 The type File_Type needs finalization (see 7.6).
 
-Replace D.7(4) by:
+Replace D.7(4/1) by:
 
 No_Nested_Finalization
 
@@ -94,15 +94,15 @@
 designate a type that needs finalization (see 7.6) shall be declared only at
 library level.
 
-Add in the Static Semantics of D.15 (AI 297):
+Add in the Static Semantics of D.15 (AI-297):
 
 The type Timing_Event needs finalization (see 7.6).
 
-Add in the Static Semantics of D.14 (AI 307):
+Add in the Static Semantics of D.14 (AI-307):
 
 The type Timer needs finalization (see 7.6).
 
-Add in the Static Semantics of AI 354:
+Add in the Static Semantics of AI-354:
 
 The type Group_Budget needs finalization (see 7.6).