fixes to rst

Author: bnmnetp

_sources/FrontBackMatter/copyright.rst

@@ -9,11 +9,10 @@
 Copyright Notice
 ================
 
-|  Copyright (C)  Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
-|  Meyers, and Dario Mitchell.  Permission is granted to copy, distribute
-|  and/or modify this document under the terms of the GNU Free Documentation
-|  License, Version 1.3 or any later version published by the Free Software
-|  Foundation; with Invariant Sections being Forward, Prefaces, and
-|  Contributor List, no Front-Cover Texts, and no Back-Cover Texts.  A copy of
-|  the license is included in the section entitled "GNU Free Documentation
-|  License".
+Copyright (C)  Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
+Meyers, and Dario Mitchell.  Permission is granted to copy, distribute
+and/or modify this document under the terms of the GNU Free Documentation
+License, Version 1.3 or any later version published by the Free Software
+Foundation; with Invariant Sections being Forward, Prefaces, and
+Contributor List, no Front-Cover Texts, and no Back-Cover Texts.  A copy of
+the license is included in the section entitled "GNU Free Documentation License".

_sources/Functions/Functionsthatreturnvalues.rst

@@ -118,11 +118,6 @@ debugging
 easier.  These temporary variables are examples of **local variables**, pursued further
 in the next section.
 
-.. The line `toInvest = float(input("How much do you want to invest?"))`
-..  also shows yet another example
-..  of *composition* --- we can call a function like `float`, and its arguments
- .. can be the results of other function calls (like `input`) that we've called along the way.
-
 Notice something important here. The name of the variable we pass as an
 argument --- ``toSquare`` --- has nothing to do with the name of the formal parameter
 --- ``x``.  It is as if  ``x = toSquare`` is executed when ``square`` is called.

_sources/GUIandEventDrivenProgramming/12_model_view_controller.rst

@@ -95,7 +95,7 @@ four basic commands we need to send to the *model*:
 
 * A user clicked on something on the left frame.
 * The user wants to start a new game. (The user clicked on the "Start" button.)
