From e32a6a02ee6a14cd85c715979503a58b0d661085 Mon Sep 17 00:00:00 2001
From: "Kartik K. Agaram" <vc@akkartik.com>
Date: Wed, 27 Apr 2016 17:59:46 -0700
Subject: 2878

---
 html/chessboard.mu.html | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

(limited to 'html')

diff --git a/html/chessboard.mu.html b/html/chessboard.mu.html
index d4241248..f1b1c16f 100644
--- a/html/chessboard.mu.html
+++ b/html/chessboard.mu.html
@@ -45,16 +45,11 @@ body { font-size: 12pt; font-family: monospace; color: #eeeeee; background-color
   <span class="Comment"># In mu it is good form (though not required) to explicitly show the</span>
   <span class="Comment"># hardware you rely on.</span>
   <span class="Comment">#</span>
-  <span class="Comment"># The chessboard also returns the same keyboard and screen objects. In mu it</span>
-  <span class="Comment"># is good form to not modify ingredients of a function unless they are also</span>
-  <span class="Comment"># results. Here we clearly modify both keyboard and screen, so we return</span>
-  <span class="Comment"># both.</span>
-  <span class="Comment">#</span>
   <span class="Comment"># Here the console and screen are both 0, which usually indicates real</span>
   <span class="Comment"># hardware rather than a fake for testing as you'll see below.</span>
   chessboard <span class="Constant">0/screen</span>, <span class="Constant">0/console</span>
 
-  close-console  <span class="Comment"># cleanup screen, keyboard and mouse</span>
+  close-console  <span class="Comment"># clean up screen, keyboard and mouse</span>
 ]
 
 <span class="SalientComment">## But enough about mu. Here's what it looks like to run the chessboard program.</span>
-- 
cgit 1.4.1-2-gfad0