Format fixes in html files from 2018

2018/burton1/README.md

@@ -51,7 +51,7 @@ One line, one array, one loop and one statement but it prints many bytes. It won
 
 Feed this anything on `stdin`.
 
-The [included script.sh](%%REPO_URL%%/2018/burton1/scripthd.sh) may be used as a driver program for this entry.
+The included [scripthd.sh](%%REPO_URL%%/2018/burton1/scripthd.sh) may be used as a driver program for this entry.
 It adds several nice-to-have features, and allows salt-to-taste customizability.
 
 This code has been compiled and tested on:
@@ -227,15 +227,12 @@ It pre-dates `varargs.h`, and assembly was the only way to gain access to the
 variable argument types.  The first edition _The C Programming Language_, 1978,
 page 71, remarks:
 
-```
-    By the way, there is no entirely satisfactory way to write a portable function
-    that accepts a variable number of arguments, because there is no portable way
-    for the called function to determine how many arguments where actually passed
-    to it in a given call.
-    ...
-    `printf`, the most common C function with a variable number of arguments,
-    ... is also non-portable and must be modified for different environments.
-```
+> By the way, there is no entirely satisfactory way to write a portable function
+that accepts a variable number of arguments, because there is no portable way
+for the called function to determine how many arguments where actually passed to
+it in a given call.  ...  `printf`, the most common C function with a variable
+number of arguments, ... is also non-portable and must be modified for different
+environments.
 
 It is fascinating to explore the roots of C through the history of the operating
 system it was birthed within.  C is often criticized as a difficult, inscrutable

2018/burton1/index.html

@@ -429,7 +429,7 @@ with <code>-Wno-</code> options.</p>
 <p>One line, one array, one loop and one statement but it prints many bytes. It won.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <p>Feed this anything on <code>stdin</code>.</p>
-<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/burton1/scripthd.sh">included script.sh</a> may be used as a driver program for this entry.
+<p>The included <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/burton1/scripthd.sh">scripthd.sh</a> may be used as a driver program for this entry.
 It adds several nice-to-have features, and allows salt-to-taste customizability.</p>
 <p>This code has been compiled and tested on:</p>
 <ul>
@@ -559,13 +559,14 @@ shortest code that compiles and runs correctly in Ancient UNIX.</p>
 It pre-dates <code>varargs.h</code>, and assembly was the only way to gain access to the
 variable argument types. The first edition <em>The C Programming Language</em>, 1978,
 page 71, remarks:</p>
-<pre><code>    By the way, there is no entirely satisfactory way to write a portable function
-    that accepts a variable number of arguments, because there is no portable way
-    for the called function to determine how many arguments where actually passed
-    to it in a given call.
-    ...
-    `printf`, the most common C function with a variable number of arguments,
-    ... is also non-portable and must be modified for different environments.</code></pre>
+<blockquote>
+<p>By the way, there is no entirely satisfactory way to write a portable function
+that accepts a variable number of arguments, because there is no portable way
+for the called function to determine how many arguments where actually passed to
+it in a given call. … <code>printf</code>, the most common C function with a variable
+number of arguments, … is also non-portable and must be modified for different
+environments.</p>
+</blockquote>
 <p>It is fascinating to explore the roots of C through the history of the operating
 system it was birthed within. C is often criticized as a difficult, inscrutable
 language, but as this contest demonstrates, this is in parody. <em>Shell-gol</em> is