fix formatting in thanks-for-help.html HTML in bugs.html

Attempted to fix formatting problems of `thanks-for-help.html`
that was introduced in commit 476b0d45f0.

Fixed some HTML info notices in `bugs.html` as well.

bugs.html

@@ -2780,23 +2780,29 @@ touched either.</p>
 <h3 id="source-code-2019karnsprog.c">Source code: <a href="2019/karns/prog.c">2019/karns/prog.c</a></h3>
 <h3 id="information-2019karnsindex.html">Information: <a href="2019/karns/index.html">2019/karns/index.html</a></h3>
 <p>The author stated the following:</p>
-<hr />
-<ul>
-<li>The program must be ran in a terminal that supports ANSI escape codes for
-moving the cursor and changing colors.</li>
-<li>Segfaults happen sometimes.</li>
-<li>I don’t know what memory management there is, if any.</li>
-<li>The program will not compile by an ANSI C compiler: it uses for loops, and
-it uses C++ style comments. It should compile cleanly using a C99 standard.</li>
-<li>Breadth first search is slow (and very slow on certain maps), but my A star
-version of this program is too big.</li>
-<li>Lots of extra whitespace may be needed if you want to feed in an arbitrary
-file.</li>
-<li>It fails to compile on GCC sometimes (according to a friend of mine, I’ve
-not encountered this myself).</li>
-<li>The program could be obfuscated much further.</li>
-<li>The program contains some unused code and data.</li>
-</ul>
+<pre><code>    - The program must be ran in a terminal that supports ANSI escape
+      codes for moving the cursor and changing colors.
+
+    - Segfaults happen sometimes.
+
+    - I don&#39;t know what memory management there is, if any.
+
+    - The program will not compile by an ANSI C compiler: it uses
+      for loops, and it uses C++ style comments. It should compile
+      cleanly using a C99 standard.
+
+    - Breadth first search is slow (and very slow on certain maps),
+      but my A star version of this program is too big.
+
+    - Lots of extra whitespace may be needed if you want to feed in
+      an arbitrary file.
+
+    - It fails to compile on GCC sometimes (according to a friend
+      of mine, I&#39;ve not encountered this myself).
+
+    - The program could be obfuscated much further.
+
+    - The program contains some unused code and data.</code></pre>
 <div id="2019_lynn">
 <h2 id="lynn">2019/lynn</h2>
 </div>
@@ -2818,17 +2824,15 @@ file you should delete all the checkpoint files because the format depends on
 both the network and the input – using the wrong checkpoint is likely to cause
 a crash.</p>
 <p>The author also wrote:</p>
-<hr />
-<p><strong>IMPORTANT NOTE</strong>: 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 />
+<pre><code>    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.
+    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>
 <div id="2019_poikola">
 <h2 id="poikola">2019/poikola</h2>
 </div>