improve markdown references to FAQ entries

We quasi-canonicalized markdown links to FAQ entries.

**IMPORTANT NOTE**: This is a useful step in completing issue #2417.  This commit is consistent with the top level TODO comment requirements.  Nevertheless, this changes made by this commit needs to be examined and in some cases improved.

A link to an FAQ entry is of the form:

```
FAQ on "[the link text](....faq.html#string)"
    FAQ on "[the link text](....faq.html#string)"
```

The "FAQ" is at the start of the line, or in rare cases is preceded only by whitespace.

The reference to the FAQ starts outside of the markdown link with the string **FAQ ON "**.

After the markdown link is a **"** followed by either the end of line or a single punctuation character such as a period or comma.

We reduced the size of "the link text" that refer to an FAQ to at most 3 words.  In some cases the sentence and/or text surrounding the markdown link to a FAQ may need to be further adjusted to better accommodate this new style.

**IMPORTANT NOTE**: References to a FAQ entry are on a separate line.

p.s. When linking to the `faq.html` file itself, we use markdown of the form "`the [IOCCC FAQ](..../faq.html)`" and place the word "the" outside of the "IOCCC FAQ" link text.

Given the above system (and because references to an FAQ entry is on a separate line), the following command shows links to FAQ entries, sorted by FAQ entry "link #name" so that one may evaluate the way a given FAQ entry is referenced:

```sh
find * -name '*.md' -print0 | xargs0 grep -E '^[[:space:]]*FAQ on "' | sed -e 's/^\([^:]*\):\( *FAQ on "[^#]*\)#\([^)]*\)\()".*\)$/#\3\t\1\t\2#\3\4/' | sort
```

The above command shows the value of consistency when it comes to FAQ references.

**NOTE**: There are a few differences on how a given FAQ is references.  That is probably OK as there is NOT an "total mandate" that all references to a given FAQ must have the same "link text" for example.  On the other hand if references to a given FAQ can be identical, that might be helpful.  We are certain that in some contexts the "link text" might need to change.

Should we decide to change the way FAQ are referenced, we will be able to modify identify and modify them with greater ease.'

Examine the changes made by this commit and adjust and/or improve as needed.

Performed `make www` to accomplish the above and to test under macOS.

2019/README.md

@@ -65,7 +65,7 @@ the idea was limited in scope.
 
 **IMPORTANT NOTE**: See [contact.html](../contact.html) for up to date contact details
 as well as details on how to provide fixes to any of the entries.
-See also [the IOCCC FAQ](../faq.html) for additional information on the IOCCC.
+See also the [IOCCC FAQ](../faq.html) for additional information on the IOCCC.
 
 <!--
 

2019/giles/README.md

@@ -20,8 +20,8 @@
 
 
 NOTE: `play`, which [try.sh](%%REPO_URL%%/2019/giles/try.sh) uses, comes from SoX, the Swiss Army Knife
-of sound processing programs.  If you don't have this installed, see [FAQ 3.10:
-How do I compile and use an IOCCC entry that requires sound](../../faq.html#sox).
+of sound processing programs.  If you don't have this installed, see
+FAQ on "[SDL1 and SDL2](../../faq.html#sox)".
 
 
 ## Judges' remarks:

2019/giles/index.html

@@ -414,8 +414,8 @@ Location: <a href="../../location.html#AU">AU</a> - <em>Commonwealth of Australi
 <h2 id="try">Try:</h2>
 <pre><code>    ./try.sh</code></pre>
 <p>NOTE: <code>play</code>, which <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/giles/try.sh">try.sh</a> uses, comes from SoX, the Swiss Army Knife
-of sound processing programs. If you don’t have this installed, see <a href="../../faq.html#sox">FAQ 3.10:
-How do I compile and use an IOCCC entry that requires sound</a>.</p>
+of sound processing programs. If you don’t have this installed, see
+FAQ on “<a href="../../faq.html#sox">SDL1 and SDL2</a>”.</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>Do you need to pretend enjoying a more spacious living environment than you
 actually are in, or the great outdoors with mountains and canyons, when

2019/index.html

@@ -438,7 +438,7 @@ the idea was limited in scope.</p>
 <h2 id="final-comments">Final Comments</h2>
 <p><strong>IMPORTANT NOTE</strong>: See <a href="../contact.html">contact.html</a> for up to date contact details
 as well as details on how to provide fixes to any of the entries.
-See also <a href="../faq.html">the IOCCC FAQ</a> for additional information on the IOCCC.</p>
+See also the <a href="../faq.html">IOCCC FAQ</a> for additional information on the IOCCC.</p>
 <!--
 
     Copyright © 1984-2024 by Landon Curt Noll. All Rights Reserved.

2019/mills/README.md

@@ -49,11 +49,14 @@ You decide. :-)
 **Historic note**: The award title use of the word "**tweeted**"
 should be regarded as a IOCCC anachronism.  Over the years the
 maximum size of a _tweet_ changed since this entry won the IOCCC.
-Moreover, the [IOCCC now uses Mastodon](../../faq.html#try_mastodon)
+Moreover, the **IOCCC uses Mastodon**.
 instead of whatever someone (and especially those who appear to
 have poor impulse control) chooses to call the platform where people
 used to tweet.
 
+See the
+FAQ on "[Mastodon](../../faq.html#try_mastodon)".
+
 
 ## Author's remarks:
 

2019/mills/index.html

@@ -430,10 +430,12 @@ guidelines for the IOCCC?</p>
 <p><strong>Historic note</strong>: The award title use of the word “<strong>tweeted</strong>”
 should be regarded as a IOCCC anachronism. Over the years the
 maximum size of a <em>tweet</em> changed since this entry won the IOCCC.
-Moreover, the <a href="../../faq.html#try_mastodon">IOCCC now uses Mastodon</a>
+Moreover, the <strong>IOCCC uses Mastodon</strong>.
 instead of whatever someone (and especially those who appear to
 have poor impulse control) chooses to call the platform where people
 used to tweet.</p>
+<p>See the
+FAQ on “<a href="../../faq.html#try_mastodon">Mastodon</a>”.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <h3 id="welcome-to-omlet">Welcome to OMLET! 🍳:</h3>
 <p>OMLET is the <em>Obfuscated Machine Learning Environment Toolkit</em>, a