Integrating my changes, mostly minor/cosmetic fixes; plus a big Windows lib update

1 files changed, 5 insertions, 5 deletions

diff --git a/doc/effects.txt b/doc/effects.txt
index 85de1ffdf..8084ae17a 100755
--- a/doc/effects.txt
+++ b/doc/effects.txt
@@ -9,7 +9,7 @@ explicit like in Haskell?
 The idea is that side effects and partial evaluation belong together:
 Iff a proc is side effect free and all its argument are evaluable at
 compile time, it can be evaluated by the compiler. However, really
-difficult is the ``newString`` proc: If it is simply wrapped, it 
+difficult is the ``newString`` proc: If it is simply wrapped, it
 should not be evaluated at compile time! On other occasions it can
 and should be evaluted:
 
@@ -20,22 +20,22 @@ and should be evaluted:
       result[i] = toUpper(s[i])
 
 No, it really can always be evaluated. The code generator should transform
-``s = "\0\0\0..."`` back into ``s = newString(...)``. 
+``s = "\0\0\0..."`` back into ``s = newString(...)``.
 
 
-``new`` cannot be evaluated at compile time either. 
+``new`` cannot be evaluated at compile time either.
 
 
 Raise statement
 ===============
 
-It is impractical to consider ``raise`` a statement with side effects.
+It is impractical to consider ``raise`` as a statement with side effects.
 
 
 Solution
 ========
 
 Being side effect free does not suffice for compile time evaluation. However,
-the evaluator can attempt to evaluate at compile time. 
+the evaluator can attempt to evaluate at compile time.