Fix markdown and html files and Makefile

Much like the ferguson1/ fixes in the previous commit I have fixed the
lists in the markdown files and the html files have been updated too.

 I *believe* I got the chocolate-cake.html generated properly after
making a change of the chocolate-cake.text (because it's encrypted with
the Enigma and because the judges have their headers/footers I had to
take the generated file from ferguson1 - corrected - and then encrypt it
with the proper key).

Makefile now refers to *.text files rather than *.markdown.

There might be some other changes I forgot.

2020/ferguson2/recode.html

@@ -34,23 +34,30 @@ good chocolate and could use a delicious <a href="chocolate-cake.html">Double-la
 <p>Alternatively if you just want the recipe you could look at my Snake entry
 &lsquo;Don&rsquo;t tread on me award&rsquo; since it&rsquo;s also there and not enciphered.</p>
 
-<p><a name="toc"></a>
--   <a href="#recode">What is recode and why is it recommended?</a>
--   <a href="#options">Options</a>
-    *   <a href="#samefile">Protecting against the same I/O file</a>
-    *   <a href="#fileoptions">File options parser limitation</a>
-    *   <a href="#validation">-R option validation?</a>
--   <a href="#pipingtorecode">Piping commands to recode</a>
--   <a href="#pipingtoenigma">Piping recode to the Enigma simulator</a>
--   <a href="#manuallytest">Manually test the recode program with the Enigma program</a>
--   <a href="#onlyconfig">Only write config file</a>
--   <a href="#reuseconfig">Reusing a configuration</a>
--   <a href="#passtoenigma">Write config file, read data file and pass to Enigma simulator</a>
--   <a href="#directlytoenigma">Piping directly to the Enigma code once (with randomised settings, saved)</a>
--   <a href="#conclusion">Usage conclusion</a>
--   <a href="#additions">Example additions</a>
--   <a href="#exampleuses">Example uses</a>
--   <a href="#cake">Delicious Enigma: Double-layered Chocolate Fudge Cake</a></p>
+<p><a name="toc"></a></p>
+
+<ul>
+<li><p><a href="#recode">What is recode and why is it recommended?</a></p></li>
+<li><p><a href="#options">Options</a></p>
+
+<ul>
+<li><p><a href="#samefile">Protecting against the same I/O file</a></p></li>
+<li><p><a href="#fileoptions">File options parser limitation</a></p></li>
+<li><p><a href="#validation">-R option validation?</a></p></li>
+</ul>
+</li>
+<li><p><a href="#pipingtorecode">Piping commands to recode</a></p></li>
+<li><p><a href="#pipingtoenigma">Piping recode to the Enigma simulator</a></p></li>
+<li><p><a href="#manuallytest">Manually test the recode program with the Enigma program</a></p></li>
+<li><p><a href="#onlyconfig">Only write config file</a></p></li>
+<li><p><a href="#reuseconfig">Reusing a configuration</a></p></li>
+<li><p><a href="#passtoenigma">Write config file, read data file and pass to Enigma simulator</a></p></li>
+<li><p><a href="#directlytoenigma">Piping directly to the Enigma code once (with randomised settings, saved)</a></p></li>
+<li><p><a href="#conclusion">Usage conclusion</a></p></li>
+<li><p><a href="#additions">Example additions</a></p></li>
+<li><p><a href="#exampleuses">Example uses</a></p></li>
+<li><p><a href="#cake">Delicious Enigma: Double-layered Chocolate Fudge Cake</a></p></li>
+</ul>
 
 <h1><a name="recode" href="#toc">What is recode and why is it recommended?</a></h1>