Working on spelling

docs/build/index.html

@@ -561,7 +561,7 @@ <h2 id="build-better">Section 19.4: A Better Design</h2>
 <ol>
 <li>
 <p>The configuration might not come directly from a JSON file—for example,
-    it might be embedded in a larger file or generated by anothe prrogram—so
+    it might be embedded in a larger file or generated by another program—so
     we should modify the constructor to take the loaded JSON configuration as input.</p>
 </li>
 <li>

docs/dup/index.html

@@ -421,12 +421,12 @@ <h2 id="dup-start">Section 3.1: Getting Started</h2>
 </thead>
 <tbody>
 <tr>
-<td>aaa</td>
-<td>aaa</td>
-<td>aaa</td>
-<td>bb</td>
-<td>bb</td>
-<td>c</td>
+<td><code>aaa</code></td>
+<td><code>aaa</code></td>
+<td><code>aaa</code></td>
+<td><code>bb</code></td>
+<td><code>bb</code></td>
+<td><code>c</code></td>
 </tr>
 </tbody>
 </table>
@@ -539,7 +539,7 @@ <h2 id="dup-group">Section 3.2: Hashing Files</h2>
 but is it?
 As a more stringent test,
 let&rsquo;s try hashing every line of text in
-<a href="https://www.gutenberg.org/">Project Gutenberg</a>&lsquo;s version of the novel <em>Dracula</em>
+the <a href="https://www.gutenberg.org/">Project Gutenberg</a> version of the novel <em>Dracula</em>
 and plot the distribution (<a class="fig-ref" href="../dup/#dup-naive-dracula">Figure 3.3</a>).</p>
 <figure id="dup-naive-dracula">
 <img src="./naive_dracula.svg" alt="Hash codes of <em>Dracula</em>"/>

docs/finale/index.html

@@ -345,7 +345,8 @@ <h1>Chapter 27: Conclusion</h1>
 <figcaption markdown="1">Figure 27.1: De Rosa SK Pininfarina bicycle.</figcaption>
 </figure>
 
-<p>Consider the bicycle–more specifically,
+<p>Consider the bicycle:
+more specifically,
 the De Rosa SK Pininfarina (<a class="fig-ref" href="../finale/#finale-bicycle">Figure 27.1</a>).
 I think it&rsquo;s beautiful,
 but I wouldn&rsquo;t call it art,

docs/intro/index.html

@@ -559,7 +559,7 @@ <h2 id="intro-acknowledgments">Section 1.6: Acknowledgments</h2>
 <div class="center">
 <p><em>This one&rsquo;s for Mike and Jon:</em>
   <br>
-  <em>I&rsquo;m glad you always found time to chat.</em></p>
+  <em>I am glad you always found time to chat.</em></p>
 </div>
         </main>
       </div>

docs/undo/index.html

@@ -358,7 +358,7 @@ <h1>Chapter 24: Undo and Redo</h1>
 we will also implement undo,
 which will introduce another commonly-used software design pattern.</p>
 <h2 id="undo-start">Section 24.1: Getting Started</h2>
-<p>Our file fiewer has four classes (<a class="fig-ref" href="../undo/#undo-classes">Figure 24.1</a>):</p>
+<p>Our file viewer has four classes (<a class="fig-ref" href="../undo/#undo-classes">Figure 24.1</a>):</p>
 <ul>
 <li>
 <p>A <code>Window</code> can draw lines and report its size.</p>
@@ -753,7 +753,7 @@ <h2 id="undo-backward">Section 24.3: Going Backward</h2>
 so we are essentially undoing our undo forever.
 The solution is to modify the base class <code>Action</code> to have a <code>.save</code> method
 that tells the application whether or not to save this action.
-The default implemenation returns <code>True</code>,
+The default implementation returns <code>True</code>,
 but we override it in <code>Undo</code> to return <code>False</code>:</p>
 <div class="code-sample lang-py" title="undoable.py">
 <div class="highlight"><pre><span></span><code><span class="k">class</span> <span class="nc">Undo</span><span class="p">(</span><span class="n">Action</span><span class="p">):</span>

info/bibliography.bib

@@ -29,7 +29,7 @@ @book{Brand1995
 @book{Bentley1982,
   author = {Jon Louis Bentley},
   title = {Writing Efficient Programs},
-  publisher = {Prentice Hall {PTR}},
+  publisher = {Prentice-Hall {PTR}},
   year = {1982},
   isbn = {978-0139702440}
 }

info/glossary.yml

@@ -22,7 +22,7 @@
   en:
     term: abstract base class
     def: >
-      An [abstract_class](#abstract_class) from which the [class](#class)
+      An [abstract class](#abstract_class) from which the [class](#class)
       in question is derived.
 
 - key: abstract_class
@@ -1427,7 +1427,7 @@
     full : JavaScript Object Notation
     def: >
       A way to represent data by combining basic values like numbers and
-      character strings in [lists](#list) and [key/value](#dictionary)
+      character strings in [lists](#list) and [key-value](#dictionary)
       structures. The acronym stands for "JavaScript Object Notation"; unlike
       better-defined standards like [XML](#xml), it is unencumbered by a syntax
       for comments or ways to define a [schema](#schema).