X-Git-Url: http://lambda.jimpryor.net/git/gitweb.cgi?a=blobdiff_plain;f=topics%2Fweek1_advanced_notes.mdwn;h=203a22fcf1adb0a8fbf6726f3926099966599003;hb=6906b72ae2c64971056a409aa132a394eef64860;hp=3b49365a6e997dbcc347b579ccf62ec63ab6c3db;hpb=26ee92a52489d4249af8c5b1a0066b0e4e6be7e1;p=lambda.git

diff --git a/topics/week1_advanced_notes.mdwn b/topics/week1_advanced_notes.mdwn
index 3b49365a..203a22fc 100644
--- a/topics/week1_advanced_notes.mdwn
+++ b/topics/week1_advanced_notes.mdwn
@@ -51,7 +51,7 @@ I agree it's annoying that these conventions are so diverse. There are plenty ot
 
 A function value doesn't have any structure---at least none that's visible to the pattern-matching system. You can only match against simple patterns like `_` or the variable `f`.
 
-When matching a variable against a λ-generated function value in a `let`- or `letrec`-construction, there's an alternative syntax that you may find more convenient. This:
+When matching a λ-generated function value against a variable in a `let`- or `letrec`-construction, there's an alternative syntax that you may find more convenient. This:
 
 `let`  
   `f match` λ`x.` φ`;`  
@@ -156,7 +156,7 @@ but:
 
 is parsed as:
 
-   not (empty? xs)
+    not (empty? xs)
 
 
 ### Some common functions ###