fix join's type

[lambda.git] / topics / week7_introducing_monads.mdwn

diff --git a/topics/week7_introducing_monads.mdwn b/topics/week7_introducing_monads.mdwn
index 6bfa13c..61012d5 100644 (file)
--- a/topics/week7_introducing_monads.mdwn
+++ b/topics/week7_introducing_monads.mdwn
@@ -56,7 +56,7 @@ type variable instantiates to. So if our box type is `α list`, and `α` instant
 
 <u>int</u>
 
-for the type of a boxed `int`. (We'll fool with the markup to make this show a genuine box later; for now it will just display as underlined.)
+for the type of a boxed `int`.
 
 
 
@@ -105,7 +105,7 @@ Here are the types of our crucial functions, together with our pronunciation, an
 
 <code>=&lt;&lt; or mdnib (flip mbind) (<u>Q</u>) -> (Q -> <u>R</u>) -> (<u>R</u>)</code>
 
-<code>join: <span class="double">P</span> -> <u>P</u></code> 
+<code>join: <span class="box2">P</span> -> <u>P</u></code> 
 
 
 The menagerie isn't quite as bewildering as you might suppose. Many of these will
@@ -371,7 +371,7 @@ Compare the new definitions of `safe_add3` and `safe_div3` closely: the definiti
 for `safe_add3` shows what it looks like to equip an ordinary operation to
 survive in dangerous presupposition-filled world. Note that the new
 definition of `safe_add3` does not need to test whether its arguments are
-None values or real numbers---those details are hidden inside of the
+`None` values or real numbers---those details are hidden inside of the
 `bind` function.
 
 Note also that our definition of `safe_div3` recovers some of the simplicity of