Fix html lint (W3C Nu) errors

In the case of two which had an abstract (.entry.json file) that
includes one (in one case) '<' or two (in another case) '<'s a markdown
code block had to be used as otherwise the abstract would have to have a
&lt; which looks even worse. This is not ideal but if we want it to pass
lint this is what has to be done. Use of json \uxxxx won't work as that
encodes it to < literally.

In the case of 2018/burton[12] the author had a section called Coda.
This conflicted with the problem that all generated html files have such
a section. To fix this problem I renamed it 'Final remarks'. Not ideal
but at least it now passes as valid.

There were a number of different kinds of problems and in one case the
symbols < and > could be fixed by changing it to a code block (which it
should have been anyway) - that was 2020/ferguson1 I think.

2020/ferguson1/terminals.html

@@ -568,7 +568,7 @@ even just the <code>reset</code> command.</p>
 <p>The Linux man page says:</p>
 <blockquote>
 <p>You might have to run the <code>reset</code> tool like:</p>
-<p><LF>reset<LF></p>
+<p><code>&lt;LF&gt;reset&lt;LF&gt;</code></p>
 <p>(the line-feed character is normally control-J) to get the terminal to work,
 as carriage-return may no longer work in the abnormal state.</p>
 </blockquote>

2020/ferguson1/terminals.md

@@ -193,7 +193,7 @@ The Linux man page says:
 
 > You might have to run the `reset` tool like:
 >
->   <LF>reset<LF>
+>   `<LF>reset<LF>`
 >
 >   (the line-feed character is normally control-J) to get the terminal to work,
 as carriage-return may no longer work in the abnormal state.