X-Git-Url: http://lambda.jimpryor.net/git/gitweb.cgi?p=lambda.git;a=blobdiff_plain;f=week11.mdwn;h=cc7af5e2b3aad3cdcd41fe8dfa3cf4cf12ffe64a;hp=97416e2c1d5110145ac63ed8a9af67ed79f01393;hb=11976c4200a22c3bb279e5efeebbadc3ab3b835a;hpb=63822483bf23bc42870790e40e4424d862d36cd5

diff --git a/week11.mdwn b/week11.mdwn
index 97416e2c..cc7af5e2 100644
--- a/week11.mdwn
+++ b/week11.mdwn
@@ -183,7 +183,7 @@ For simplicity, I'll continue to use the abbreviated form:
 
 	{parent = ...; siblings = [subtree 20; *; subtree 80]}, * filled by subtree 50
 
-But that should be understood as standing for the more fully-spelled-out structure. Structures of this sort are called **tree zippers**, for a reason that will emerge. They should already seem intuitively similar to list zippers, though, at least in what we're using them to represent. I think it may initially be more helpful to call these **targetted trees**, though, and so will be switching back and forth between this different terms.
+But that should be understood as standing for the more fully-spelled-out structure. Structures of this sort are called **tree zippers**. They should already seem intuitively similar to list zippers, at least in what we're using them to represent. I think it may also be helpful to call them **targetted trees**, though, and so will be switching back and forth between these different terms.
 
 Moving left in our targetted tree that's targetted on `node 50` would be a matter of shifting the `*` leftwards: