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

--- ai05s/ai05-0177-1.txt	2010/06/14 01:07:27	1.2
+++ ai05s/ai05-0177-1.txt	2010/10/19 03:51:18	1.3
@@ -14,7 +14,7 @@
 !problem
 
 With the advent of pre and postconditions (see AI05-0145-1), and conditional
-expressions (see AI05-0147-1), expressions in specification are going to grow
+expressions (see AI05-0147-1), expressions in specifications are going to grow
 much larger and become more complicated. It is important that parts of such
 expressions can be abstracted.
 
@@ -105,9 +105,6 @@
 Including both this and the formal subprogram default would make this completely
 similar to null procedures.
 
----
-
-
 !example
 
 ** TBD **
@@ -2165,7 +2162,8 @@
 > I probably am; see my paper on this topic. I needed a way to
 > differentiate pure runtime checks (which I called "assertions") from
 > checks that can usefully be analyzed statically (which I called
-> "contracts"). Maybe there is a better term for the latter, but that is always what I meant by "contracts"
+> "contracts"). Maybe there is a better term for the latter, but that is always
+> what I meant by "contracts"
 
 That's REALLY confusing terminology. As Bob says, the word contract is strongly
 associated with Ada (as in the trademarked phrase programming by contract) and