Format, typo, consistency check YYYY/README.md

There are many fixes made but a few questions remain so when I reach
those years I will address those then. Unfortunately, due to
infrastructure work right now, this is all I can say even though there
are a number of things I'd like to say.

2018/index.html

@@ -393,21 +393,14 @@ compile the entry and how to run the winning program. Look at the winning
 source and try to figure how it does what it does! You may then wish to look at
 the Author’s remarks for even more details. This year we included most of the
 information included by the submitter.</p>
-<p>The primary site can be found at <a href="https://www.ioccc.org">www.ioccc.org</a>.</p>
-<p>Use <code>make</code> to compile entries. It is possible that on non-Unix / non-Linux
-systems the Makefile needs to be changed. See the Makefile for details.</p>
-<p>Look at the source and try to figure out what the programs do, and run
-them with various inputs.</p>
-<p>Read over the Makefile and index.html files for compile/build issues. Your
-system may require certain changes (add or remove a library, add or remove a
-<code>#define</code>).</p>
 <p>Some C compilers are not quite as good as they should be. If yours is
 lacking, you may need to compile using clang or gcc instead of your local
 compiler.</p>
+<p>The primary website can be found at <a href="https://www.ioccc.org">www.ioccc.org</a>.</p>
 <h2 id="remarks-on-some-of-the-winning-entries">Remarks on some of the winning entries</h2>
 <p>We believe you will again be impressed with this year’s winning entries.</p>
 <p>The <a href="mills/index.html">Best of Show - 2018/mills</a> is an amazing tribute to entries
-from 1984 and 2015.</p>
+from <a href="../1984/index.html">1984</a> and <a href="../2015/index.html">2015</a>.</p>
 <p>Take a close look at the <a href="hou/index.html">Most likely to top the charts - 2018/hou</a>.
 Observe that while it contains no variables and no operators, it
 remains functional in what it does.</p>
@@ -416,7 +409,7 @@ short and sweet implementation of a classic utility and a nod to a winning entry
 from 1986. Sometimes it takes 20 some years to do things the true IOCCC way.</p>
 <p>The color of the remarks text this year was inspired by one of the stars
 of the <a href="poikola/index.html">Most stellar - 2018/poikola</a>.</p>
-<p>The <a href="endoh2/index.html">Best use of python - 2018/endoh2</a> is a not what you might think it is.
+<p>The <a href="endoh2/index.html">Best use of python - 2018/endoh2</a> is not what you might think it is.
 It is something completely different.</p>
 <p>The <a href="ciura/index.html">Most likely to be awarded - 2018/ciura</a> has an amazing vocabulary!</p>
 <p>There are also nods to entries of the years <a href="../2000/bellard/index.html">2000/bellard</a>,
@@ -427,18 +420,25 @@ It is something completely different.</p>
 would have been much higher had some people paid attention to rules 2
 and 22 (one third of 666).</p>
 <p>Rule 22, now known as “Catch 22” states:</p>
-<pre><code>    22) Your source code, data files, remarks and program output must NOT
-        identify the authors of your code.  The judges STRONGLY prefer to
-        not know who is submitting entries to the IOCCC.
-
-        The &quot;Peter Honeyman is exempt&quot; guideline also applies to this rule.
-        Identifying yourself, in an obvious way in your code, data, remarks
-        or program output, unless you are Peter Honeyman or pretending
-        to be Peter Honeyman, will be grounds for disqualification of your entry.</code></pre>
+<blockquote>
+<ol start="22" type="1">
+<li>Your source code, data files, remarks and program output must NOT identify
+the authors of your code. The judges STRONGLY prefer to not know who is
+submitting entries to the IOCCC.</li>
+</ol>
+<p>The “Peter Honeyman is exempt” guideline also applies to this rule.
+Identifying yourself, in an obvious way in your code, data, remarks or program
+output, unless you are Peter Honeyman or pretending to be Peter Honeyman, will
+be grounds for disqualification of your entry.</p>
+</blockquote>
 <p>A number of other entries were based on <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/iocccsize.c">iocccsize.c</a>, making
 derivative works rather than original works.</p>
 <p>Still other entries were too large, violating the first line of rule 2:</p>
-<pre><code>    2) The size of your program source must be &lt;= 4096 bytes in length.</code></pre>
+<blockquote>
+<ol start="2" type="1">
+<li>The size of your program source must be &lt;= 4096 bytes in length.</li>
+</ol>
+</blockquote>
 <p>While these entries might have passed under the 2053 limit for iocccsize,
 they were larger than &lt;= 4096 bytes, sometimes by an order or magnitude.</p>
 <p>We hope the authors of some of those entries will fix and re-submit