fix HTML problems associated with leading ---'s

Please do not use "**---**" in markdown lines to separate sections.

This causes `pandoc(1)` to generate "**\<hr />**".

The "**\<hr />**" has no effect in standard HTML 5 and interacts
badly with unquoted attribute values.

If a horizontal line is really needed, use "**\<hr>**".

If a short line is needed, use: "**\<hr
style="width:10%;text-align:left;margin-left:0">**"

2019/duble/README.md

@@ -54,7 +54,7 @@ Alternatively, if you want to change the size, do something like:
 
 The author provided us with the following table for use:
 
----
+<hr style="width:10%;text-align:left;margin-left:0">
 
 * **Arrow keys**: move cursor.
 * `p` key: enter *pen* mode (type **p** again to return to the default *move*
@@ -76,7 +76,7 @@ After editing the file and quitting, try:
 i.e. execute the file.
 
 
----
+<hr style="width:10%;text-align:left;margin-left:0">
 
 WARNING: if the file is deleted it might lock any session still in use. These
 will have to be killed from another shell session or by closing the terminal tab

2019/duble/index.html

@@ -171,7 +171,7 @@ See <a href="#alternate-code">Alternate code</a> below if you are curious.</p>
 <p>Alternatively, if you want to change the size, do something like:</p>
 <pre><code>    make clobber LINES=20 COLUMNS=20 all</code></pre>
 <p>The author provided us with the following table for use:</p>
-<hr />
+<hr style="width:10%;text-align:left;margin-left:0">
 <ul>
 <li><strong>Arrow keys</strong>: move cursor.</li>
 <li><code>p</code> key: enter <em>pen</em> mode (type <strong>p</strong> again to return to the default <em>move</em>
@@ -186,7 +186,7 @@ the editor.</p>
 <p>After editing the file and quitting, try:</p>
 <pre><code>    /tmp/drawing</code></pre>
 <p>i.e. execute the file.</p>
-<hr />
+<hr style="width:10%;text-align:left;margin-left:0">
 <p>WARNING: if the file is deleted it might lock any session still in use. These
 will have to be killed from another shell session or by closing the terminal tab
 (in other words don’t do this from the console!). If the file cannot be opened

2019/mills/README.md

@@ -398,19 +398,23 @@ with `RNN(h, x)` defined as above.  Each RNN module has its own set of
 parameters and its own hidden state vector.  This will improve the network's
 performance, at the cost of a much larger parameter space.
 
----
+<hr style="width:10%;text-align:left;margin-left:0">
 
-**IMPORTANT NOTE**: Since OMLET uses the system stack for network storage,
+**IMPORTANT NOTE**:
+
+```
+Since OMLET uses the system stack for network storage,
 larger networks may cause OMLET to crash (typically with a message like
-`Segmentation fault`) unless the system stack size is first increased.
+Segmentation fault) unless the system stack size is first increased.
 The exact command for doing so depends on your shell and your system's
-hard limits.  On `sh`/`ksh`/`bash` shells, you can view the hard limit
-with `ulimit -Hs` and set it with `ulimit -s 65532` (replacing `65532`
-with the actual hard limit).  On `csh`/`tcsh` shells, you can view
-the hard limit with `limit -h stacksize` and set it with
-`limit stacksize 65532` (replacing `65532` with the actual hard limit).
+hard limits.  On sh/ksh/bash shells, you can view the hard limit
+with ulimit -Hs and set it with ulimit -s 65532 (replacing 65532
+with the actual hard limit).  On csh/tcsh shells, you can view
+the hard limit with limit -h stacksize and set it with
+limit stacksize 65532 (replacing 65532 with the actual hard limit).
+```
 
----
+<hr style="width:10%;text-align:left;margin-left:0">
 
 You can try the deeper network by doing
 

2019/mills/index.html

@@ -435,17 +435,18 @@ other:</p>
 <p>with <code>RNN(h, x)</code> defined as above. Each RNN module has its own set of
 parameters and its own hidden state vector. This will improve the network’s
 performance, at the cost of a much larger parameter space.</p>
-<hr />
-<p><strong>IMPORTANT NOTE</strong>: Since OMLET uses the system stack for network storage,
+<hr style="width:10%;text-align:left;margin-left:0">
+<p><strong>IMPORTANT NOTE</strong>:</p>
+<pre><code>Since OMLET uses the system stack for network storage,
 larger networks may cause OMLET to crash (typically with a message like
-<code>Segmentation fault</code>) unless the system stack size is first increased.
-The exact command for doing so depends on your shell and your system’s
-hard limits. On <code>sh</code>/<code>ksh</code>/<code>bash</code> shells, you can view the hard limit
-with <code>ulimit -Hs</code> and set it with <code>ulimit -s 65532</code> (replacing <code>65532</code>
-with the actual hard limit). On <code>csh</code>/<code>tcsh</code> shells, you can view
-the hard limit with <code>limit -h stacksize</code> and set it with
-<code>limit stacksize 65532</code> (replacing <code>65532</code> with the actual hard limit).</p>
-<hr />
+Segmentation fault) unless the system stack size is first increased.
+The exact command for doing so depends on your shell and your system&#39;s
+hard limits.  On sh/ksh/bash shells, you can view the hard limit
+with ulimit -Hs and set it with ulimit -s 65532 (replacing 65532
+with the actual hard limit).  On csh/tcsh shells, you can view
+the hard limit with limit -h stacksize and set it with
+limit stacksize 65532 (replacing 65532 with the actual hard limit).</code></pre>
+<hr style="width:10%;text-align:left;margin-left:0">
 <p>You can try the deeper network by doing</p>
 <pre><code>    make rnn2</code></pre>
 <p>(or even <code>make rnn3</code> if you want a three-layer RNN) and train it with</p>