Finish fixing html files in 2004

There is one thing brought up on GitHub that might necessitate a minor
change but that can happen later.

bugs.html

@@ -2228,24 +2228,21 @@ sentence 2, and so fails to display responses from <code>hibachi</code>.</p>
 <h3 id="source-code-2004jdalbecjdalbec.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/jdalbec/jdalbec.c">2004/jdalbec/jdalbec.c</a></h3>
 <h3 id="information-2004jdalbecindex.html">Information: <a href="2004/jdalbec/index.html">2004/jdalbec/index.html</a></h3>
 <p>The author stated that:</p>
-<pre><code>    Arguments matching `/[^2]22$/` cause the program to segfault
-    after rapidly exhausting the available stack space.  I could
-    probably fix this by adding some special cases to the code,
-    but [Blaine the Mono] it&#39;s quite a bit more exciting this way,
-    don&#39;t you think?[/Blaine]  Since the trailing `22` will be
-    its own atom anyway, you can just insert a space in front of
-    it if you run into this feature (e.g. `1 22` instead of `122`).
-
-    Arguments matching `/(?:.){10,}/` will produce visually incorrect
-    results (e.g., generation 1 starting from 1111111111 will
-    print as `: 1`), but there&#39;s nothing interesting about these
-    arguments that can&#39;t be modeled using shorter runs of the same
-    symbol.
-
-    Arguments matching `/(?:.){257,}/` may produce mathematically
-    incorrect results (e.g., generation 1 starting from a string
-    of 257 `1`s will be calculated as `11`); the remark from the
-    previous paragraph applies here also.</code></pre>
+<blockquote>
+<p>Arguments matching <code>/[^2]22$/</code> cause the program to segfault after rapidly
+exhausting the available stack space. I could probably fix this by adding some
+special cases to the code, but [Blaine the Mono] it’s quite a bit more exciting
+this way, don’t you think?[/Blaine] Since the trailing <code>22</code> will be its own
+atom anyway, you can just insert a space in front of it if you run into this
+feature (e.g. <code>1 22</code> instead of <code>122</code>).</p>
+<p>Arguments matching <code>/(?:.){10,}/</code> will produce visually incorrect results
+(e.g., generation 1 starting from 1111111111 will print as <code>: 1</code>), but there’s
+nothing interesting about these arguments that can’t be modeled using shorter
+runs of the same symbol.</p>
+<p>Arguments matching <code>/(?:.){257,}/</code> may produce mathematically incorrect
+results (e.g., generation 1 starting from a string of 257 <code>1</code>s will be
+calculated as <code>11</code>); the remark from the previous paragraph applies here also.</p>
+</blockquote>
 <div id="2004_sds">
 <h2 id="sds">2004/sds</h2>
 </div>