-* The user wants to stop playing a game. (The user clicked on the "Stop button.)
+* The user wants to stop playing a game. (The user clicked on the "Stop" button.)
 * The user wants to quit the application. (The user clicked on the "Quit" button.)
 
 The *controller** needs to recognize these events and send them to appropriate

_sources/PythonTurtle/OurFirstTurtleProgram.rst

@@ -218,10 +218,10 @@ screen until we click on it.
    :answer_c: It makes the turtle draw half of a rectangle on the screen.
    :answer_d: Nothing, it is unnecessary.
    :correct: b
-   :feedback_a: The line &quotalex = turtle.Turtle()&quot is what actually creates the turtle object.
+   :feedback_a: The line "alex = turtle.Turtle()" is what actually creates the turtle object.
    :feedback_b: This line imports the module called turtle, which has all the built in functions for drawing on the screen with the Turtle object.
-   :feedback_c: This functionality is performed with the lines: &quotalex.forward(150)&quot, &quotlex.left(90)&quot, and &quotalex.forward(75)&quot
-   :feedback_d: If we leave it out, Python will give an error saying that it does not know about the name &quotturtle&quot when it reaches the line &quotwn = turtle.Screen()&quot
+   :feedback_c: This functionality is performed with the lines: "alex.forward(150)", "lex.left(90)", and "alex.forward(75)"
+   :feedback_d: If we leave it out, Python will give an error saying that it does not know about the name "turtle" when it reaches the line "wn = turtle.Screen()"
 
    Consider the following code:
 
@@ -260,11 +260,11 @@ screen until we click on it.
 
 .. mchoice:: test_question3_1_4
    :practice: T
-   :answer_a: <img src="../_static/test1Alt1.png" alt="right turn of 90 degrees before drawing, draw a line 150 pixels long, turn left 90, and draw a line 75 pixels long">
-   :answer_b: <img src="../_static/test1Alt2.png" alt="left turn of 180 degrees before drawing,  draw a line 150 pixels long, turn left 90, and draw a line 75 pixels long">
-   :answer_c: <img src="../_static/test1Alt3.png" alt="left turn of 270 degrees before drawing,  draw a line 150 pixels long, turn left 90, and draw a line 75 pixels long">
-   :answer_d: <img src="../_static/test1Alt4v2.png" alt="right turn of 270 degrees before drawing, draw a line 150 pixels long, turn right 90, and draw a line 75 pixels long">
-   :answer_e: <img src="../_static/test1correct.png" alt="left turn of 90 degrees before drawing,  draw a line 150 pixels long, turn left 90, and draw a line 75 pixels long">
+   :answer_a: <img src="../_static/test1Alt1.png" alt="right turn of 90 degrees before drawing, draw a line 150 pixels long, turn left 90, and draw a line 75 pixels long"/>
+   :answer_b: <img src="../_static/test1Alt2.png" alt="left turn of 180 degrees before drawing,  draw a line 150 pixels long, turn left 90, and draw a line 75 pixels long"/>
+   :answer_c: <img src="../_static/test1Alt3.png" alt="left turn of 270 degrees before drawing,  draw a line 150 pixels long, turn left 90, and draw a line 75 pixels long">/
+   :answer_d: <img src="../_static/test1Alt4v2.png" alt="right turn of 270 degrees before drawing, draw a line 150 pixels long, turn right 90, and draw a line 75 pixels long"/>
+   :answer_e: <img src="../_static/test1correct.png" alt="left turn of 90 degrees before drawing,  draw a line 150 pixels long, turn left 90, and draw a line 75 pixels long"/>
    :correct: e
    :feedback_a: This code would turn the turtle to the south before drawing
    :feedback_b: This code would turn the turtle to the west before drawing

_sources/Selection/BooleanFunctions.rst

@@ -107,7 +107,7 @@ the boolean expression causes a call to the ``isDivisible`` function.  This is v
    :answer_b: No
    :correct: a
    :feedback_a: It is perfectly valid to return the result of evaluating a Boolean expression.
-   :feedback_b: x +y < z is a valid Boolean expression, which will evaluate to True or False.  It is perfectly legal to return True or False from a function, and to have the statement to be evaluated in the same line as the return keyword.
+   :feedback_b: x +y &lt; z is a valid Boolean expression, which will evaluate to True or False.  It is perfectly legal to return True or False from a function, and to have the statement to be evaluated in the same line as the return keyword.
 
    Is the following statement legal in a Python function (assuming x, y and z are defined to be numbers)?
 

_sources/SimplePythonData/OrderofOperations.rst

@@ -51,8 +51,8 @@ rules for its mathematical operators that mathematics does.
 
 .. (The
 ..   acronym PEDMAS could mislead you to thinking that division has higher
-..   precedence than multiplication, and addition is done ahead of subtraction -
-..   don't be misled.  Subtraction and addition are at the same precedence, and
+..   precedence than multiplication, and addition is done ahead of subtraction.
+..   Don't be misled.  Subtraction and addition are at the same precedence, and
 ..   the left-to-right rule applies.)
 
 .. note::

_sources/UnitTesting/CheckingAssumptionsWithAssert.rst

@@ -239,7 +239,7 @@ to help streamline the diagnostic work.
    An ``assert`` statement displays output if the condition is True.
 
 .. mchoice:: mc_assert_2
-   :answer_a: assert len(msg) <= 0
+   :answer_a: assert len(msg) &lt;= 0
    :answer_b: assert len(msg) > 0
    :answer_c: assert msg[0]
    :answer_d: none of these

_sources/UnitTesting/DesigningTestableFunctions.rst

@@ -161,7 +161,7 @@ precondition and postcondition terminology in your docstrings, it helps to *thin
 **Check your understanding**
 
 .. mchoice:: mc_testable_2
-   :answer_a: len(msg) <= 0
+   :answer_a: len(msg) &lt;= 0
    :answer_b: len(msg) > 0
    :answer_c: msg == ""
    :answer_d: none of these

_sources/UnitTesting/TestingWithpytest.rst

@@ -247,7 +247,7 @@ sense, just remember: in order for pytest to work correctly, any code that is pa
             def grade(score):
                 global illegal, testA, testB, testF
 
-                if score > 100 or score < 0:
+                if score > 100 or score &lt; 0:
                     illegal = True
                     return ''
                 elif score >= 90: