first two sections of "your first python program" chapter

porting-code-to-python-3-with-2to3.html

@@ -799,7 +799,7 @@ except:
 <li>The <code>sum()</code> function will also work with an iterator, so <code>2to3</code> makes no changes here either.  Like <a href="#dict">dictionary methods that return views instead of lists</a>, this applies to <code>min()</code>, <code>max()</code>, <code>sum()</code>, <code>list()</code>, <code>tuple()</code>, <code>set()</code>, <code>sorted()</code>, <code>any()</code>, and <code>all()</code>.
 </ol>
 <h2 id="raw_input"><code>raw_input()</code> and <code>input()</code> global functions</h2>
-<p>Python 2 had two global functions for asking the user for input on the command line.  The first, called <code>input()</code>, expected the user to enter a Python expression (and returned the result).  The second, called <code>raw_input()</code>, just returned whatever the user typed.  This was wildly confusing for beginners and wildly regarded as a &#8220;wart&#8221; in the language.  Python 3 excises this wart by renaming <code>raw_input()</code> to <code>input()</code>, so it works the way everyone naively expects it to work.
+<p>Python 2 had two global functions for asking the user for input on the command line.  The first, called <code>input()</code>, expected the user to enter a Python expression (and returned the result).  The second, called <code>raw_input()</code>, just returned whatever the user typed.  This was wildly confusing for beginners and widely regarded as a &#8220;wart&#8221; in the language.  Python 3 excises this wart by renaming <code>raw_input()</code> to <code>input()</code>, so it works the way everyone naively expects it to work.
 <p class="skip"><a href="#skipcompareraw_input">skip over this table</a>
 <table id="compareraw_input">
 <tr><th>Notes</th>