Change label= to marker= on <ol>.

Author: jdeisenberg

pretext/Debugging/HowtoAvoidDebugging.ptx

@@ -3,7 +3,7 @@
   <title>How to Avoid Debugging</title>
   <p>Perhaps the most important lesson in debugging is that it is <term>largely avoidable</term> &#x2013; if you work carefully.</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p><term>Understand the Problem</term>  You must have a firm grasp on <term>what</term> you are trying to accomplish but not
                     necessarily <term>how</term> to do it. You do not need to understand the entire problem. But you must understand

pretext/Debugging/KnowyourerrorMessages.ptx

@@ -349,7 +349,7 @@ print(time_when_alarm_go_off)
     </hint>
     <p><term>Finding Clues</term>  With name errors one of the best things you can do is use the editor, or browser search function.  Quite often if you search for the exact word in the error message one of two things will happen:</p>
     <p>
-      <ol label="1">
+      <ol marker="1">
         <li>
           <p>The word you are searching for will appear only once in your code, it's also likely that it will be on the right hand side of an assignment statement, or as a parameter to a function.  That should confirm for you that you have a typo somewhere.  If the name in question <term>is</term> what you thought it should be then you probably have a typo on the left hand side of an assignment statement on a line before your error message occurs.  Start looking backward at your assignment statements.  In some cases it's really nice to leave all the highlighted strings from the search function visible as they will help you very quickly find a line where you might have expected your variable to be highlighted.</p>
         </li>
@@ -390,7 +390,7 @@ print(alarm_time)
         <title>Solution</title>
         <p>In this example the error message is about <c>set_time</c> not defined on line 3.  In this case the undefined name is not used in an assignment statement, but is used as a parameter (incorrectly) to a function call.   A search on <c>set_time</c> reveals that in fact it is only used once in the program.  Did the author mean <c>set_alarm</c>?  If we make that assumption we immediately get another error <c>NameError: name 'alarm_time' is not defined on line: 3</c>.  The variable <c>alarm_time</c> is defined on line 4, but that does not help us on line 3.  Furthermore we now have to ask the question is this function call <c>int(present_time, set_alarm, alarm_time)</c> even the correct use of the <c>int</c> function?  The answer to that is a resounding no.  Let's list all of the things wrong with line 3:</p>
         <p>
-          <ol label="1">
+          <ol marker="1">
             <li>
               <p><c>set_time</c> is not defined and never used, the author probably meant <c>set_alarm</c>.</p>
             </li>

pretext/Dictionaries/Exercises.ptx

@@ -59,7 +59,7 @@ for char in sorted(keys):
     <p>Give the Python interpreter's response to each of the following from a
                     continuous interpreter session:</p>
     <p>
-      <ol label="a">
+      <ol marker="a">
         <li>
           <program language="python">
             <input>

pretext/Functions/Functionscancallotherfunctions.ptx

@@ -139,7 +139,7 @@ wn.exitonclick()
             new functions. Actually, there are a lot of reasons, but this example
             demonstrates two:</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p>Creating a new function gives you an opportunity to name a group of
                     statements. Functions can simplify a program by hiding a complex computation

pretext/Functions/ProgramDevelopment.ptx

@@ -131,7 +131,7 @@ test.testEqual(distance(0,0, 1,1), 1.41)
             to chunk music &#x2014; from indvidual notes to chords, bars, phrases, and so on.</p>
   <p>The key aspects of the process are:</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p>Make sure you know what you are trying to accomplish. Then you can write appropriate unit tests.</p>
       </li>

pretext/Functions/functions.ptx

@@ -23,7 +23,7 @@ def name( parameters ):
             several <term>compound statements</term> we will see, all of which have the same
             pattern:</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p>A header line which begins with a keyword and ends with a colon.</p>
       </li>

pretext/GUIandEventDrivenProgramming/11_gui_program_example.ptx

@@ -11,7 +11,7 @@
             developed. For a typical GUI program development, you are encouraged to go
             through these stages:</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p>Using scratch paper, physically draw a rough sketch of your user interface.</p>
       </li>

pretext/IntroRecursion/ConvertinganIntegertoaStringinAnyBase.ptx

@@ -19,7 +19,7 @@
   <p>Knowing what our base is suggests that the overall algorithm will
             involve three components:</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p>Reduce the original number to a series of single-digit numbers.</p>
       </li>

pretext/IntroRecursion/TheThreeLawsofRecursion.ptx

@@ -4,7 +4,7 @@
   <p>Like the robots of Asimov, all recursive algorithms must obey three
             important laws:</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p>A recursive algorithm must have a <term>base case</term>.</p>
       </li>

pretext/Lists/Exercises.ptx

@@ -56,7 +56,7 @@ print(myList)
     <statement>
       <p>Starting with the list of the previous exercise, write Python statements to do the following:</p>
       <p>
-        <ol label="a">
+        <ol marker="a">
           <li>
             <p>Append <q>apple</q> and 76 to the list.</p>
           </li>
@@ -366,7 +366,7 @@ def count(lst):
     <statement>
       <p>Although Python provides us with many list methods, it is good practice and very instructive to think about how they are implemented.  Implement a Python function that works like the following:</p>
       <p>
-        <ol label="a">
+        <ol marker="a">
           <li>
             <p>count</p>
           </li>