X-Git-Url: http://lambda.jimpryor.net/git/gitweb.cgi?p=lambda.git;a=blobdiff_plain;f=week4.mdwn;h=58d6bc38204bd3bcbf4afabe6d9c4306b82735de;hp=8353afb79a49f7e0a8de035021d471fcf3d3d936;hb=73b21c99d5a3f8184681a1fa1e0bb2b44ab4c34f;hpb=6d58ca4a1e34835770dcb3213cc95470209b06ec;ds=sidebyside

diff --git a/week4.mdwn b/week4.mdwn
index 8353afb7..58d6bc38 100644
--- a/week4.mdwn
+++ b/week4.mdwn
@@ -520,12 +520,11 @@ but really all we're in a position to mean by that are claims about the result
 of the complex expression semantically depending only on this, not on that. A
 demon evaluator who custom-picked the evaluation order to make things maximally
 bad for you could ensure that all the semantically unnecessary computations got
-evaluated anyway. We don't have any way to prevent that. Later,
-we'll see ways to *semantically guarantee* one evaluation order rather than
-another. Though even then the demonic evaluation-order-chooser could make it
-take unnecessarily long to compute the semantically guaranteed result. Of
-course, in any real computing environment you'll know you're dealing with a
-fixed evaluation order and you'll be able to program efficiently around that.
+evaluated anyway. We don't yet know any way to prevent that. Later, we'll see
+ways to *guarantee* one evaluation order rather than another. Of
+course, in any real computing environment you'll know in advance that you're
+dealing with a fixed evaluation order and you'll be able to program efficiently
+around that.
 
 In detail, then, here's what our v5 lists will look like:
 
@@ -595,7 +594,7 @@ detail](http://okmij.org/ftp/Streams.html#enumerator-stream).
 >	
 >			f a (f b (f c (f d (f e z))))
 >	
->	The left fold on the other hand starts combining `z` with elements from the left. `f z z` is then combined with `b`, and so on:
+>	The left fold on the other hand starts combining `z` with elements from the left. `f z a` is then combined with `b`, and so on:
 >	
 >			f (f (f (f (f z a) b) c) d) e
 >