fix more broken markdown links

We fix more markdown links in markdown files that refer to files
internally to the web site.

Added tmp tools to find and print various markdown links:

* `tmp/md-links.sh` - print all markdown links
* `tmp/md-token-links.sh` - print all markdown links that start with a **%%TOKEN%%**
* `tmp/md-local-links.sh` - print all markdown links to a local file
* `tmp/md-link-paths.sh` - print local file paths referenced in markdown links

Fixed a number of markdown formatting problems with `thanks-for-help.md`.
Fixed markdown links to files in `thanks-for-help.md`.  Improved
heading levels in `thanks-for-help.md`, and made entry sections consistent.

Changed all markdown links that end in "))" to end in a better way.

Explained in `markdown.md` why we are avoiding markdown links that
end in "))".

Ran `make www` to perform the above.

TODO: Fix stuff we broke by mistake doing the above.

TODO: Fix more broken markdown links.

2018/burton1/README.md

@@ -60,7 +60,7 @@ This code has been compiled and tested on:
 * X86-Linux, gcc 4.1.2 and 4.8.4, -O0 and -O3
 * ARM-QEMU, gcc 4.8.4, -O0 and -O3
 * X86-FreeBSD 10.3, clang 3.4.1, -O0 and -O3
-* TCC 0.9.26 (x86-64) (used as a proxy for [2001/bellard](../../2001/bellard/index.html))
+* TCC 0.9.26 (x86-64), used as a proxy for [2001/bellard](../../2001/bellard/index.html)
 * UNIX V7 pcc (Johnson's C compiler) on a [simulated PDP-11/45](http://simh.trailing-edge.com/)
   (see spoiler for further detail)
 
@@ -193,7 +193,7 @@ correct.
 
 But how does this work at all, even as an extension?  `o[]` allocates one(!)
 byte in a zero-filled data area (formerly
-[BSS](https://en.wikipedia.org/wiki/.bss)).  The UNIX-derived systems this code
+[.bss](https://en.wikipedia.org/wiki/.bss) language).  The UNIX-derived systems this code
 was run upon all place the storage of `O` and `o` into a zero-filled VM page
 with nothing following: thus, there are plenty of available and unused zero
 bytes following `O`, addressed via `o`, and this code only needs 17. This is

2018/burton1/index.html

@@ -426,7 +426,7 @@ It adds several nice-to-have features, and allows salt-to-taste customizability.
 <li>X86-Linux, gcc 4.1.2 and 4.8.4, -O0 and -O3</li>
 <li>ARM-QEMU, gcc 4.8.4, -O0 and -O3</li>
 <li>X86-FreeBSD 10.3, clang 3.4.1, -O0 and -O3</li>
-<li>TCC 0.9.26 (x86-64) (used as a proxy for <a href="../../2001/bellard/index.html">2001/bellard</a>)</li>
+<li>TCC 0.9.26 (x86-64), used as a proxy for <a href="../../2001/bellard/index.html">2001/bellard</a></li>
 <li>UNIX V7 pcc (Johnson’s C compiler) on a <a href="http://simh.trailing-edge.com/">simulated PDP-11/45</a>
 (see spoiler for further detail)</li>
 </ul>
@@ -526,7 +526,7 @@ that writing more than a single char will cause a fault, which is <em>technicall
 correct.</p>
 <p>But how does this work at all, even as an extension? <code>o[]</code> allocates one(!)
 byte in a zero-filled data area (formerly
-<a href="https://en.wikipedia.org/wiki/.bss">BSS</a>). The UNIX-derived systems this code
+<a href="https://en.wikipedia.org/wiki/.bss">.bss</a> language). The UNIX-derived systems this code
 was run upon all place the storage of <code>O</code> and <code>o</code> into a zero-filled VM page
 with nothing following: thus, there are plenty of available and unused zero
 bytes following <code>O</code>, addressed via <code>o</code>, and this code only needs 17. This is

2018/burton2/README.md

@@ -166,7 +166,7 @@ determine which tool was correct when there were differences.
 ```
 
 NB: `iocccsize` gets a different answer from `tac` on its own
-([iocccsize.c](%%REPO_URL%%/2018/iocccsize.c)) source code;
+[iocccsize.c](%%REPO_URL%%/2018/iocccsize.c) source code;
 `tac` gets the correct answer.  This is due to the aforementioned bugs within `iocccsize`,
 proved by fixing
 [iocccsize.c](%%REPO_URL%%/2018/iocccsize.c) with the included patch, so `iocccsize` reports
@@ -402,7 +402,7 @@ in [prog.c](%%REPO_URL%%/2018/burton/prog.c), and the program
 [manpage.sh](%%REPO_URL%%/2018/burton/manpage.sh) was added to the corpus.
 
 [manpage.sh](%%REPO_URL%%/2018/burton/manpage.sh) is a useful program that turns ASCII versions of man
-pages (e.g. [tac.man](%%REPO_URL%%/2018/burton/tac.man)) into real man pages.  It works for C and C-like
+pages (e.g., [tac.man](%%REPO_URL%%/2018/burton/tac.man) man page) into real man pages.  It works for C and C-like
 languages, command lines, and was designed to handle man page sections 1-8.  It
 works well on most inputs, but tends to need some raw nroff for more fancy
 constructions, such as combined arguments (e.g. the `-r` and `-s` arguments to tac

2018/burton2/index.html

@@ -508,7 +508,7 @@ determine which tool was correct when there were differences.</p>
     but due to obfuscation, has had some significant, deep changes for the contest.
     Nevertheless, the more clearly written code remains a spoiler for this entry.</code></pre>
 <p>NB: <code>iocccsize</code> gets a different answer from <code>tac</code> on its own
-(<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/iocccsize.c">iocccsize.c</a>) source code;
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/iocccsize.c">iocccsize.c</a> source code;
 <code>tac</code> gets the correct answer. This is due to the aforementioned bugs within <code>iocccsize</code>,
 proved by fixing
 <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/iocccsize.c">iocccsize.c</a> with the included patch, so <code>iocccsize</code> reports
@@ -684,7 +684,7 @@ Thanks to his reports, the version of <a href="https://github.com/ioccc-src/temp
 in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/burton/prog.c">prog.c</a>, and the program
 <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/burton/manpage.sh">manpage.sh</a> was added to the corpus.</p>
 <p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/burton/manpage.sh">manpage.sh</a> is a useful program that turns ASCII versions of man
-pages (e.g. <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/burton/tac.man">tac.man</a>) into real man pages. It works for C and C-like
+pages (e.g., <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/burton/tac.man">tac.man</a> man page) into real man pages. It works for C and C-like
 languages, command lines, and was designed to handle man page sections 1-8. It
 works well on most inputs, but tends to need some raw nroff for more fancy
 constructions, such as combined arguments (e.g. the <code>-r</code> and <code>-s</code> arguments to tac

2018/ciura/README.md

@@ -5,7 +5,7 @@
 ```
 
 There is an alternate version that lacks a useful bug fix. See [Alternate
-code](#alternate-code) and the author's remarks ([remarks section](#remarks))
+code](#alternate-code) and the author's remarks, [remarks section](#remarks),
 below for more details.
 
 

2018/ciura/index.html

@@ -400,7 +400,7 @@ Location: <a href="../../location.html#PL">PL</a> - <em>Republic of Poland</em>
 <h2 id="to-build">To build:</h2>
 <pre><code>    make</code></pre>
 <p>There is an alternate version that lacks a useful bug fix. See <a href="#alternate-code">Alternate
-code</a> and the author’s remarks (<a href="#remarks">remarks section</a>)
+code</a> and the author’s remarks, <a href="#remarks">remarks section</a>,
 below for more details.</p>
 <h2 id="to-use">To use:</h2>
 <pre><code>    ./prog &lt; text</code></pre>

2018/ferguson/README.md

@@ -163,9 +163,9 @@ number of ways but the `-m` option enables it specially (I discuss this
 thoroughly in **[Hints](#hints)**).
 
 **[Hints](#hints):** Perhaps the longest part of this document because in it I
-document the [keyboards](#keyboards), [options](#options), subtleties (including
+document the [keyboards](#keyboards), [options](#options), subtleties, including
 features that might appear to be bugs but aren't - including an
-[input error](#error)), an [Easter egg spoiler](#spoiler) and quite a few
+[input error](#error), an [Easter egg spoiler](#spoiler) and quite a few
 [example invocations](#invocations). If you've read the man page you probably
 don't need this unless there is something specific you're after.
 

2018/ferguson/index.html

@@ -503,9 +503,9 @@ randomised mode that doesn’t use a genetic algorithm; it can be triggered a
 number of ways but the <code>-m</code> option enables it specially (I discuss this
 thoroughly in <strong><a href="#hints">Hints</a></strong>).</p>
 <p><strong><a href="#hints">Hints</a>:</strong> Perhaps the longest part of this document because in it I
-document the <a href="#keyboards">keyboards</a>, <a href="#options">options</a>, subtleties (including
+document the <a href="#keyboards">keyboards</a>, <a href="#options">options</a>, subtleties, including
 features that might appear to be bugs but aren’t - including an
-<a href="#error">input error</a>), an <a href="#spoiler">Easter egg spoiler</a> and quite a few
+<a href="#error">input error</a>, an <a href="#spoiler">Easter egg spoiler</a> and quite a few
 <a href="#invocations">example invocations</a>. If you’ve read the man page you probably
 don’t need this unless there is something specific you’re after.</p>
 <p><strong><a href="#obfuscation">Obfuscation</a>:</strong> Some of the techniques that might not be used.</p>

2018/poikola/README.md

@@ -88,8 +88,8 @@ best viewing experience is achieved when the terminal in use supports 24-bit
 colors, has a black background and the size is at least 125x38.
 
 Special note for Mac users: `Terminal.app` does not work as expected; you might
-need xterm from XQuartz (see [FAQ 3.7: How do I compile and use on macOS, an
-IOCCC entry that requires X11?](../../faq.html#X11macos)) or some other working
+need xterm from XQuartz, see [FAQ 3.7: How do I compile and use on macOS, an
+IOCCC entry that requires X11?](../../faq.html#X11macos), or some other working
 terminal. Thanks to [Dave Burton](../../authors.html#Dave_Burton) for spotting this
 problem.
 

2018/poikola/index.html

@@ -440,8 +440,8 @@ better with it.</p>
 best viewing experience is achieved when the terminal in use supports 24-bit
 colors, has a black background and the size is at least 125x38.</p>
 <p>Special note for Mac users: <code>Terminal.app</code> does not work as expected; you might
-need xterm from XQuartz (see <a href="../../faq.html#X11macos">FAQ 3.7: How do I compile and use on macOS, an
-IOCCC entry that requires X11?</a>) or some other working
+need xterm from XQuartz, see <a href="../../faq.html#X11macos">FAQ 3.7: How do I compile and use on macOS, an
+IOCCC entry that requires X11?</a>, or some other working
 terminal. Thanks to <a href="../../authors.html#Dave_Burton">Dave Burton</a> for spotting this
 problem.</p>
 <p>The main reason for the header <code>unistd.h</code> is <code>getdelim(3)</code> but once I included it

2018/vokes/README.md

@@ -51,7 +51,7 @@ grouped into strongly connected components. Given a set of nodes
 representing targets and edges representing dependencies between them,
 it produces a build order with any dependency cycles gathered.
 
-For example, the following input (provided as [example-1.txt](example-1.txt)):
+For example, the following input, provided as [example-1.txt](example-1.txt):
 
 ```
     0 4 8

2018/vokes/index.html

@@ -421,7 +421,7 @@ and prints the graph’s nodes in reverse-topologically sorted order,
 grouped into strongly connected components. Given a set of nodes
 representing targets and edges representing dependencies between them,
 it produces a build order with any dependency cycles gathered.</p>
-<p>For example, the following input (provided as <a href="example-1.txt">example-1.txt</a>):</p>
+<p>For example, the following input, provided as <a href="example-1.txt">example-1.txt</a>:</p>
 <pre><code>    0 4 8
     1 0
     2 1 3

2018/yang/README.md

@@ -32,7 +32,7 @@ this program left and recompiling will reveal other tools including a right rota
 and a shift program.
 
 Strange things happen [when the world is upside
-down](https://en.wikipedia.org/wiki/Wacky_Wednesday_(book))! It is entirely possible
+down](https://en.wikipedia.org/wiki/Wacky_Wednesday_(book))! It is entirely possible
 that this remark is completely misleading.
 
 What exactly does the shift program do?
@@ -123,7 +123,7 @@ the 10th final string from [prog.c](%%REPO_URL%%/2018/yang/prog.c).  The intent
 wooden puzzle boxes that can be opened by pushing and shifting various
 well-concealed seams.  Thus, finding the correct sequence of rotates
 and shifts is left as an exercise to the reader (but if you are really
-lazy, just read the [Makefile](%%REPO_URL%%/2018/yang/Makefile)).
+lazy, just read the [Makefile](%%REPO_URL%%/2018/yang/Makefile).
 
 Source code for all the tools needed to solve this puzzle are embedded
 in [prog.c](%%REPO_URL%%/2018/yang/prog.c), all you need is a C compiler.

2018/yang/index.html

@@ -469,7 +469,7 @@ the 10th final string from <a href="https://github.com/ioccc-src/temp-test-ioccc
 wooden puzzle boxes that can be opened by pushing and shifting various
 well-concealed seams. Thus, finding the correct sequence of rotates
 and shifts is left as an exercise to the reader (but if you are really
-lazy, just read the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/yang/Makefile">Makefile</a>).</p>
+lazy, just read the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/yang/Makefile">Makefile</a>.</p>
 <p>Source code for all the tools needed to solve this puzzle are embedded
 in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/yang/prog.c">prog.c</a>, all you need is a C compiler.</p>
 <h3 id="features">Features</h3>