Format fixes in html files from 2018

2018/ferguson/FILES.html

@@ -393,15 +393,15 @@
 <ul>
 <li><a href="prog.c">prog.c</a>
 <ul>
-<li>This is the source file to the <code>weasel</code> program [1].</li>
+<li>This is the source file to the <code>weasel</code> program.</li>
 </ul></li>
 <li><a href="prog.alt.c">prog.alt.c</a>
 <ul>
-<li>This is the source code file to the <code>weasel.alt</code> program [1].</li>
+<li>This is the source code file to the <code>weasel.alt</code> program.</li>
 </ul></li>
 <li><a href="test.sh">test.sh</a>
 <ul>
-<li>Script provided to test the weasel program [1].</li>
+<li>Script provided to test the weasel program.</li>
 </ul></li>
 <li><a href="test-strings.txt">test-strings.txt</a>
 <ul>
@@ -412,24 +412,17 @@ target strings.</li>
 <ul>
 <li>The Makefile that simplifies compilation as well as providing some deep
 magic and other things designed by the IOCCC judges. There’s also a <code>make   test</code> target that runs the <code>test.sh</code> script. The index.html file shows how
-to pass options to the script itself [1].</li>
+to pass options to the script itself.</li>
 </ul></li>
 <li><a href="weasel.1">weasel.1</a>
 <ul>
 <li>The man page for weasel.</li>
 </ul></li>
-<li><a href="README.md">README.md</a>
+<li><a href="rpm.html">rpm.html</a>
 <ul>
-<li>The source of the index.html file [3].</li>
+<li>This file briefly answers ‘why’ I submitted an rpm spec file.</li>
 </ul></li>
-<li><a href="rpm.md">rpm.md</a>
-<ul>
-<li>This file briefly answers ‘why’ I submitted an rpm spec file ‘weasel.spec’
-as well as the possibility of building the RPM for others (despite the fact
-I am confident that I’m the only one who would make use of it). This file
-isn’t included in the RPM itself; it remains only on the IOCCC website.</li>
-</ul></li>
-<li><a href="weasel.spec">weasel.spec</a>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/ferguson/weasel.spec">weasel.spec</a>
 <ul>
 <li>The RPM spec file for building the RPM. This is specific to the entry on
 the IOCCC website but would also be available in the source rpm file if it
@@ -439,30 +432,7 @@ was built.</li>
 <ul>
 <li>This web page.</li>
 </ul></li>
-<li><a href="FILES.md">FILES.md</a>
-<ul>
-<li>The markdown source file for <a href="FILES.html">FILES.html</a></li>
-</ul></li>
 </ul>
-<h2 id="footnote">Footnote</h2>
-<p>The follow footnotes are for if the weasel program is installed into the
-system via the RPM file (that can be built by say <code>rpmbuild -bb weasel.spec</code> on
-an RPM linux system).</p>
-<p>As I noted before it was primarily personal reasons that I submitted the spec
-file. Years later I thought of removing it but since I quite enjoyed the judges’
-remarks I have kept it in place. Please note that the paths below are dependent
-on the prefix used in installation; where I suggest <code>/usr</code> it is equally
-possible it could be under ‘/usr/local’, for example.</p>
-<p>[1] Note that <a href="prog.c">prog.c</a> and
-<a href="prog.alt.c">prog.alt.c</a> would be
-linked to <code>weasel.c</code> and <code>weasel.alt.c</code>
-(respectively) in the <code>/usr/src/weasel</code>
-subdirectory.</p>
-<p>[2] The file would most likely be compressed as
-<code>weasel.1.gz</code> under the <code>/usr/share/man/man1</code>
-subdirectory.</p>
-<p>[3] These files would be in the <code>/usr/share/doc/weasel</code>
-subdirectory.</p>
 <hr style="width:10%;text-align:left;margin-left:0">
 <p>Jump to: <a href="#">top</a></p>
 <!--