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.
2024-07-17 03:11:19 -07:00
1 parent d852734d98
commit 0bc6c3e413
@@ -19,7 +19,7 @@ post](https://groups.google.com/g/net.lang.c/c/lx-TAuEyeRI/m/HdOOnNx6LC0J).

 **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.


 <!--
@@ -407,7 +407,7 @@ post</a>.</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.
@@ -17,7 +17,7 @@ the best 4.

 **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.


 <!--
@@ -406,7 +406,7 @@ the best 4.</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.
@@ -28,7 +28,7 @@ Feather) started this year.  A notice was posted to net.announce.

 **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.


 <!--
@@ -415,7 +415,7 @@ Feather) started this year. A notice was posted to net.announce.</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.
@@ -32,7 +32,7 @@ the foils.

 **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.


 <!--
@@ -420,7 +420,7 @@ the foils.</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.
@@ -28,7 +28,7 @@ also available on a wide number of USENET archive sites.

 **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.


 <!--
@@ -414,7 +414,7 @@ also available on a wide number of USENET archive sites.</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.
@@ -29,7 +29,7 @@ Journal](https://www.vintage-computer.com/publications.php?microsystemsjournal).

 **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.


 <!--
@@ -415,7 +415,7 @@ Journal</a>.</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.
@@ -29,7 +29,7 @@ available on a wide number of USENET archive sites such as uunet.

 **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.


 <!--
@@ -414,7 +414,7 @@ available on a wide number of USENET archive sites such as uunet.</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.
@@ -88,7 +88,7 @@ people used to contact the IOCCC in this given year:
 purposes only, and should not be used today.  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.


 ## Credits:
@@ -465,7 +465,7 @@ judges@toad.com</p>
 purposes only, and should not be used today. 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>
 <h2 id="credits">Credits:</h2>
 <p>We would like to thank Barbara Frezza for her role as official chef
 of the contest. Landon Noll appreciated the opportunity to serve
@@ -81,7 +81,7 @@ us a line.  We enjoy seeing who, where and how the contest is used.
 purposes only, and should not be used today.  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.


 ## Credits:
@@ -457,7 +457,7 @@ us a line. We enjoy seeing who, where and how the contest is used.</p>
 purposes only, and should not be used today. 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>
 <h2 id="credits">Credits:</h2>
 <p>We would like to thank Barbara Frezza for her role as official chef of
 the contest. Landon Noll and Larry Bassel appreciated the opportunity
@@ -48,7 +48,7 @@ us a line.  We enjoy seeing who, where and how the contest is used.
 purposes only, and should not be used today.  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.


 ### Credits:
@@ -10,8 +10,8 @@ section below to run the original (the bug also exists here).
 ```

 NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to
-compile. If you don't have the X11 installed see the [FAQ on how to compile and
-run an entry that requires X11](../../faq.html#X11).
+compile. If you don't have the X11 installed see the
+FAQ on "[X11](../../faq.html#X11)".

 To configure how many microseconds to sleep before updates try:

@@ -414,8 +414,8 @@ bugs.html</a>). See the <a href="#original-code">original code</a>
 section below to run the original (the bug also exists here).</p>
 <pre><code>    make alt</code></pre>
 <p>NOTE: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
-compile. If you don’t have the X11 installed see the <a href="../../faq.html#X11">FAQ on how to compile and
-run an entry that requires X11</a>.</p>
+compile. If you don’t have the X11 installed see the
+FAQ on “<a href="../../faq.html#X11">X11</a>”.</p>
 <p>To configure how many microseconds to sleep before updates try:</p>
 <pre><code>    make clobber SLEEP=200 alt</code></pre>
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
@@ -430,7 +430,7 @@ us a line. We enjoy seeing who, where and how the contest is used.</p>
 purposes only, and should not be used today. 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>
 <h3 id="credits">Credits:</h3>
 <p>We would like to thank Barbara Frezza for her role as official chef
 of the contest. Landon Curt Noll and Larry Bassel appreciated the opportunity
@@ -1,8 +1,9 @@
 ## To build:

 NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to
-compile. See [the FAQ on how to run entries that require X11](../../faq.html#X11) if
-you need help.
+compile. See the
+FAQ on "[X11](../../faq.html#X11)"
+if you need help.


 ``` <!---sh-->
@@ -409,8 +409,9 @@ Location: <a href="../../location.html#NO">NO</a> - <em>Kingdom of Norway</em> (
 <!-- BEFORE: 1st line of markdown file: 1993/jonth/README.md -->
 <h2 id="to-build">To build:</h2>
 <p>NOTE: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
-compile. See <a href="../../faq.html#X11">the FAQ on how to run entries that require X11</a> if
-you need help.</p>
+compile. See the
+FAQ on “<a href="../../faq.html#X11">X11</a>”
+if you need help.</p>
 <pre><code>    make all</code></pre>
 <h2 id="to-use">To use:</h2>
 <pre><code>    ./jonth     # must be run on an X11 server</code></pre>
@@ -117,7 +117,7 @@ as well as details on how to provide fixes to any of the entries.
 purposes only, and should not be used today.  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.


 ## Credits
@@ -482,7 +482,7 @@ as well as details on how to provide fixes to any of the entries.</p>
 purposes only, and should not be used today. 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>
 <h2 id="credits">Credits</h2>
 <p>We would like to thank Barbara Frezza for her role as official chef
 of the contest. Landon Curt Noll and Larry Bassel appreciated the opportunity
@@ -65,7 +65,7 @@ us a line.  We enjoy seeing who, where and how the contest is used.
 purposes only, and should not be used today.  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.


 ## Credits
@@ -444,7 +444,7 @@ us a line. We enjoy seeing who, where and how the contest is used.</p>
 purposes only, and should not be used today. 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>
 <h2 id="credits">Credits</h2>
 <p>We would like to thank Barbara Frezza for her role as official chef of
 the contest. Landon Noll, Larry Bassel and Sriram Srinivasan
@@ -85,7 +85,7 @@ us a line.  We enjoy seeing who, where and how the contest is used.
 purposes only, and should not be used today.  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.


 <!--
@@ -450,7 +450,7 @@ us a line. We enjoy seeing who, where and how the contest is used.</p>
 purposes only, and should not be used today. 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.
@@ -109,7 +109,7 @@ Send such email to:
 purposes only, and should not be used today.  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.

 If you use, distribute or publish these entries in some way, please drop
 us a line.  We enjoy seeing who, where and how the contest is used.
@@ -475,7 +475,7 @@ Send such email to:</p>
 purposes only, and should not be used today. 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>
 <p>If you use, distribute or publish these entries in some way, please drop
 us a line. We enjoy seeing who, where and how the contest is used.</p>
 <p>You must include the words ‘ioccc question’ in the subject of your email
@@ -84,7 +84,7 @@ Send such email to:
 purposes only, and should not be used today.  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.


 <!--
@@ -451,7 +451,7 @@ Send such email to:</p>
 purposes only, and should not be used today. 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.
@@ -5,9 +5,11 @@
 ```

 NOTE: if you don't have curses or SDL1 installed both modes will fail to compile. In
-that case see the [FAQ 3.8 - How do I compile an IOCCC entry that requires SDL1
-or SDL2?](../../faq.html#SDL) and [FAQ 3.9  - How do I compile an IOCCC entry that
-requires ncurses?](../../faq.html#curses) for more information.
+that case see the
+FAQ on "[SDL1 and SDL2](../../faq.html#SDL)"
+and
+FAQ on "[ncurses](../../faq.html#curses)"
+for more information.

 We recommend that you use the alternate code so you can see what this entry
 looked like back in 2000 (with a configurable speed). See the
@@ -415,9 +415,11 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
 <h2 id="to-build">To build:</h2>
 <pre><code>    make alt</code></pre>
 <p>NOTE: if you don’t have curses or SDL1 installed both modes will fail to compile. In
-that case see the <a href="../../faq.html#SDL">FAQ 3.8 - How do I compile an IOCCC entry that requires SDL1
-or SDL2?</a> and <a href="../../faq.html#curses">FAQ 3.9 - How do I compile an IOCCC entry that
-requires ncurses?</a> for more information.</p>
+that case see the
+FAQ on “<a href="../../faq.html#SDL">SDL1 and SDL2</a>”
+and
+FAQ on “<a href="../../faq.html#curses">ncurses</a>”
+for more information.</p>
 <p>We recommend that you use the alternate code so you can see what this entry
 looked like back in 2000 (with a configurable speed). See the
 <a href="#original-code">original code</a> section for the original entry.</p>
@@ -66,7 +66,7 @@ Send such email to:
 purposes only, and should not be used today.  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.


 <!--
@@ -439,7 +439,7 @@ Send such email to:</p>
 purposes only, and should not be used today. 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.
@@ -59,7 +59,7 @@ character printed on the screen.
 ### Why did I write this ?


-Let's just quote the [FAQ](../../faq.html):
+Let's just quote the [IOCCC FAQ](../../faq.html):

 Q: Are there types of entries that are submitted so frequently that the
   judges get tired of them?
@@ -434,7 +434,7 @@ sequential version is slower as it works in <code>O(n*log n)</code>. But you hav
 nice picture instead… the cost is a constant number of operation for each
 character printed on the screen.</p>
 <h3 id="why-did-i-write-this">Why did I write this ?</h3>
-<p>Let’s just quote the <a href="../../faq.html">FAQ</a>:</p>
+<p>Let’s just quote the <a href="../../faq.html">IOCCC FAQ</a>:</p>
 <p>Q: Are there types of entries that are submitted so frequently that the
 judges get tired of them?</p>
 <p>A: Yes, there are types of entries that show up over and over again.
@@ -51,7 +51,7 @@ them for the next IOCCC.

 **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.


 <!--
@@ -430,7 +430,7 @@ them for the next IOCCC.</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.
@@ -84,7 +84,7 @@ them for the next IOCCC.

 **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.


 <!--
@@ -9,8 +9,8 @@

 You will need an [SVG](https://www.w3.org/TR/SVG11/expanded-toc.html) viewer or
 a converter like [ImageMagick](https://imagemagick.org/index.php)'s `convert`.
-See [FAQ 3.17 - How do I compile and install ImageMagick for entries that
-require it?](../../faq.html#imagemagick).
+See
+FAQ on "[ImageMagick](../../faq.html#imagemagick)".

 Look here to find some [SVG Viewer
 Implementations](https://www.w3.org/Graphics/SVG/WG/wiki/Implementations).
@@ -412,8 +412,8 @@ Location: <a href="../../location.html#FR">FR</a> - <em>French Republic</em> (<e
 <h2 id="to-use">To use:</h2>
 <p>You will need an <a href="https://www.w3.org/TR/SVG11/expanded-toc.html">SVG</a> viewer or
 a converter like <a href="https://imagemagick.org/index.php">ImageMagick</a>’s <code>convert</code>.
-See <a href="../../faq.html#imagemagick">FAQ 3.17 - How do I compile and install ImageMagick for entries that
-require it?</a>.</p>
+See
+FAQ on “<a href="../../faq.html#imagemagick">ImageMagick</a>”.</p>
 <p>Look here to find some <a href="https://www.w3.org/Graphics/SVG/WG/wiki/Implementations">SVG Viewer
 Implementations</a>.</p>
 <pre><code>    ./boutines &lt; input &gt; output.svg</code></pre>
@@ -447,7 +447,7 @@ them for the next IOCCC.</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.
@@ -1,7 +1,8 @@
 ## To build:

-This entry requires SDL. See [3.8  - How do I compile an IOCCC entry that
-requires SDL1 or SDL2?](../../faq.html#SDL) for information on how to install it if you
+This entry requires SDL. See
+FAQ on "[SDL1 and SDL2](../../faq.html#SDL)"
+for information on how to install it if you
 haven't already.

 If you have SDL installed:
@@ -408,8 +408,9 @@ Location: <a href="../../location.html#FI">FI</a> - <em>Republic of Finland </em

 <!-- BEFORE: 1st line of markdown file: 2005/jetro/README.md -->
 <h2 id="to-build">To build:</h2>
-<p>This entry requires SDL. See <a href="../../faq.html#SDL">3.8 - How do I compile an IOCCC entry that
-requires SDL1 or SDL2?</a> for information on how to install it if you
+<p>This entry requires SDL. See
+FAQ on “<a href="../../faq.html#SDL">SDL1 and SDL2</a>”
+for information on how to install it if you
 haven’t already.</p>
 <p>If you have SDL installed:</p>
 <pre><code>    make</code></pre>
@@ -49,7 +49,7 @@ of the submitter).

 **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.


 <!--
@@ -427,7 +427,7 @@ of the submitter).</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.
@@ -46,7 +46,7 @@ disqualify entries that reveal the identity of the submitter).

 **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.


 <!--
@@ -425,7 +425,7 @@ disqualify entries that reveal the identity of the submitter).</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.
@@ -105,7 +105,7 @@ in some particularly impressive way.

 **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.


 <!--
@@ -467,7 +467,7 @@ in some particularly impressive way.</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.
@@ -65,8 +65,8 @@ NOTE: if you use vim to view the code, make sure to do:
 ```

 in command mode, before looking at the code, to see the correct layout. For more
-help see [[6.14 - How do I set certain tabstops for viewing source code in
-vi&#x28;m&#x29;?](../../faq.html#tabstops)
+help see the
+FAQ on "[tabstops](../../faq.html#tabstops)".


 ## Author's remarks:
@@ -438,8 +438,8 @@ just to understand <em>18 key <strong>characters</strong></em> of this code.</p>
 <p>NOTE: if you use vim to view the code, make sure to do:</p>
 <pre><code>    :set tabstop=4</code></pre>
 <p>in command mode, before looking at the code, to see the correct layout. For more
-help see [<a href="../../faq.html#tabstops">6.14 - How do I set certain tabstops for viewing source code in
-vi(m)?</a></p>
+help see the
+FAQ on “<a href="../../faq.html#tabstops">tabstops</a>”.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <h3 id="nesting-errors-detector">Nesting Errors Detector</h3>
 <h4 id="what-does-it-do">What does it do</h4>
@@ -83,7 +83,7 @@ excel over similar previous winning entry in some particularly impressive way.

 **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.


 <!--
@@ -22,8 +22,9 @@ For more detailed information see [2013/endoh3 in bugs.html](../../bugs.html#201
    ./endoh3
 ```

-This program plays sound. See [FAQ 3.10 - How do I compile and use an IOCCC
-entry that requires sound?](../../faq.html#sox) if you do not know how to set your
+This program plays sound. See
+FAQ on "[compile with sound](../../faq.html#sox)"
+if you do not know how to set your
 system up for this or if you want to verify that everything is oky.


@@ -415,8 +415,9 @@ Location: <a href="../../location.html#JP">JP</a> - <em>Japan</em></li>
 <p>For more detailed information see <a href="../../bugs.html#2013_endoh3">2013/endoh3 in bugs.html</a>.</p>
 <h2 id="to-use">To use:</h2>
 <pre><code>    ./endoh3</code></pre>
-<p>This program plays sound. See <a href="../../faq.html#sox">FAQ 3.10 - How do I compile and use an IOCCC
-entry that requires sound?</a> if you do not know how to set your
+<p>This program plays sound. See
+FAQ on “<a href="../../faq.html#sox">compile with sound</a>”
+if you do not know how to set your
 system up for this or if you want to verify that everything is oky.</p>
 <h2 id="try">Try:</h2>
 <pre><code>    ./try.sh
@@ -450,7 +450,7 @@ excel over similar previous winning entry in some particularly impressive way.</
 <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.
@@ -1,7 +1,8 @@
 ## To build:

-This entry requires SDL to be installed. See [FAQ 3.8](../../faq.html#SDL) if you
-don't know how to do this for your system.
+This entry requires SDL to be installed. See
+FAQ on "[SDL1 and SDL2](../../faq.html#SDL)"
+if you don't know how to do this for your system.

 ``` <!---sh-->
    make
@@ -408,8 +408,9 @@ Location: <a href="../../location.html#IT">IT</a> - <em>Italian Republic</em> (<

 <!-- BEFORE: 1st line of markdown file: 2014/maffiodo1/README.md -->
 <h2 id="to-build">To build:</h2>
-<p>This entry requires SDL to be installed. See <a href="../../faq.html#SDL">FAQ 3.8</a> if you
-don’t know how to do this for your system.</p>
+<p>This entry requires SDL to be installed. See
+FAQ on “<a href="../../faq.html#SDL">SDL1 and SDL2</a>”
+if you don’t know how to do this for your system.</p>
 <pre><code>    make</code></pre>
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
 <p>The current status of this entry is:</p>
@@ -5,8 +5,8 @@
 ```

 NOTE: this program requires the tool `tcpserver` to use. If you do not have this
-program see [FAQ 3.14 - How do I compile and install tcpserver for entries that
-require it](../../faq.html#tcpserver).
+program see
+FAQ on "[tcpserver](../../faq.html#tcpserver)".


 ## To use:
@@ -415,8 +415,8 @@ Location: <a href="../../location.html#JP">JP</a> - <em>Japan</em></li>
 <h2 id="to-build">To build:</h2>
 <pre><code>    make</code></pre>
 <p>NOTE: this program requires the tool <code>tcpserver</code> to use. If you do not have this
-program see <a href="../../faq.html#tcpserver">FAQ 3.14 - How do I compile and install tcpserver for entries that
-require it</a>.</p>
+program see
+FAQ on “<a href="../../faq.html#tcpserver">tcpserver</a>”.</p>
 <h2 id="to-use">To use:</h2>
 <pre><code>    tcpserver -v 127.0.0.1 10333 ./prog ioccc.txt</code></pre>
 <p>Then connect to http://localhost:10333 with your browser.</p>
@@ -90,7 +90,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.

 <!--

@@ -5,8 +5,8 @@
 ```

 To use this entry requires, in some invocations, a sound processing program.
-This can be ALSA or SoX but we recommend the latter. See [FAQ 3.10 - How do I
-compile and use an IOCCC entry that requires sound?](../../faq.html#sox).
+This can be ALSA or SoX but we recommend the latter. See
+FAQ on "[SDL1 and SDL2](../../faq.html#sox)".


 ### Bugs and (Mis)features:
@@ -410,8 +410,8 @@ Location: <a href="../../location.html#SE">SE</a> - <em>Kingdom of Sweden</em> (
 <h2 id="to-build">To build:</h2>
 <pre><code>    make</code></pre>
 <p>To use this entry requires, in some invocations, a sound processing program.
-This can be ALSA or SoX but we recommend the latter. See <a href="../../faq.html#sox">FAQ 3.10 - How do I
-compile and use an IOCCC entry that requires sound?</a>.</p>
+This can be ALSA or SoX but we recommend the latter. See
+FAQ on “<a href="../../faq.html#sox">SDL1 and SDL2</a>”.</p>
 <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
 <p>The current status of this entry is:</p>
 <pre><code>    STATUS: INABIAF - please DO NOT fix</code></pre>
@@ -27,10 +27,10 @@ graphics viewer of choice.  After that try:

 NOTE: the script uses the tools `pngtopam(1)` (or `pngtopnm(1)` for older
 versions) and `pnmscale` come from the netpbm project and `cjpeg(1)` comes from
-`libjpeg-turbo`. If you don't have these tools already see [FAQ 3.15 - How do I
-compile and install netpbm for entries that require it?](../../faq.html#netpbm) and
-[FAQ 3.16 - How do I compile and install libjpeg-turbo for entries that require
-it?](../../faq.html#libjpeg).
+`libjpeg-turbo`. If you don't have these tools already see
+FAQ on "[netpbm](../../faq.html#netpbm)"
+and
+FAQ on "[libjpeg-turbo](../../faq.html#libjpeg)".

 NOTE: [Lenna.png](Lenna.png) is from
 <https://upload.wikimedia.org/wikipedia/en/7/7d/Lenna_%28test_image%29.png>.
@@ -420,10 +420,10 @@ graphics viewer of choice. After that try:</p>
 <pre><code>    ./try.sh</code></pre>
 <p>NOTE: the script uses the tools <code>pngtopam(1)</code> (or <code>pngtopnm(1)</code> for older
 versions) and <code>pnmscale</code> come from the netpbm project and <code>cjpeg(1)</code> comes from
-<code>libjpeg-turbo</code>. If you don’t have these tools already see <a href="../../faq.html#netpbm">FAQ 3.15 - How do I
-compile and install netpbm for entries that require it?</a> and
-<a href="../../faq.html#libjpeg">FAQ 3.16 - How do I compile and install libjpeg-turbo for entries that require
-it?</a>.</p>
+<code>libjpeg-turbo</code>. If you don’t have these tools already see
+FAQ on “<a href="../../faq.html#netpbm">netpbm</a>”
+and
+FAQ on “<a href="../../faq.html#libjpeg">libjpeg-turbo</a>”.</p>
 <p>NOTE: <a href="Lenna.png">Lenna.png</a> is from
 <a href="https://upload.wikimedia.org/wikipedia/en/7/7d/Lenna_%28test_image%29.png" class="uri">https://upload.wikimedia.org/wikipedia/en/7/7d/Lenna_%28test_image%29.png</a>.</p>
 <h2 id="alternate-code">Alternate code:</h2>
@@ -206,7 +206,9 @@ bytes following `O`, addressed via `o`, and this code only needs 17. This is
 _undefined_ behavior, but as shown, it is widely available.

 The [1979 Seventh Edition UNIX][1] (v7) system pre-dates the IOCCC by several years,
-and the source code to `sh`(1) was a [significant inspiration for this contest](../../faq.html#ioccc_start).
+and the source code to `sh`(1) was a **significant inspiration for this contest**.
+See the
+FAQ on "[IOCCC beginnings](../../faq.html#ioccc_start)".
 There are two C compilers present: `cc` written by Dennis Ritchie, and `pcc` written by Steven Johnson.
 The nested conditional expressions in 116 and smaller are too complex for `cc` ("Illegal conditional")
 but `pcc` handles them correctly, and neither compiler accepts `char o[]` or
@@ -543,7 +543,9 @@ 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
 <em>undefined</em> behavior, but as shown, it is widely available.</p>
 <p>The <a href="http://minnie.tuhs.org/cgi-bin/utree.pl">1979 Seventh Edition UNIX</a> (v7) system pre-dates the IOCCC by several years,
-and the source code to <code>sh</code>(1) was a <a href="../../faq.html#ioccc_start">significant inspiration for this contest</a>.
+and the source code to <code>sh</code>(1) was a <strong>significant inspiration for this contest</strong>.
+See the
+FAQ on “<a href="../../faq.html#ioccc_start">IOCCC beginnings</a>”.
 There are two C compilers present: <code>cc</code> written by Dennis Ritchie, and <code>pcc</code> written by Steven Johnson.
 The nested conditional expressions in 116 and smaller are too complex for <code>cc</code> (“Illegal conditional”)
 but <code>pcc</code> handles them correctly, and neither compiler accepts <code>char o[]</code> or
@@ -1,7 +1,8 @@
 ## To build:

-This entry requires SDL2 to be installed. See [FAQ 3.8: How do I compile an
-IOCCC entry that requires SDL1 or SDL2?](../../faq.html#SDL) if you don't have it
+This entry requires SDL2 to be installed. See
+FAQ on "[SDL1 and SDL2](../../faq.html#SDL)"
+if you don't have it
 installed and don't know how to do so.

 ``` <!---sh-->
@@ -408,8 +408,9 @@ Location: <a href="../../location.html#AU">AU</a> - <em>Commonwealth of Australi

 <!-- BEFORE: 1st line of markdown file: 2018/giles/README.md -->
 <h2 id="to-build">To build:</h2>
-<p>This entry requires SDL2 to be installed. See <a href="../../faq.html#SDL">FAQ 3.8: How do I compile an
-IOCCC entry that requires SDL1 or SDL2?</a> if you don’t have it
+<p>This entry requires SDL2 to be installed. See
+FAQ on “<a href="../../faq.html#SDL">SDL1 and SDL2</a>”
+if you don’t have it
 installed and don’t know how to do so.</p>
 <pre><code>    make</code></pre>
 <h2 id="to-use">To use:</h2>
@@ -460,7 +460,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.
@@ -96,8 +96,9 @@ 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 on "[X11 on macOS](../../faq.html#X11macos)",
+or some other working
 terminal. Thanks to [Dave Burton](../../authors.html#Dave_Burton) for spotting this
 problem.

@@ -454,8 +454,9 @@ 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
+FAQ on “<a href="../../faq.html#X11macos">X11 on macOS</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
@@ -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.

 <!--

@@ -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:
@@ -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
@@ -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.
@@ -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:

@@ -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
@@ -63,7 +63,7 @@ One more thing that feels dated is digraphs and trigraphs.

 **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.

 <!--

@@ -42,8 +42,9 @@ will be converted to the DTMF sound!
 ```

 If the script [try.sh](%%REPO_URL%%/2020/giles/try.sh) did not play a WAV file, it means you do not have
-SoX installed; see [FAQ 3.10: How do I compile and use an IOCCC entry that
-requires sound?](../../faq.html#sox). In this case install it and try it again or
+SoX installed; see
+FAQ on "[SDL1 and SDL2](../../faq.html#sox)".
+In this case install it and try it again or
 play the files `jenny.wav` and `ioccc28.wav` in a program that can play WAV
 files.

@@ -429,8 +429,9 @@ will be converted to the DTMF sound!</p>
    # See
    ./prog 867-5309 &gt; jenny.wav</code></pre>
 <p>If the script <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/giles/try.sh">try.sh</a> did not play a WAV file, it means you do not have
-SoX installed; see <a href="../../faq.html#sox">FAQ 3.10: How do I compile and use an IOCCC entry that
-requires sound?</a>. In this case install it and try it again or
+SoX installed; see
+FAQ on “<a href="../../faq.html#sox">SDL1 and SDL2</a>”.
+In this case install it and try it again or
 play the files <code>jenny.wav</code> and <code>ioccc28.wav</code> in a program that can play WAV
 files.</p>
 <p>NOTE: the phone number of <code>jenny.wav</code> comes from
@@ -435,7 +435,7 @@ perhaps re-submit them for the next IOCCC.</p>
 <p>One more thing that feels dated is digraphs and trigraphs.</p>
 <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.
@@ -391,9 +391,14 @@
 <h1 id="wait---before-you-send-that-email">WAIT!!! - Before you send that email</h1>
 <p>If you are trying to:</p>
 <ul>
-<li><strong>Fix a winning IOCCC entry</strong> - See <a href="faq.html#fix_an_entry">FAQ 5.2</a></li>
-<li><strong>Update winning author information</strong> - See <a href="faq.html#fix_author">FAQ 5.5</a></li>
-<li><strong>Correct a website problem</strong> - See <a href="faq.html#fix_web_site">FAQ 5.4</a> or <a href="faq.html#fix_link">FAQ 5.6</a></li>
+<li><strong>Fix a winning IOCCC entry</strong> - See
+FAQ on “<a href="faq.html#fix_an_entry">fix entry</a>”</li>
+<li><strong>Update winning author information</strong> - See
+FAQ on “<a href="faq.html#fix_author">fixing author information</a>”</li>
+<li><strong>Correct a website problem</strong> - See
+FAQ on “<a href="faq.html#fix_web_site">fixing the website</a>”
+or
+FAQ on “<a href="faq.html#fix_link">fix URL</a>”</li>
 </ul>
 <p>Instead of sending us email, <strong>Please</strong> consider using the <a href="https://github.com/ioccc-src/winner/pulls">GitHub
 pull request</a> process
@@ -401,9 +406,12 @@ against the <a href="https://github.com/ioccc-src/winner/branches">master branch
 of the <a href="https://github.com/ioccc-src/winner">ioccc-src/winner repo</a>.</p>
 <p>If you are trying to:</p>
 <ul>
-<li><strong>Report a bug in an IOCCC winning entry</strong> - See <a href="faq.html#report_bug">FAQ 5.1</a></li>
-<li><strong>Report an IOCCC website problem</strong> - See <a href="faq.html#report_web_problem">FAQ 5.3</a></li>
-<li><strong>Report a broken or wrong web link</strong> - See <a href="faq.html#fix_link">FAQ 5.6</a></li>
+<li><strong>Report a bug in an IOCCC winning entry</strong> - See
+FAQ on “<a href="faq.html#report_bug">report entry bug</a>”</li>
+<li><strong>Report an IOCCC website problem</strong> - See
+FAQ on “<a href="faq.html#report_web_problem">report website problem</a>”</li>
+<li><strong>Report a broken or wrong web link</strong> - See
+FAQ on “<a href="faq.html#fix_link">report broken link</a>”</li>
 </ul>
 <p>In general, unless you have a fix, if you want to report something, you should instead first look at the <a href="https://github.com/ioccc-src/winner/issues">IOCCC
 issues</a> to see if the
@@ -413,9 +421,12 @@ reported, then feel free to <a href="https://github.com/ioccc-src/winner/issues/
 issue</a>.</p>
 <p>If you are trying to:</p>
 <ul>
-<li><strong>Comment or make a suggestion on IOCCC rules</strong> - See <a href="faq.html#feedback">FAQ 0.5</a></li>
-<li><strong>Comment or make a suggestion on IOCCC guidelines</strong> - See <a href="faq.html#feedback">FAQ 0.5</a></li>
-<li><strong>Comment or make a suggestion on IOCCC tools</strong> - See <a href="faq.html#feedback">FAQ 0.5</a></li>
+<li><strong>Comment or make a suggestion on IOCCC rules</strong> - See
+FAQ on “<a href="faq.html#feedback">rules feedback</a>”</li>
+<li><strong>Comment or make a suggestion on IOCCC guidelines</strong> - See
+FAQ on “<a href="faq.html#feedback">guidelines feedback</a>”</li>
+<li><strong>Comment or make a suggestion on IOCCC tools</strong> - See
+FAQ on “<a href="faq.html#feedback">tools feedback</a>”</li>
 </ul>
 <p>Those FAQ entries will help guide you on how to make public comments
 and suggestion in the relevant places.</p>
@@ -426,8 +437,9 @@ and suggestion in the relevant places.</p>
 <h2 id="please-follow-the-ioccc-on-mastodon">Please follow the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a></h2>
 <p>We use Mastodon to make minor announcements, in addition announcing
 major events such as the opening of a new IOCCC, or who won.</p>
-<p>See “<a href="faq.html#try_mastodon">FAQ 6.12: What is Mastodon and why does IOCCC use it?</a>” for more
-information on Mastodon.</p>
+<p>See
+FAQ on “<a href="faq.html#try_mastodon">Mastodon</a>”
+for more information on Mastodon.</p>
 <h1 id="if-you-really-need-to-send-email-the-ioccc-judges">If you really need to send email the IOCCC judges</h1>
 <p>Did you look at the above section?</p>
 <p>If you must contact the IOCCC judges by email, then please send email to:
@@ -2,9 +2,14 @@

 If you are trying to:

-* **Fix a winning IOCCC entry** - See [FAQ 5.2](faq.html#fix_an_entry)
-* **Update winning author information** - See [FAQ 5.5](faq.html#fix_author)
-* **Correct a website problem** - See [FAQ 5.4](faq.html#fix_web_site) or [FAQ 5.6](faq.html#fix_link)
+* **Fix a winning IOCCC entry** - See
+FAQ on "[fix entry](faq.html#fix_an_entry)"
+* **Update winning author information** - See
+FAQ on "[fixing author information](faq.html#fix_author)"
+* **Correct a website problem** - See
+FAQ on "[fixing the website](faq.html#fix_web_site)"
+or
+FAQ on "[fix URL](faq.html#fix_link)"

 Instead of sending us email, **Please** consider using the [GitHub
 pull request](https://github.com/ioccc-src/winner/pulls) process
@@ -13,9 +18,12 @@ of the [ioccc-src/winner repo](https://github.com/ioccc-src/winner).

 If you are trying to:

-* **Report a bug in an IOCCC winning entry** - See [FAQ 5.1](faq.html#report_bug)
-* **Report an IOCCC website problem** - See [FAQ 5.3](faq.html#report_web_problem)
-* **Report a broken or wrong web link** - See [FAQ 5.6](faq.html#fix_link)
+* **Report a bug in an IOCCC winning entry** - See
+FAQ on "[report entry bug](faq.html#report_bug)"
+* **Report an IOCCC website problem** - See
+FAQ on "[report website problem](faq.html#report_web_problem)"
+* **Report a broken or wrong web link** - See
+FAQ on "[report broken link](faq.html#fix_link)"

 In general, unless you have a fix, if you want to report something, you should instead first look at the [IOCCC
 issues](https://github.com/ioccc-src/winner/issues) to see if the
@@ -26,9 +34,12 @@ issue](https://github.com/ioccc-src/winner/issues/new).

 If you are trying to:

-* **Comment or make a suggestion on IOCCC rules** - See [FAQ 0.5](faq.html#feedback)
-* **Comment or make a suggestion on IOCCC guidelines** - See [FAQ 0.5](faq.html#feedback)
-* **Comment or make a suggestion on IOCCC tools** - See [FAQ 0.5](faq.html#feedback)
+* **Comment or make a suggestion on IOCCC rules** - See
+FAQ on "[rules feedback](faq.html#feedback)"
+* **Comment or make a suggestion on IOCCC guidelines** - See
+FAQ on "[guidelines feedback](faq.html#feedback)"
+* **Comment or make a suggestion on IOCCC tools** - See
+FAQ on "[tools feedback](faq.html#feedback)"

 Those FAQ entries will help guide you on how to make public comments
 and suggestion in the relevant places.
@@ -45,8 +56,9 @@ See the above FAQ entries for more details.
 We use Mastodon to make minor announcements, in addition announcing
 major events such as the opening of a new IOCCC, or who won.

-See "[FAQ 6.12: What is Mastodon and why does IOCCC use it?](faq.html#try_mastodon)" for more
-information on Mastodon.
+See
+FAQ on "[Mastodon](faq.html#try_mastodon)"
+for more information on Mastodon.


 # If you really need to send email the IOCCC judges
@@ -545,7 +545,9 @@ to our submission portal.</p>
 <li><p>Makefile</p>
 <p>Makefile to build (make all) and cleanup (make clean &amp; make clobber)</p></li>
 <li><p>remarks.md</p>
-<p>Remarks about your entry in markdown format: see <a href="#remarks_md">FAQ 2.1</a> for more info.</p></li>
+<p>Remarks about your entry in markdown format: see
+FAQ on “<a href="#remarks_md">remarks.md</a>”
+for more info.</p></li>
 <li><p>[file …]</p>
 <p>Optional extra data files to include with your entry</p></li>
 </ul>
@@ -583,7 +585,8 @@ winners based on the same theme.</p>
 frequently submitted theme, be sure that it is obfuscated in several
 new and novel ways.</p>
 <p><strong>IMPORTANT HINT</strong>: Be sure to <strong>clearly explain</strong> near the beginning
-of your <code>remarks.md</code> file, see <a href="#remarks_md">FAQ 2.1</a>,
+of your <code>remarks.md</code> file, see
+FAQ on “<a href="#remarks_md">remarks.md</a>”,
 <strong>why you are submitting a entry based on a frequently
 submitted theme</strong> and <strong>how compares with previous IOCCC winners</strong>
 of the same theme.</p>
@@ -662,7 +665,8 @@ previous IOCCC entries make it more challenging to be successful.</p>
 state something along the lines of:</p>
 <pre><code>    We tend to dislike programs that: are similar to previous winning entries.</code></pre>
 <p><strong>FAIR WARNING</strong>: Be sure to <strong>clearly explain</strong> near the beginning
-of your <code>remarks.md</code> file, see <a href="#remarks_md">FAQ 2.1</a>,
+of your <code>remarks.md</code> file, see
+FAQ on “<a href="#remarks_md">remarks.md</a>”,
 <strong>why you are submitting a entry based on a frequently
 submitted theme</strong> and <strong>how compares with previous IOCCC winners</strong>
 of the same theme.</p>
@@ -788,14 +792,15 @@ with your submission. If the <a href="judges.html">IOCCC judges</a> truly need m
 information, they will ask (either in public or suggest a private conversation).</p>
 <p>Again, <strong>please</strong> don’t hesitate to ask: Your question may be something that
 others are wondering about as well!</p>
-<p>See also <a href="#feedback">FAQ about making suggestions</a>.</p>
+<p>See also
+FAQ on “<a href="#feedback">rules, guidelines, tools feedback</a>”.</p>
 <div id="faq0_7">
 <div id="markdown">
 <h3 id="faq-0.7---what-are-the-ioccc-best-practices-for-using-markdown">FAQ 0.7: - What are the IOCCC best practices for using markdown?</h3>
 </div>
 </div>
 <p>The IOCCC makes extensive use of <a href="https://daringfireball.net/projects/markdown/">markdown</a>.
-For example, we <a href="faq.html#submit">submitting to the IOCCC</a>, we have people
+For example, we <a href="#submit">submitting to the IOCCC</a>, we have people
 to submit remarks about entry in markdown format. Every
 <a href="years.html">winning IOCCC entry</a> uses a <code>README.md</code> markdown file
 as the basis for forming the <code>index.html</code> web page for that entry.
@@ -868,8 +873,10 @@ for a list of valid codes.</li>
 </ul></li>
 <li><p><code>mastodon</code> (null or double quoted string)</p>
 <ul>
-<li>The <strong><a href="#try_mastodon">Mastodon</a> handle</strong> of this author in the form of <code>@user@domain</code>, or
-<code>null</code> if not provided.</li>
+<li>The Mastodon handle of this author in the form of <code>@user@domain</code>, or
+<code>null</code> if not provided. See
+FAQ on “<a href="#try_mastodon">Mastodon</a>”
+for more information.</li>
 </ul></li>
 <li><p><code>github</code> (null or double quoted string)</p>
 <ul>
@@ -904,9 +911,12 @@ by this author.</li>
 </ul>
 <p><strong>NOTE:</strong> if you have won before, we <strong>ENCOURAGE</strong> you to use the same handle of
 your previous winning entries, to help in organising the
-<a href="authors.html">authors.html</a> page and the author JSON file (see: <a href="#author_handle_faq">What is an
-author handle?</a> and <a href="#author_json">What is an <code>author_handle.json</code>
-file and how are they used?</a>).</p></li>
+<a href="authors.html">authors.html</a> page and the author JSON file.
+See
+FAQ on “<a href="#author_handle_faq">author handle</a>”
+and
+FAQ on “<a href="#author_json">author_handle.json</a>”
+for more information.</p></li>
 <li><p><code>author_number</code> (number)</p>
 <ul>
 <li>This author number in the <code>authors</code> array.</li>
@@ -1036,7 +1046,10 @@ array your submission <strong>will be</strong> invalid.</p></li>
 <strong>NOT</strong> email the <a href="judges.html">Judges</a> your submission!</p></li>
 <li><p><code>formed_timestamp</code> (number)</p>
 <ul>
-<li>Seconds since epoch when <code>.auth.json</code>/<a href="#info_json">.info json</a> was formed (see <code>gettimeofday(2)</code>).</li>
+<li>Seconds since epoch when <code>.auth.json was formed (see</code>gettimeofday(2)`).
+See also
+FAQ on “<a href="#info_json">.info.json</a>”
+for more inforation.</li>
 </ul>
 <p><strong>NOTE:</strong> this <strong>MUST</strong> be greater than or equal to <code>MIN_TIMESTAMP</code> (see
 <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/soup/limit_ioccc.h">soup/limit_ioccc.h</a>
@@ -1100,15 +1113,24 @@ validate the <code>.auth.json</code> file.</p>
 compressed tarball of your submission. The <code>.info.json</code> file contains
 information about the submission, in JSON format. The
 JSON <code>manifest</code> array contains information about the files of the submission,
-<strong>including</strong> the <strong>mandatory</strong> <a href="#auth_json">.auth.json</a>, <a href="#info_json">.info.json</a>,
-C source and <a href="#remarks">remarks</a> files. In particular:</p>
+<strong>including</strong> the <strong>mandatory</strong> <code>.auth.json</code> file,
+the <strong>mandatory</strong> <code>remarks.md</code> file,
+and the <strong>mandatory</strong> C source file.
+See the
+FAQ on “<a href="#auth_json">.auth.json</a>”
+and
+FAQ on “<a href="#remarks_md">remarks.md</a>”
+for more inforation.</p>
 <ul>
 <li><p><code>info_JSON</code> (double quoted string)</p>
 <ul>
 <li>This <code>MUST</code> be <code>".info.json"</code>, defined as <code>INFO_JSON_FILENAME</code> in
 <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h">soup/entry_util.h</a>
 in the <a href="https://github.com/ioccc-src/mkiocccentry/">mkiocccentry repo</a>, and
-it is the <a href="#info_json">.info.json</a> file that <code>mkiocccentry</code> forms.</li>
+it is the <code>.info.json</code> file that <code>mkiocccentry</code> forms.
+See the
+FAQ on “<a href="#info_json">.info.json</a>”
+for more information.</li>
 </ul>
 <p><strong>NOTE:</strong> if this is <strong>NOT</strong> the case you stand a great chance of having your
 submission rejected for violating <a href="next/rules.html#rule17">Rule 17</a>!</p></li>
@@ -1117,7 +1139,10 @@ submission rejected for violating <a href="next/rules.html#rule17">Rule 17</a>!<
 <li>This <code>MUST</code> be <code>".auth.json"</code>, defined as <code>AUTH_JSON_FILENAME</code> in
 <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h">soup/entry_util.h</a>
 in the <a href="https://github.com/ioccc-src/mkiocccentry/">mkiocccentry repo</a>, and
-it is the <a href="#auth_json">.auth.json</a> file that <code>mkiocccentry</code> forms.</li>
+it is the <code>.auth.json</code> file that <code>mkiocccentry</code> forms.
+See the
+FAQ on “<a href="#auth_json">.auth.json</a>”
+for more inforation.</li>
 </ul>
 <p><strong>NOTE:</strong> if this is <strong>NOT</strong> the case you stand a great chance of having your
 submission rejected for violating <a href="next/rules.html#rule17">Rule 17</a>!</p></li>
@@ -1137,7 +1162,10 @@ copied to <code>prog.c</code>.</p></li>
 <li>This <code>MUST</code> be <code>"Makefile"</code>, defined as <code>MAKEFILE_FILENAME</code> in
 <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h">soup/entry_util.h</a>
 in the <a href="https://github.com/ioccc-src/mkiocccentry/">mkiocccentry repo</a>, and
-is your <a href="#makefile">Makefile</a>.</li>
+is your <code>Makefile</code> file.
+See the
+FAQ on “<a href="#makefile">Makefile</a>”
+for more information.</li>
 </ul>
 <p><strong>NOTE:</strong> if this is <strong>NOT</strong> the case you stand a great chance of having your
 submission rejected for violating <a href="next/rules.html#rule17">Rule 17</a>!</p>
@@ -1148,7 +1176,10 @@ copied to <code>Makefile</code>.</p></li>
 <li>This <code>MUST</code> be <code>"remarks.md"</code>, defined as <code>REMARKS_FILENAME</code> in
 <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h">soup/entry_util.h</a>
 in the <a href="https://github.com/ioccc-src/mkiocccentry/">mkiocccentry repo</a>, and
-is your <a href="#remarks">remarks.md</a>.</li>
+is your <code>remarks.md]</code> file.
+See the
+FAQ on “<a href="#remarks_md">remarks.md</a>”
+for more information.</li>
 </ul>
 <p><strong>NOTE:</strong> if this is <strong>NOT</strong> the case you stand a great chance of having your
 submission rejected for violating <a href="next/rules.html#rule17">Rule 17</a>!</p>
@@ -1384,36 +1415,49 @@ overflows in general.</p></li>
 <li><p><code>Makefile_override</code> (boolean)</p>
 <ul>
 <li><code>true</code> if the user overrides any warnings about an incomplete/incorrect
-<a href="#makefile">Makefile</a>, else <code>false</code>.</li>
+<code>Makefile file, else</code>false`.</li>
 </ul>
-<p><strong>NOTE:</strong> if the <a href="#makefile">Makefile</a> has no problems and this is <code>true</code> then
+<p><strong>NOTE:</strong> if the <code>Makefile</code> file has no problems and this is <code>true</code> then
 you stand a good chance of having your submission rejected for violating
-<a href="next/rules.html#rule17">Rule 17</a>!</p></li>
+<a href="next/rules.html#rule17">Rule 17</a>!</p>
+<p>See the
+FAQ on “<a href="#makefile">Makefile</a>”
+for more information.</p></li>
 <li><p><code>first_rule_is_all</code> (boolean)</p>
 <ul>
-<li><code>true</code> if the first rule in the <a href="#makefile">Makefile</a> is
-<code>all</code>, else <code>false</code>.</li>
-</ul></li>
+<li><code>true</code> if the first rule in the <code>Makefile</code> file is <code>all</code>, else <code>false</code>.</li>
+</ul>
+<p>See the
+FAQ on “<a href="#makefile">Makefile</a>”
+for more information.</p></li>
 <li><p><code>found_all_rule</code> (boolean)</p>
 <ul>
-<li><code>true</code> if the <a href="#makefile">Makefile</a> has an <code>all</code> rule, else
-<code>false</code>.</li>
-</ul></li>
+<li><code>true</code> if the <code>Makefile</code> file has an <code>all</code> rule, else <code>false</code>.</li>
+</ul>
+<p>See the
+FAQ on “<a href="#makefile">Makefile</a>”
+for more information.</p></li>
 <li><p><code>found_clean_rule</code> (boolean)</p>
 <ul>
-<li><code>true</code> if the <a href="#makefile">Makefile</a> has a <code>clean</code> rule, else
-<code>false</code>.</li>
-</ul></li>
+<li><code>true</code> if the <code>Makefile</code> file has a <code>clean</code> rule, else <code>false</code>.</li>
+</ul>
+<p>See the
+FAQ on “<a href="#makefile">Makefile</a>”
+for more information.</p></li>
 <li><p><code>found_clobber_rule</code> (boolean)</p>
 <ul>
-<li><code>true</code> if the <a href="#makefile">Makefile</a> has a <code>clobber</code> rule,
-else <code>false</code>.</li>
-</ul></li>
+<li><code>true</code> if the <code>Makefile</code> file has a <code>clobber</code> rule, else <code>false</code>.</li>
+</ul>
+<p>See the
+FAQ on “<a href="#makefile">Makefile</a>”
+for more information.</p></li>
 <li><p><code>found_try_rule</code> (boolean)</p>
 <ul>
-<li><code>true</code> if the <a href="#makefile">Makefile</a> has a <code>try</code> rule, else
-<code>false</code>.</li>
-</ul></li>
+<li><code>true</code> if the <code>Makefile</code> file has a <code>try</code> rule, else <code>false</code>.</li>
+</ul>
+<p>See the
+FAQ on “<a href="#makefile">Makefile</a>”
+for more information.</p></li>
 <li><p><code>test_mode</code> (boolean)</p>
 <ul>
 <li><code>true</code> if the <code>test</code> ID was used to form the tarball, else <code>false</code>.</li>
@@ -1422,7 +1466,7 @@ else <code>false</code>.</li>
 contest! Please do <strong>NOT</strong> email the <a href="judges.html">Judges</a> your submission!</p></li>
 <li><p><code>formed_timestamp</code> (number)</p>
 <ul>
-<li>Seconds since epoch when <a href="#auth_json">.auth.json</a>/<code>.info json</code> was formed (see <code>gettimeofday(2)</code>).</li>
+<li>Seconds since epoch when JSON (<code>.auth.json</code> or <code>.info.json</code>) file was formed (see <code>gettimeofday(2)</code>).</li>
 </ul>
 <p><strong>NOTE:</strong> this <strong>MUST</strong> be greater than or equal to <code>MIN_TIMESTAMP</code> (see
 <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/soup/limit_ioccc.h">soup/limit_ioccc.h</a>
@@ -1950,10 +1994,11 @@ hints, especially in cases were something else needs to be installed.</p>
 <p>Please see the <a href="bugs.html">bugs.html</a> file for details about known problems with IOCCC entries. In some cases you may be dealing with a problematic entry. In a few fun cases, the IOCCC does not compile by design!</p>
 <p>If you have a fix that makes a minimal impact to the entry, then
 please consider submitting that change in the form of a pull request.
-Please see <a href="#fix_an_entry">FAQ 5.2 How may I submit a fix to an IOCCC
-entry</a>. See also the <a href="#pull_request">FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request</a> for more information about pull requests.</p>
+Please see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”.
+See also the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
+for more information about pull requests.</p>
 <p>In some cases alternative code has been added that does compile on some or most
 systems. Check the write up for the entry for “alt” code and possible ways to
 compile and run that code. In some cases we replaced the original code (but not
@@ -1986,10 +2031,10 @@ in question to see if the problem is known, and if a fix is wanted,
 consider trying to port the code to a 64-bit system and submitting
 a pull request with that change. Pull requests that fix such code
 while trying to minimize the impact of any changes and preserving
-the spirit of the original code are very welcome! Please see <a href="#fix_an_entry">FAQ
-5.2 How may I submit a fix to an IOCCC entry</a> for
-details. See also the <a href="#pull_request">FAQ 6.10 How does someone make a change to
-a file and submit that change as a GitHub pull request</a>
+the spirit of the original code are very welcome! Please see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
+for details. See also the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
 for more information about pull requests.</p>
 <div id="faq3_3">
 <h3 id="faq-3.3-why-do-some-ioccc-entries-fail-to-compile-under-macos">FAQ 3.3: Why do some IOCCC entries fail to compile under macOS?</h3>
@@ -2003,7 +2048,8 @@ others will be looked at, when found.</p>
 with an entry. Should you manage to port the entry, and assuming your changes
 also attempt to preserve the original intent of the IOCCC entry, we would
 encourage you to submit a pull request with your ported code.
-Please see <a href="#fix_an_entry">FAQ 5.2 How may I submit a fix to an IOCCC entry</a>
+Please see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
 for details.</p>
 <div id="faq3_4">
 <h3 id="faq-3.4-why-does-clang-or-gcc-fail-to-compile-an-ioccc-entry">FAQ 3.4: Why does clang or gcc fail to compile an IOCCC entry?</h3>
@@ -2022,10 +2068,11 @@ other things that have to be done plus remembering to do it.</p>
 <p>See if the problem is mentioned in <a href="bugs.html">bugs.html</a>. If you have a change
 that fixes the problem (even if it just a change to the <code>Makefile</code>) that doesn’t
 negatively impact the entry too much, consider submitting that change in the
-form of a pull request. Please see <a href="#fix_an_entry">FAQ 5.2 How may I submit a fix to an IOCCC
-entry</a>. See also the <a href="#pull_request">FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request</a> for more information about pull requests.</p>
+form of a pull request. Please see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”.
+See also the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
+for more information about pull requests.</p>
 <div id="faq3_5">
 <h3 id="faq-3.5-what-is-this-cb-tool-that-is-mentioned-in-the-ioccc">FAQ 3.5: What is this cb tool that is mentioned in the IOCCC?</h3>
 </div>
@@ -2095,25 +2142,34 @@ entries that use X11 in an unusual way might fail under <strong>Wayland</strong>
 information.</p>
 <p>If your system uses <strong>Wayland</strong> and not X11, you might give the IOCCC entries
 that use X11 a try. They might work but again we do not know.</p>
-<p><strong>IMPORTANT NOTE</strong>: The <a href="judges.html">IOCCC judges</a> <a href="#no_support">do not support IOCCC entries</a>.
+<p><strong>IMPORTANT NOTE</strong>: The <a href="judges.html">IOCCC judges</a> <strong>do not support IOCCC entries</strong>.
+See the
+FAQ on “<a href="#no_support">no entry support</a>”.
 So if an IOCCC entry that uses X11 fails under <strong>Wayland</strong>, and you wish to
 provide a fix to the IOCCC entry so that it will run under <strong>Wayland</strong>,
-then consider <a href="#fix_an_entry">submitting a fix</a> so that it will run under <strong>Wayland</strong>.</p>
+then consider submitting a fix so that it will run under <strong>Wayland</strong>.
+See the
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
+for more information.</p>
 <p>Basically: if you discover an entry does not work in Wayland you are welcome to
 provide <strong>alternate code</strong> that works for Wayland. We will happily credit you in
 the <a href="thanks-for-help.html">thanks-for-help.html</a> file.</p>
 <h4 id="red-hat-based-linux">Red Hat based Linux</h4>
-<p>First, see the above note on <a href="#X11_general">installing and starting Xorg</a>.</p>
+<p>First, see
+FAQ on “<a href="#X11_general">general X11</a>”.</p>
 <p>Install Xorg and related packages:</p>
 <pre><code>    sudo dnf install --skip-broken --best --exclude xorgxrdp --exclude xorgxrdp-glamor &#39;*xorg*&#39; &#39;libx*&#39; &#39;libX*&#39; &#39;fontconfig*&#39;</code></pre>
 <p>See also:</p>
 <ul>
 <li><a href="https://www.wikihow.com/Configure-X11-in-Linux">How to Configure X11 in Linux</a></li>
 </ul>
-<p><strong>IMPORTANT NOTE</strong>: The <a href="#Xorg_deprecated">X.org server has been deprecated</a>.
-See the above note for details.</p>
+<p><strong>IMPORTANT NOTE</strong>: The X.org server has been deprecated.
+See the
+FAQ on “<a href="#Xorg_deprecated">X.org deprecated</a>”
+for more information.</p>
 <h4 id="macos">macOS</h4>
-<p>First, see the above note on <a href="#X11_general">installing and starting Xorg</a>.
+<p>First, see the
+FAQ on “<a href="#X11_general">general X11</a>”.
 However, for macOS, instead of installing the Xorg server, you need to install and launch
 the <a href="https://www.xquartz.org">most recent XQuartz</a> application
 and then run the IOCCC entry from the <a href="https://en.wikipedia.org/wiki/Xterm">Xterm window
@@ -2138,17 +2194,23 @@ shell</a> started:</p>
 <p>Note that you can compile the code in your regular terminal prior to opening
 XQuartz, should you wish to. You can even run it from that terminal and it
 should open XQuartz.</p>
-<p><strong>IMPORTANT NOTE</strong>: The <a href="#Xorg_deprecated">X.org server has been deprecated</a>.
-See the above note for details.</p>
+<p><strong>IMPORTANT NOTE</strong>: The X.org server has been deprecated.
+See the
+FAQ on “<a href="#Xorg_deprecated">X.org deprecated</a>”
+for more information.</p>
 <h4 id="debian-based-linux">Debian based Linux</h4>
-<p>First, see the above note on <a href="#X11_general">installing and starting Xorg</a>.</p>
+<p>First, see the
+FAQ on “<a href="#X11_general">general X11</a>”.</p>
 <p>According to the <a href="https://wiki.debian.org/Xorg">Debian Xorg wiki</a>, installing
 X11 requires:</p>
 <pre><code>    sudo apt install xorg</code></pre>
-<p><strong>IMPORTANT NOTE</strong>: The <a href="#Xorg_deprecated">X.org server has been deprecated</a>.
-See the above note for details.</p>
+<p><strong>IMPORTANT NOTE</strong>: The X.org server has been deprecated.
+See the
+FAQ on “<a href="#Xorg_deprecated">X.org deprecated</a>”
+for more information.</p>
 <h4 id="other-linux-distributions">Other Linux distributions</h4>
-<p>First, see the above note on <a href="#X11_general">installing and starting Xorg</a>.</p>
+<p>First, see the
+FAQ on “<a href="#X11_general">general X11</a>”.</p>
 <p>For general documentation on installing X11, this <a href="https://help.ubuntu.com/community/ServerGUI">ServerGUI for
 Ubuntu</a>, and in particular, these
 may be helpful:</p>
@@ -2165,13 +2227,18 @@ may be helpful:</p>
 <pre><code>    sudo dnf install --skip-broken --best --exclude xorgxrdp --exclude xorgxrdp-glamor &#39;*xorg*&#39; &#39;libx*&#39; &#39;libX*&#39; &#39;fontconfig*&#39;</code></pre>
 <p>For systems that have the <code>yum(1)</code> command:</p>
 <pre><code>    sudo yum install --skip-broken --best --exclude xorgxrdp --exclude xorgxrdp-glamor &#39;*xorg*&#39; &#39;libx*&#39; &#39;libX*&#39; &#39;fontconfig*&#39;</code></pre>
-<p><strong>IMPORTANT NOTE</strong>: The <a href="#Xorg_deprecated">X.org server has been deprecated</a>.
-See the above note for details.</p>
+<p><strong>IMPORTANT NOTE</strong>: The X.org server has been deprecated.
+See the
+FAQ on “<a href="#Xorg_deprecated">X.org deprecated</a>”
+for more information.</p>
 <h4 id="package-website">Package website</h4>
-<p>First, see the above note on <a href="#X11_general">installing and starting Xorg</a>.</p>
+<p>First, see the
+FAQ on “<a href="#X11_general">general X11</a>”.</p>
 <p>See the <a href="https://x.org/wiki/">X.org</a> foundation website.</p>
-<p><strong>IMPORTANT NOTE</strong>: The <a href="#Xorg_deprecated">X.org server has been deprecated</a>.
-See the above note for details.</p>
+<p><strong>IMPORTANT NOTE</strong>: The X.org server has been deprecated.
+See the
+FAQ on “<a href="#Xorg_deprecated">X.org deprecated</a>”
+for more information.</p>
 <div id="faq3_8">
 <div id="SDL">
 <h3 id="faq-3.8-how-do-i-compile-an-ioccc-entry-that-requires-sdl1-or-sdl2">FAQ 3.8: How do I compile an IOCCC entry that requires SDL1 or SDL2?</h3>
@@ -2190,7 +2257,9 @@ in the above command.</p>
 <pre><code>    export SDL2_INCLUDE_ROOT=/usr</code></pre>
 <p>but this might not be necessary in more modern days especially as we use
 <code>sdl-config</code> and <code>sdl2-config</code> which should find the proper paths.</p>
+<div id="X11macos">
 <h4 id="macos-1">macOS</h4>
+</div>
 <p>If you’re using macOS there are at least three ways to obtain it. You can
 use Homebrew or MacPorts. If you do not wish to use either of those
 package managers, you can always try to install via the package website.
@@ -2229,8 +2298,9 @@ for downloading, installing and using SDL.</p>
 be that you need additional SDL libraries. See the entry’s index.html for
 details. If something is not noted you’re welcome to report it as an issue or
 fix it and make a pull request.</p>
-<p>See the <a href="#pull_request">FAQ 6.10 How does someone make a change to a file and submit that change
-as a GitHub pull request</a> for more information about pull requests.</p>
+<p>See the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
+for more information about pull requests.</p>
 <div id="faq3_9">
 <div id="curses">
 <h3 id="faq-3.9-how-do-i-compile-an-ioccc-entry-that-requires-ncurses">FAQ 3.9: How do I compile an IOCCC entry that requires (n)curses?</h3>
@@ -2420,7 +2490,9 @@ that you may wish to try.</p>
 entry. If so, you are invited to try and fix the IOCCC entry and
 submit that fix by way of a <a href="https://github.com/ioccc-src/winner/pulls">GitHub pull
 request</a>.
-Please see <a href="#fix_an_entry">FAQ 5.2</a> for how to submit a fix to an IOCCC entry.</p>
+Please see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
+for how to submit a fix to an IOCCC entry.</p>
 <div id="faq3_14">
 <div id="tcpserver">
 <h3 id="faq-3.14---how-do-i-compile-and-install-tcpserver-for-entries-that-require-it">FAQ 3.14 - How do I compile and install tcpserver for entries that require it?</h3>
@@ -2557,9 +2629,9 @@ for downloading, installing and using ImageMagick.</p>
 </div>
 </div>
 <p>This depends on your operating system for which we describe a couple below.</p>
-<p>In general OpenGL needs X11 to be installed and the X Window Server to be running.
-See <a href="#X11_general">FAQ 3.7: How do I run an IOCCC entry that requires X11?</a> for
-general information about X11.</p>
+<p>In general OpenGL needs X11 to be installed and the X Window Server to be running. See
+FAQ on “<a href="#X11">X11</a>”
+for general information about X11.</p>
 <p>Once X11 is install and the X Window Server is running, one needs to compile
 and link with the two libraries, <em>GL</em> and <em>GLU</em>:</p>
 <pre><code>    cc ... -lGL -lGLU -L _location-where-X11-libs-are-installed_ -lX11</code></pre>
@@ -2652,8 +2724,8 @@ then do:</p>
 <span id="cb59-3"><a href="#cb59-3" aria-hidden="true" tabindex="-1"></a>        <span class="ex">./mullender.alt</span></span></code></pre></div>
 <p>to compile all versions and then run the alternate version (if you have
 a PDP-11 or VAX-11 you would be able to run the original version). For more help
-on compiling entries, see also <a href="#make_rules">3.0 - What Makefile rules are available to
-build or clean up IOCCC entries?</a>.</p>
+on compiling entries, see also the
+FAQ on “<a href="#make_rules">IOCCC Makefile rules</a>”.</p>
 <p>If you want to view the <code>index.html</code> file you can point your browser to the
 <code>index.html</code> file of the winning entry (e.g. <code>1984/mullender/index.html</code>) with the
 caveats noted above.</p>
@@ -2692,8 +2764,8 @@ extract it and then switch to the directory and compile everything of each
 entry:</p>
 <div class="sourceCode" id="cb60"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb60-1"><a href="#cb60-1" aria-hidden="true" tabindex="-1"></a>        <span class="bu">cd</span> 1984</span>
 <span id="cb60-2"><a href="#cb60-2" aria-hidden="true" tabindex="-1"></a>        <span class="fu">make</span> everything</span></code></pre></div>
-<p>For more help on compiling entries, see also <a href="#make_rules">3.0 - What Makefile rules are
-available to build or clean up IOCCC entries?</a>.</p>
+<p>For more help on compiling entries, see also the
+FAQ on “<a href="#make_rules">IOCCC Makefile rules</a>”.</p>
 <p>Of course in this case you can also switch to individual entries and look at the
 <code>index.html</code> file (or any other file in the entry) and try out the entries that
 interest you, as if you downloaded that entry’s individual tarball.</p>
@@ -2867,7 +2939,8 @@ original code is in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/m
 some cases, such as <code>1984/mullender</code>, the original code is the same as the code
 as no changes were made (there is an alt version for systems that are not
 VAX-11/PDP-11, however).</p>
-<p>See also <a href="#what_changed">FAQ 4.2: What was changed in an IOCCC entry source code?</a></p>
+<p>See also
+FAQ on “<a href="#what_changed">entry source code changes</a>”</p>
 <div id="faq4_4">
 <h3 id="faq-4.4-what-is-the-meaning-of-the-file-ending-in-.orig.c-in-ioccc-entries">FAQ 4.4: What is the meaning of the file ending in .orig.c in IOCCC entries?</h3>
 </div>
@@ -2929,8 +3002,9 @@ other times something else.</p>
 </div>
 <p>Like with files being renamed, there are multiple reasons files were added or
 removed. The addition of the <code>try.sh</code> and <code>try.alt.sh</code> scripts is the most
-significant example of files being added. These scripts, as the <a href="#try">FAQ about this
-says</a>, help demonstrate entries by automating commands, sometimes many
+significant example of files being added. These scripts, as the
+FAQ on “<a href="#try">try.sh and try.alt.sh</a>”,
+help demonstrate entries by automating commands, sometimes many
 commands and not always simple commands, that one would previously have to run
 manually (there are other benefits as well).</p>
 <p>Alternate code, sometimes provided by the author, sometimes provided by the
@@ -2954,7 +3028,9 @@ ways.</p>
 <p>The <a href="bugs.html">known bugs</a> file, order by IOCCC years, contains a
 list of known bugs &amp; (mis)features. If you are looking for an IOCCC entry
 to try and fix, this file is a good place to start.</p>
-<p>See <a href="#fix_an_entry">FAQ 5.2</a> for information on how to submit a fix to
+<p>See
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
+for information on how to submit a fix to
 an IOCCC entry. Before you consider trying to fix an IOCCC winning entry,
 please check the <a href="bugs.html">known bugs</a> file for the IOCCC entry
 in question. Note that in several cases what you may have discovered,
@@ -2978,10 +3054,11 @@ course if the entry does not work we’ll certainly be more inclined to accept t
 fix. If it is accepted we’ll be happy to credit you in the
 <a href="thanks-for-help.html">thanks</a> file. If you’re a previous author of a winning IOCCC entry we will happily
 link to your entries; if you’re not we can link to your website if you wish.</p>
-<p>Please see <a href="#fix_an_entry">FAQ 5.2 How may I submit a fix to an IOCCC
-entry</a> for information on how to submit a fix to an
-IOCCC entry. See also the <a href="#pull_request">FAQ 6.10 How does someone make a change
-to a file and submit that change as a GitHub pull request</a>
+<p>Please see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
+for information on how to submit a fix to an
+IOCCC entry. See also the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
 for more information about pull requests.</p>
 <div id="faq5_2">
 <div id="fix_an_entry">
@@ -3014,10 +3091,11 @@ IOCCC winning entries are presented!</p>
 <a href="https://github.com/ioccc-src/winner/pulls">GitHub pull request</a>
 against the <a href="https://github.com/ioccc-src/winner/branches">master branch</a>
 of the <a href="https://github.com/ioccc-src/winner">ioccc-src/winner repo</a>.</p>
-<p>Please see <a href="#fix_an_entry">FAQ 5.2 How may I submit a fix to an IOCCC
-entry</a>. See also the <a href="#pull_request">FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request</a> for more information about pull requests.</p>
+<p>Please see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”.
+See also the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
+for more information about pull requests.</p>
 <p>Note that we’re much more inclined to accept an author’s fixes but the judges
 have the final say in the matter.</p>
 <div id="faq5_3">
@@ -3026,13 +3104,17 @@ have the final say in the matter.</p>
 </div>
 </div>
 <p>If you discover a problem with the IOCCC website that is related
-to a particular IOCCC entry, please see <a href="#report_bug">FAQ 5.1</a> for
-information about reporting a bug in an IOCCC entry, and see <a href="#fix_an_entry">FAQ
-5.2</a> for information on how to submit a fix to an IOCCC entry.</p>
+to a particular IOCCC entry, please see
+FAQ on “<a href="#report_bug">report entry bug</a>”
+for information about reporting a bug in an IOCCC entry, and see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
+for information on how to submit a fix to an IOCCC entry.</p>
 <p>If you discover a problem with the IOCCC website (such as a broken link, which
 may or may not be specific to a particular IOCCC entry) that is <strong>not related
 to a particular IOCCC entry</strong>, the best way you can help is to submit a fix to
-the IOCCC website. See <a href="#fix_web_site">FAQ 5.4</a> for information on submitting fixes
+the IOCCC website. See
+FAQ on “<a href="#fix_web_site">fixing the website</a>”
+for information on submitting fixes
 to the IOCCC website.</p>
 <p>If you do not have an IOCCC website fix, and just wish to report a general IOCCC
 website problem, we ask that you first look at the <a href="https://github.com/ioccc-src/winner/issues">IOCCC
@@ -3046,15 +3128,18 @@ to <a href="https://github.com/ioccc-src/winner/issues/new">open a new IOCCC iss
 </div>
 </div>
 <p>For IOCCC website problems that relate to a particular IOCCC entry, please
-see <a href="#fix_an_entry">FAQ 5.2</a> for information on how submit a fix to an IOCCC entry.</p>
+see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
+for information on how submit a fix to an IOCCC entry.</p>
 <p>You may open a <a href="https://github.com/ioccc-src/winner/pulls">GitHub pull request</a>
 against the <a href="https://github.com/ioccc-src/winner/branches">master branch</a>
 of the <a href="https://github.com/ioccc-src/winner">ioccc-src/winner repo</a>
 to submit a fix.</p>
-<p>Please see <a href="#fix_an_entry">FAQ 5.2 How may I submit a fix to an IOCCC
-entry</a>. See also the <a href="#pull_request">FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request</a> for more information about pull requests.</p>
+<p>Please see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”.
+See also the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
+for more information about pull requests.</p>
 <h4 id="some-html-files-should-not-be-directly-modified">Some HTML files should NOT be directly modified</h4>
 <p>Nearly all HTML files on the <a href="https://www.ioccc.org">IOCCC website</a>
 are built from <a href="https://daringfireball.net/projects/markdown/">markdown</a> files.
@@ -3074,14 +3159,15 @@ For example, in <a href="contact.html">contact.html</a>, one may read:</p>
    &lt;!-- !!! Do not modify this web page, instead modify the file: contact.md --&gt;
    &lt;!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! --&gt;</code></pre>
 <p>This means that you could consider editing the referenced markdown file
-AND then run <code>make www</code> from the top level directory in your <a href="#pull_request">IOCCC pull
-request</a>. There are quicker ways but to be sure you get
+AND then run <code>make www</code> from the top level directory in your IOCCC pull
+request. There are quicker ways but to be sure you get
 everything built you should do this. If you modified a markdown and you do not
 see the same file as a html file then you did not complete the fix.</p>
-<p>Please see <a href="#fix_an_entry">FAQ 5.2 How may I submit a fix to an IOCCC
-entry</a>. See also the <a href="#pull_request">FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request</a> for more information about pull requests.</p>
+<p>Please see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”.</p>
+<p>See also the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
+for more information about pull requests.</p>
 <p>In some cases, the HTML file is <strong>NOT</strong> based on markdown content, but instead
 came from JSON and other data files. So instead of the above reference to a
 markdown file, you will read:</p>
@@ -3095,7 +3181,9 @@ markdown file, you will read:</p>
 <p>This means there is <strong>NOT even a markdown file to edit</strong>. Instead one must
 modify JSON files and/or change a <a href="bin/index.html">bin directory tool</a>.</p>
 <p>If this happens, consider opening up an <a href="https://github.com/ioccc-src/winner/issues">IOCCC issue</a>
-and ask for help. See <a href="#fix_an_entry">FAQ 5.3</a> for information on opening up an IOCCC issue.</p>
+and ask for help. See
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
+for information on opening up an IOCCC issue.</p>
 <div id="faq5_5">
 <div id="fix_author">
 <h2 id="faq-5.5-how-may-i-correct-or-update-ioccc-author-information">FAQ 5.5: How may I correct or update IOCCC author information?</h2>
@@ -3105,20 +3193,29 @@ and ask for help. See <a href="#fix_an_entry">FAQ 5.3</a> for information on ope
 <p>If you know the location of an author listed under:</p>
 <p>      <strong><a href="location.html#ZZ">ZZ - Unknown location</a></strong></p>
 <p>or if you find IOCCC author location that is incorrect,
-then <strong>please <a href="faq.html#pull_request">submit a pull request</a></strong>,
+then <strong>please submit a pull request</strong>,
 or at least <a href="contact.html">inform the IOCCC judges</a>.</p>
+<p>See the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
+for more information.</p>
 <p>Authors of IOCCC winning entries are kept in JSON files of the form:</p>
 <pre><code>    author/author_handle.json</code></pre>
 <p>where <code>author_handle</code> is an author handle.</p>
-<p>See <a href="#author_handle_faq">FAQ 6.5</a> for more information about author handles.</p>
-<p>See <a href="#author_json">FAQ 6.6</a> for information about the contents of these JSON file and
-how they are used.</p>
-<p>See <a href="#find_author_handle">FAQ 6.13</a> for how to find your own <em>author_handle</em>.</p>
+<p>See the
+FAQ on “<a href="#author_handle_faq">author handle</a>”
+for more information about author handles.</p>
+<p>See the
+FAQ on “<a href="#author_json">author_handle.json</a>”
+for information about the contents of these JSON file and how they are used.</p>
+<p>See the
+FAQ on “<a href="#find_author_handle">finding author handles</a>”
+for how to find your own <em>author_handle</em>.</p>
 <p>The contents of these JSON files contain the best known information
-about authors of IOCCC entries. See <a href="#author_json">FAQ 6.6</a> for information
-about the contents of these JSON file and how they are used.</p>
+about authors of IOCCC entries. See
+FAQ on “<a href="#author_json">author_handle.json</a>”
+for information about the contents of these JSON file and how they are used.</p>
 <p>You may update IOCCC author information in a <code>author_handle.json</code> file
-by <a href="faq.html#pull_request">submitting a pull request</a>
+by <a href="#pull_request">submitting a pull request</a>
 against the <a href="https://github.com/ioccc-src/winner/branches">master branch</a>
 of the <a href="https://github.com/ioccc-src/winner">ioccc-src/winner repo</a>.</p>
 <p>As these files are JSON you should verify that they are validly formed (e.g. you
@@ -3154,10 +3251,11 @@ timestamp was updated, the
 only worry about those two files. This greatly speeds things along.</p>
 <p>Once that command finishes a proper <code>git status</code> and <code>git diff</code> shows that
 everything is in order. In the end the safest way is to run <code>make www</code>, however.</p>
-<p>Please see <a href="#fix_an_entry">FAQ 5.2 How may I submit a fix to an IOCCC entry?</a>.</p>
-<p>See also the <a href="#pull_request">FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request</a> for more information about pull requests.</p>
+<p>Please see
+FAQ on “<a href="#fix_an_entry">fixing an entry</a>”.</p>
+<p>See also the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
+for more information about pull requests.</p>
 <p><strong>FYI</strong>: The <a href="location.html#ZZ">ZZ - Unknown location</a> is used for
 historic winning authors whose location or country is not known,
 whereas the <a href="location.html#XX">XX - Anonymous location</a> is used when the
@@ -3175,11 +3273,12 @@ want to have the location known but not their name and/or other details.</p>
 <p>We would appreciate if you try to fix the broken (the link goes nowhere) or wrong
 (the link goes to something that clearly is not the original intent) web link.
 If wish to fix such links, you may open a GitHub pull request as described in
-<a href="#fix_web_site">FAQ 5.4</a>. In the case of dead links or invalid links it doesn’t matter
+FAQ on “<a href="#fix_web_site">fixing the website</a>”.
+In the case of dead links or invalid links it doesn’t matter
 if it’s a specific winner or not; the procedure is the same: open a pull request
-to fix the problem. See also the <a href="#pull_request">FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request</a> for more information about pull requests.</p>
+to fix the problem. See also the
+FAQ on “<a href="#pull_request">GitHub pull request</a>”
+for more information about pull requests.</p>
 <p>As far as how to find the updated link you can try using the <a href="https://web.archive.org">Internet Wayback
 Machine</a> and see if you can find the last non 4xx non
 3xx page. Note, however, that just because it redirects, does not mean it’s not
@@ -3204,7 +3303,8 @@ if the text in some <code>index.html</code> file was:</p>
 <a href="https://web.archive.org">Internet Wayback Machine</a> archive, then
 replace that text with:</p>
 <pre><code>    See the **author&#39;s description of the program** (sorry the content is no longer available) for more information.</code></pre>
-<p>If you just wish to report the bad link issue, see <a href="#report_web_problem">FAQ 5.3</a>.</p>
+<p>If you just wish to report the bad link issue, see
+FAQ on “<a href="#report_web_problem">report website problem</a>”.</p>
 <div id="faq5_7">
 <div id="support">
 <h3 id="faq-5.7-how-may-i-support-the-ioccc">FAQ 5.7: How may I support the IOCCC?</h3>
@@ -3309,10 +3409,12 @@ something like that.</p>
 we request that you ask the <a href="judges.html">IOCCC judges</a> first.</p>
 <p>Please send your request using the instructions on the <a href="contact.html">contacting
 the IOCCC Judges</a> page.</p>
-<p>Please note that the content of the IOCCC is <a href="#copyright">Copyrighted and is under
-the CC BY-SA 4.0 License</a>.</p>
-<p>See <a href="#license">FAQ 6.11</a> for additional information on the
-<a href="license.html">Copyright and CC BY-SA 4.0 License</a>.</p>
+<p>Please note that the content of the IOCCC
+<strong>Copyrighted and is under the CC BY-SA 4.0 License</strong>.
+See the <a href="#copyright">Copyright</a> at the bottom of IOCCC web pages for more details.</p>
+<p>See
+FAQ on “<a href="#license">using IOCCC content</a>”.
+For additional information on the <a href="license.html">Copyright and CC BY-SA 4.0 License</a>.</p>
 <div id="faq6_4">
 <h3 id="faq-6.4-why-do-you-sometimes-use-the-first-person-plural">FAQ 6.4: Why do you sometimes use the first person plural?</h3>
 </div>
@@ -3355,11 +3457,17 @@ exaggeration</a>.</p>
 IOCCC. Each author has exactly one <code>author_handle</code>.</p>
 <p>For each <code>author_handle</code>, there will be a JSON file of the form:</p>
 <pre><code>    author/author_handle.json</code></pre>
-<p>See <a href="#fix_author">FAQ 5.5</a> for information about how to update
+<p>See the
+FAQ on “<a href="#fix_author">fixing author information</a>”
+for information about how to update
 and/or correct IOCCC author information.</p>
-<p>See <a href="#author_json">FAQ 6.6</a> for information about the contents of these JSON file and
+<p>See the
+FAQ on “<a href="#auth_json">.auth.json</a>”
+for information about the contents of these JSON file and
 how they are used.</p>
-<p>See <a href="#find_author_handle">FAQ 6.13</a> for how to find your own <em>author_handle</em>.</p>
+<p>See the
+FAQ on “<a href="#find_author_handle">finding author handle</a>”
+for how to find your own <em>author_handle</em>.</p>
 <p>Because the <code>author_handle</code> is used to form a JSON filename, the string must be
 POSIX safe string plus the use of <code>+</code> (for technical reasons beyond this
 answer). In particular, the <code>author_handle</code> must be an ASCII string or
@@ -3409,8 +3517,9 @@ of the author’s JSON file for ways to contact them.</p>
 <p>Each author of an IOCCC winning entry has their own <code>author_handle.json</code> file
 of the form:</p>
 <pre><code>    author/author_handle.json</code></pre>
-<p>where <em>author_handle</em> is an author handle. See <a href="#author_handle_faq">FAQ 6.5</a> for more
-information about an author handles.</p>
+<p>where <em>author_handle</em> is an author handle. See
+FAQ on “<a href="#author_handle_faq">author handle</a>”
+for more information about an author handles.</p>
 <h4 id="author_handle.json-json-file-contents"><code>author_handle.json</code> JSON file contents</h4>
 <p>The syntax of a <code>author_handle.json</code> follows the <em>So-called JSON spec</em>.
 See <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/jparse/json_index.html#so_called_json_spec">json_index.html</a>
@@ -3510,7 +3619,9 @@ in conjunction with changes to <a href="bin/index.html">bin directory tools</a>.
 <p>This <em>JSON member</em> holds the author handle of the author.</p>
 <p>There <strong>MUST</strong> be one and only one <code>author_handle</code> <em>JSON member</em>
 and the <em>JSON value</em> <strong>MUST</strong> be a <em>JSON string</em> that is also a value author handle.</p>
-<p>See <a href="#author_handle_faq">FAQ 6.5</a> for more information about an author handles.</p>
+<p>See
+FAQ on “<a href="#author_handle_faq">author handle</a>”
+for more information about an author handles.</p>
 <p>Normally the <em>author_handle</em> <em>JSON value</em> should <strong>NOT</strong> be changed
 <strong>unless there is a strong reason to do so</strong>. If the <em>JSON value</em>
 changes, then all of the <code>.entry.json</code> files for all of this authors
@@ -3638,7 +3749,7 @@ For example:</p>
 be a <em>JSON string</em> or it <strong>MUST</strong> be a <em>JSON null</em>. The <em>JSON string</em> just be a valid URL.
 If the <code>mastodon</code> handle is a <em>JSON null</em>, them the <code>mastodon_url</code> <strong>MUST</strong> be a <em>JSON null</em>.
 If the <code>mastodon</code> handle is a <em>JSON string</em>, then the <code>mastodon_url</code> <strong>MUST</strong> be a <em>JSON string</em>.</p>
-<p>The <code>mastodon_url</code> is just a translation of the above mentioned <a href="#mastodon">mastodon</a> handle.
+<p>The <code>mastodon_url</code> is just a translation of the above mentioned Mastodon handle.
 For example, if the Mastodon handle is:</p>
 <pre><code>    @user@server.domain</code></pre>
 <p>Then the <code>mastodon_url</code> would be:</p>
@@ -3648,8 +3759,9 @@ unknown, it should be the <em>JSON null</em> as the <em>JSON value</em> of this
 For example:</p>
 <pre><code>    &quot;mastodon_url&quot; : null,</code></pre>
 <p>NOTE: The <em>JSON null</em> is <strong>NOT</strong> enclosed in quotes!</p>
-<p>See <a href="faq.html#try_mastodon">the FAQ on what is Mastodon and why does IOCCC uses it</a> for more
-information on Mastodon.</p>
+<p>See
+FAQ on “<a href="#try_mastodon">Mastodon</a>”
+for more information on Mastodon.</p>
 <h5 id="github">github</h5>
 <pre><code>    &quot;github&quot; : &quot;@mame&quot;,</code></pre>
 <p>This <em>JSON member</em> holds the <a href="https://github.com">GitHub</a> handle of the author.</p>
@@ -3697,8 +3809,12 @@ a <em>JSON member</em> whose <em>JSON name</em> <strong>MUST</strong> be “<em>
 is a valid entry ID.</p>
 <p>Due to the nature of the <em>So-called JSON spec</em>, the last value of the <code>winning_entry_set</code>
 <em>JSON array</em> cannot end in a comma (<em>,</em>).</p>
-<p>See <a href="#author_json">FAQ 6.7</a> for information about entry ids.</p>
-<p>See <a href="#fix_author">FAQ 5.5</a> for information about how to update
+<p>See
+FAQ on “<a href="#author_json">author_handle.json</a>”
+for information about entry ids.</p>
+<p>See
+FAQ on “<a href="#fix_author">fixing author information</a>”
+for information about how to update
 and/or correct IOCCC author information.</p>
 <div id="faq6_7">
 <!-- we cannot use id="entry_id" because of a header in FAQ 6.6 -->
@@ -4004,7 +4120,9 @@ app from time to time to view IOCCC mastodon updates.</p>
 by going to your entry in the <a href="authors.html">authors.html</a> web page and viewing the string
 that follows the <em>author_handle</em>: line.</p>
 <p>If you are not someone who has won a previous IOCCC, you will be able to select
-a potential <em>author_handle</em> when you form your <em>submission</em> tarball (see <a href="#submit">FAQ 0.0</a>).</p>
+a potential <em>author_handle</em> when you form your <em>submission</em> tarball (see
+FAQ on “<a href="#submit">how to submit</a>”
+).</p>
 <p><strong>Helpful Hint</strong>: If an <em>author</em> clicks on their <em>author_handle:</em>
 line link, you will be taken to that author’s <code>author_handle.json</code> file.</p>
 <p>For example, <a href="authors.html#Brian_Westley">Brian Westley</a> can view his
@@ -4013,12 +4131,20 @@ Clicking on the <em>author_handle</em> shows the contents of
 the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/author/Brian_Westley.json">Brian_Westley.json</a> file.</p>
 <p><strong>IMPORTANT NOTE</strong>: An <code>author</code> who has won a previous IOCCC is encouraged to reuse their
 <code>author_handle</code> so that new winning entries can be associated with the same author.</p>
-<p>See <a href="#fix_author">FAQ 5.5</a> for information about how to update
+<p>See
+FAQ on “<a href="#fix_author">fixing author information</a>”
+for information about how to update
 and/or correct IOCCC author information.</p>
-<p>See <a href="#author_handle_faq">FAQ 6.5</a> for more information about author handles.</p>
-<p>See <a href="#author_json">FAQ 6.6</a> for information about the contents of these JSON file and
+<p>See
+FAQ on “<a href="#author_handle_faq">author handle</a>”
+for more information about author handles.</p>
+<p>See
+FAQ on “<a href="#author_json">author_handle.json</a>”
+for information about the contents of these JSON file and
 how they are used.</p>
-<p>See <a href="#terms">FAQ 6.9</a> for more information on terms such as <em>author</em>, <em>entry</em>, and <em>submission</em>.</p>
+<p>See
+FAQ on “<a href="#terms">Author, Entry, Submission</a>”
+for more information on terms such as <em>author</em>, <em>entry</em>, and <em>submission</em>.</p>
 <div id="faq6_14">
 <div id="tabstops">
 <h3 id="faq-6.14-how-do-i-set-certain-tabstops-for-viewing-source-code-in-vim">FAQ 6.14: How do I set certain tabstops for viewing source code in vi(m)?</h3>
@@ -4046,8 +4172,8 @@ It should look something like:</p>
 width=912 height=160></p>
 <p>Simply move your mouse cursor over the category you want and then click on the
 item you wish to view that drops down from the category.</p>
-<p>This is likely how it will appear with a <a href="faq.html#tablet_menu">tablet device in landscape
-mode</a>, too, unless <a href="faq.html#no_javascript_menu">JavaScript is
+<p>This is likely how it will appear with a <a href="#tablet_menu">tablet device in landscape
+mode</a>, too, unless <a href="#no_javascript_menu">JavaScript is
 disabled</a>.</p>
 <div id="mobile_menus">
 <h4 id="mobile-menus">Mobile menus</h4>
@@ -4082,10 +4208,10 @@ to <a href="https://ioccc-src.github.io/temp-test-ioccc/nojs-menu.html" class="u
 <h5 id="menus-on-tablet-devices-e.g.-ipads">Menus on tablet devices (e.g. iPads)</h5>
 </div>
 <p>With tablets, it likely depends on the orientation you have your device in. If it’s
-in portrait mode you likely will see the <a href="faq.html#mobile_phone_menu">menu that one will get on a mobile
+in portrait mode you likely will see the <a href="#mobile_phone_menu">menu that one will get on a mobile
 phone</a>.</p>
 <p>If, on the other hand, you are using landscape mode, say on an iPad Pro 11 inch
-4th generation, then you will likely see the <a href="faq.html#desktop_menu">menu as you would on a desktop or
+4th generation, then you will likely see the <a href="#desktop_menu">menu as you would on a desktop or
 laptop</a>.</p>
 <div id="1024px_menu">
 <h5 id="menus-on-mobile-devices-wider-than-1024-pixels">Menus on mobile devices wider than 1024 pixels</h5>
@@ -4095,7 +4221,7 @@ very possibly have to <strong>press and hold</strong> the menu icon:</p>
 <p><img src="png/hamburger-icon-open.png"
 alt="menu open icon"
 width=24 height=24></p>
-<p>to activate it. You can then use it <a href="faq.html#mobile_phone_menu">as you would on a mobile
+<p>to activate it. You can then use it <a href="#mobile_phone_menu">as you would on a mobile
 phone</a>.</p>
 <div id="browser_bug_menu">
 <h5 id="browsing-the-website-on-mobile-devices-with-a-browser-bug">Browsing the website on mobile devices with a browser bug</h5>
@@ -4107,10 +4233,10 @@ mode in macOS) the menu does not work at all. That is to say one might see:</p>
 width=1242 height=531></p>
 <p>Notice how the menu icon is not even there! This happens in both portrait mode
 and landscape mode.</p>
-<p>In this case one will have to use the <a href="faq.html#no_javascript_menu">no JavaScript
+<p>In this case one will have to use the <a href="#no_javascript_menu">no JavaScript
 menu</a>. If you have a fix for this that <strong>does NOT
 affect the usability of desktops, laptops or other mobile devices</strong>, please
-consider fixing it and <a href="faq.html#pull_request">opening a pull request</a> or at
+consider fixing it and <a href="#pull_request">opening a pull request</a> or at
 least <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/new/choose">report it as an
 issue</a> (choose
 the category <em>Website issue</em>).</p>
@@ -203,7 +203,9 @@ where:

 * remarks.md

-    Remarks about your entry in markdown format: see [FAQ 2.1](#remarks_md) for more info.
+    Remarks about your entry in markdown format: see
+    FAQ on "[remarks.md](#remarks_md)"
+    for more info.

 * [file ...]

@@ -258,7 +260,8 @@ frequently submitted theme, be sure that it is obfuscated in several
 new and novel ways.

 **IMPORTANT HINT**: Be sure to **clearly explain** near the beginning
-of your `remarks.md` file, see [FAQ 2.1](#remarks_md),
+of your `remarks.md` file, see
+FAQ on "[remarks.md](#remarks_md)",
 **why you are submitting a entry based on a frequently
 submitted theme** and **how compares with previous IOCCC winners**
 of the same theme.
@@ -358,7 +361,8 @@ state something along the lines of:
 ```

 **FAIR WARNING**: Be sure to **clearly explain** near the beginning
-of your `remarks.md` file, see [FAQ 2.1](#remarks_md),
+of your `remarks.md` file, see
+FAQ on "[remarks.md](#remarks_md)",
 **why you are submitting a entry based on a frequently
 submitted theme** and **how compares with previous IOCCC winners**
 of the same theme.
@@ -523,7 +527,8 @@ information, they will ask (either in public or suggest a private conversation).
 Again, **please** don't hesitate to ask: Your question may be something that
 others are wondering about as well!

-See also [FAQ about making suggestions](#feedback).
+See also
+FAQ on "[rules, guidelines, tools feedback](#feedback)".


 <div id="faq0_7">
@@ -533,7 +538,7 @@ See also [FAQ about making suggestions](#feedback).
 </div>

 The IOCCC makes extensive use of [markdown](https://daringfireball.net/projects/markdown/).
-For example, we [submitting to the IOCCC](faq.html#submit), we have people
+For example, we [submitting to the IOCCC](#submit), we have people
 to submit remarks about entry in markdown format.  Every
 [winning IOCCC entry](years.html) uses a `README.md` markdown file
 as the basis for forming the `index.html` web page for that entry.
@@ -616,8 +621,10 @@ submission:
     * The **alt URL** of this author, or `null` if not provided.

 - `mastodon` (null or double quoted string)
-     * The **[Mastodon](#try_mastodon) handle** of this author in the form of `@user@domain`, or
-     `null` if not provided.
+     * The Mastodon handle of this author in the form of `@user@domain`, or
+     `null` if not provided.  See
+     FAQ on "[Mastodon](#try_mastodon)"
+     for more information.

 - `github` (null or double quoted string)
     * The **[GitHub](https://github.com) account** of this author in the form of `@user`, or `null` if not
@@ -650,9 +657,12 @@ submission:

     **NOTE:** if you have won before, we **ENCOURAGE** you to use the same handle of
     your previous winning entries, to help in organising the
-     [authors.html](authors.html) page and the author JSON file (see: [What is an
-     author handle?](#author_handle_faq) and [What is an `author_handle.json`
-     file and how are they used?](#author_json)).
+     [authors.html](authors.html) page and the author JSON file.
+     See
+     FAQ on "[author handle](#author_handle_faq)"
+     and
+     FAQ on "[author_handle.json](#author_json)"
+     for more information.

 - `author_number` (number)
     * This author number in the `authors` array.
@@ -783,7 +793,10 @@ The file also contains the following details:
    **NOT** email the [Judges](judges.html) your submission!

 - `formed_timestamp` (number)
-    * Seconds since epoch when `.auth.json`/[.info json](#info_json) was formed (see `gettimeofday(2)`).
+    * Seconds since epoch when `.auth.json was formed (see `gettimeofday(2)`).
+    See also
+    FAQ on "[.info.json](#info_json)"
+    for more inforation.

    **NOTE:** this **MUST** be greater than or equal to `MIN_TIMESTAMP` (see
    [soup/limit_ioccc.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/limit_ioccc.h)
@@ -853,14 +866,23 @@ This file is constructed by the `mkiocccentry(1)` **prior to** forming the xz
 compressed tarball of your submission. The `.info.json` file contains
 information about the submission, in JSON format. The
 JSON `manifest` array contains information about the files of the submission,
-**including** the **mandatory** [.auth.json](#auth_json), [.info.json](#info_json),
-C source and [remarks](#remarks) files. In particular:
+**including** the **mandatory** `.auth.json` file,
+the  **mandatory** `remarks.md` file,
+and the **mandatory** C source file.
+See the
+FAQ on "[.auth.json](#auth_json)"
+and
+FAQ on "[remarks.md](#remarks_md)"
+for more inforation.

 - `info_JSON` (double quoted string)
    * This `MUST` be `".info.json"`, defined as `INFO_JSON_FILENAME` in
    [soup/entry_util.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h)
    in the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry/), and
-    it is the [.info.json](#info_json) file that `mkiocccentry` forms.
+    it is the `.info.json` file that `mkiocccentry` forms.
+    See the
+    FAQ on "[.info.json](#info_json)"
+    for more information.

    **NOTE:** if this is **NOT** the case you stand a great chance of having your
    submission rejected for violating [Rule 17](next/rules.html#rule17)!
@@ -869,7 +891,10 @@ C source and [remarks](#remarks) files. In particular:
    * This `MUST` be `".auth.json"`, defined as `AUTH_JSON_FILENAME` in
    [soup/entry_util.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h)
    in the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry/), and
-    it is the [.auth.json](#auth_json) file that `mkiocccentry` forms.
+    it is the `.auth.json` file that `mkiocccentry` forms.
+    See the
+    FAQ on "[.auth.json](#auth_json)"
+    for more inforation.

    **NOTE:** if this is **NOT** the case you stand a great chance of having your
    submission rejected for violating [Rule 17](next/rules.html#rule17)!
@@ -891,7 +916,10 @@ C source and [remarks](#remarks) files. In particular:
    * This `MUST` be `"Makefile"`, defined as `MAKEFILE_FILENAME` in
    [soup/entry_util.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h)
    in the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry/), and
-    is your [Makefile](#makefile).
+    is your `Makefile` file.
+    See the
+    FAQ on "[Makefile](#makefile)"
+    for more information.

    **NOTE:** if this is **NOT** the case you stand a great chance of having your
    submission rejected for violating [Rule 17](next/rules.html#rule17)!
@@ -903,7 +931,10 @@ C source and [remarks](#remarks) files. In particular:
    * This `MUST` be `"remarks.md"`, defined as `REMARKS_FILENAME` in
    [soup/entry_util.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h)
    in the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry/), and
-    is your [remarks.md](#remarks).
+    is your `remarks.md]` file.
+    See the
+    FAQ on "[remarks.md](#remarks_md)"
+    for more information.

    **NOTE:** if this is **NOT** the case you stand a great chance of having your
    submission rejected for violating [Rule 17](next/rules.html#rule17)!
@@ -1134,31 +1165,50 @@ The file also contains the following details:

 - `Makefile_override` (boolean)
    * `true` if the user overrides any warnings about an incomplete/incorrect
-    [Makefile](#makefile), else `false`.
+    `Makefile file, else `false`.

-    **NOTE:** if the [Makefile](#makefile) has no problems and this is `true` then
+    **NOTE:** if the `Makefile` file has no problems and this is `true` then
    you stand a good chance of having your submission rejected for violating
    [Rule 17](next/rules.html#rule17)!

+    See the
+    FAQ on "[Makefile](#makefile)"
+    for more information.
+
 - `first_rule_is_all` (boolean)
-    * `true` if the first rule in the [Makefile](#makefile) is
-    `all`, else `false`.
+    * `true` if the first rule in the `Makefile` file is `all`, else `false`.
+
+    See the
+    FAQ on "[Makefile](#makefile)"
+    for more information.

 - `found_all_rule` (boolean)
-    * `true` if the [Makefile](#makefile) has an `all` rule, else
-    `false`.
+    * `true` if the `Makefile` file has an `all` rule, else `false`.
+
+    See the
+    FAQ on "[Makefile](#makefile)"
+    for more information.

 - `found_clean_rule` (boolean)
-    * `true` if the [Makefile](#makefile) has a `clean` rule, else
-    `false`.
+    * `true` if the `Makefile` file has a `clean` rule, else `false`.
+
+    See the
+    FAQ on "[Makefile](#makefile)"
+    for more information.

 - `found_clobber_rule` (boolean)
-    * `true` if the [Makefile](#makefile) has a `clobber` rule,
-    else `false`.
+    * `true` if the `Makefile` file has a `clobber` rule, else `false`.
+
+    See the
+    FAQ on "[Makefile](#makefile)"
+    for more information.

 - `found_try_rule` (boolean)
-    * `true` if the [Makefile](#makefile) has a `try` rule, else
-    `false`.
+    * `true` if the `Makefile` file has a `try` rule, else `false`.
+
+    See the
+    FAQ on "[Makefile](#makefile)"
+    for more information.

 - `test_mode` (boolean)
    * `true` if the `test` ID was used to form the tarball, else `false`.
@@ -1167,7 +1217,7 @@ The file also contains the following details:
    contest! Please do **NOT** email the [Judges](judges.html) your submission!

 - `formed_timestamp` (number)
-    * Seconds since epoch when [.auth.json](#auth_json)/`.info json` was formed (see `gettimeofday(2)`).
+    * Seconds since epoch when JSON (`.auth.json` or `.info.json`) file was formed (see `gettimeofday(2)`).

    **NOTE:** this **MUST** be greater than or equal to `MIN_TIMESTAMP` (see
    [soup/limit_ioccc.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/limit_ioccc.h)
@@ -1836,10 +1886,11 @@ Please see the [bugs.html](bugs.html) file for details about known problems with

 If you have a fix that makes a minimal impact to the entry, then
 please consider submitting that change in the form of a pull request.
-Please see [FAQ 5.2 How may I submit a fix to an IOCCC
-entry](#fix_an_entry).  See also the [FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request](#pull_request) for more information about pull requests.
+Please see
+FAQ on "[fixing an entry](#fix_an_entry)".
+See also the
+FAQ on "[GitHub pull request](#pull_request)"
+for more information about pull requests.

 In some cases alternative code has been added that does compile on some or most
 systems.  Check the write up for the entry for "alt" code and possible ways to
@@ -1880,10 +1931,10 @@ in question to see if the problem is known, and if a fix is wanted,
 consider trying to port the code to a 64-bit system and submitting
 a pull request with that change.  Pull requests that fix such code
 while trying to minimize the impact of any changes and preserving
-the spirit of the original code are very welcome!  Please see [FAQ
-5.2 How may I submit a fix to an IOCCC entry](#fix_an_entry) for
-details.  See also the [FAQ 6.10 How does someone make a change to
-a file and submit that change as a GitHub pull request](#pull_request)
+the spirit of the original code are very welcome!  Please see
+FAQ on "[fixing an entry](#fix_an_entry)"
+for details.  See also the
+FAQ on "[GitHub pull request](#pull_request)"
 for more information about pull requests.


@@ -1902,7 +1953,8 @@ In some cases the [bugs.html](bugs.html) file may note a known macOS problem
 with an entry.  Should you manage to port the entry, and assuming your changes
 also attempt to preserve the original intent of the IOCCC entry, we would
 encourage you to submit a pull request with your ported code.
-Please see [FAQ 5.2 How may I submit a fix to an IOCCC entry](#fix_an_entry)
+Please see
+FAQ on "[fixing an entry](#fix_an_entry)"
 for details.


@@ -1927,10 +1979,11 @@ other things that have to be done plus remembering to do it.
 See if the problem is mentioned in [bugs.html](bugs.html).  If you have a change
 that fixes the problem (even if it just a change to the `Makefile`) that doesn't
 negatively impact the entry too much, consider submitting that change in the
-form of a pull request.  Please see [FAQ 5.2 How may I submit a fix to an IOCCC
-entry](#fix_an_entry).  See also the [FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request](#pull_request) for more information about pull requests.
+form of a pull request.  Please see
+FAQ on "[fixing an entry](#fix_an_entry)".
+See also the
+FAQ on "[GitHub pull request](#pull_request)"
+for more information about pull requests.


 <div id="faq3_5">
@@ -2021,10 +2074,15 @@ information.
 If your system uses **Wayland** and not X11, you might give the IOCCC entries
 that use X11 a try.  They might work but again we do not know.

-**IMPORTANT NOTE**: The [IOCCC judges](judges.html) [do not support IOCCC entries](#no_support).
+**IMPORTANT NOTE**: The [IOCCC judges](judges.html) **do not support IOCCC entries**.
+See the
+FAQ on "[no entry support](#no_support)".
 So if an IOCCC entry that uses X11 fails under **Wayland**, and you wish to
 provide a fix to the IOCCC entry so that it will run under **Wayland**,
-then consider [submitting a fix](#fix_an_entry) so that it will run under **Wayland**.
+then consider submitting a fix so that it will run under **Wayland**.
+See the
+FAQ on "[fixing an entry](#fix_an_entry)"
+for more information.

 Basically: if you discover an entry does not work in Wayland you are welcome to
 provide **alternate code** that works for Wayland. We will happily credit you in
@@ -2033,7 +2091,8 @@ the [thanks-for-help.html](thanks-for-help.html) file.

 #### Red Hat based Linux

-First, see the above note on [installing and starting Xorg](#X11_general).
+First, see
+FAQ on "[general X11](#X11_general)".

 Install Xorg and related packages:

@@ -2045,13 +2104,16 @@ See also:

 * [How to Configure X11 in Linux](https://www.wikihow.com/Configure-X11-in-Linux)

-**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated).
-See the above note for details.
+**IMPORTANT NOTE**: The X.org server has been deprecated.
+See the
+FAQ on "[X.org deprecated](#Xorg_deprecated)"
+for more information.


 #### macOS

-First, see the above note on [installing and starting Xorg](#X11_general).
+First, see the
+FAQ on "[general X11](#X11_general)".
 However, for macOS, instead of installing the Xorg server, you need to install and launch
 the [most recent XQuartz](https://www.xquartz.org) application
 and then run the IOCCC entry from the [Xterm window
@@ -2089,13 +2151,16 @@ Note that you can compile the code in your regular terminal prior to opening
 XQuartz, should you wish to. You can even run it from that terminal and it
 should open XQuartz.

-**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated).
-See the above note for details.
+**IMPORTANT NOTE**: The X.org server has been deprecated.
+See the
+FAQ on "[X.org deprecated](#Xorg_deprecated)"
+for more information.


 #### Debian based Linux

-First, see the above note on [installing and starting Xorg](#X11_general).
+First, see the
+FAQ on "[general X11](#X11_general)".

 According to the [Debian Xorg wiki](https://wiki.debian.org/Xorg), installing
 X11 requires:
@@ -2104,13 +2169,16 @@ X11 requires:
    sudo apt install xorg
 ```

-**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated).
-See the above note for details.
+**IMPORTANT NOTE**: The X.org server has been deprecated.
+See the
+FAQ on "[X.org deprecated](#Xorg_deprecated)"
+for more information.


 #### Other Linux distributions

-First, see the above note on [installing and starting Xorg](#X11_general).
+First, see the
+FAQ on "[general X11](#X11_general)".

 For general documentation on installing  X11, this [ServerGUI for
 Ubuntu](https://help.ubuntu.com/community/ServerGUI), and in particular, these
@@ -2136,18 +2204,23 @@ For systems that have the `yum(1)` command:
    sudo yum install --skip-broken --best --exclude xorgxrdp --exclude xorgxrdp-glamor '*xorg*' 'libx*' 'libX*' 'fontconfig*'
 ```

-**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated).
-See the above note for details.
+**IMPORTANT NOTE**: The X.org server has been deprecated.
+See the
+FAQ on "[X.org deprecated](#Xorg_deprecated)"
+for more information.


 #### Package website

-First, see the above note on [installing and starting Xorg](#X11_general).
+First, see the
+FAQ on "[general X11](#X11_general)".

 See the [X.org](https://x.org/wiki/) foundation website.

-**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated).
-See the above note for details.
+**IMPORTANT NOTE**: The X.org server has been deprecated.
+See the
+FAQ on "[X.org deprecated](#Xorg_deprecated)"
+for more information.


 <div id="faq3_8">
@@ -2187,7 +2260,9 @@ but this might not be necessary in more modern days especially as we use
 `sdl-config` and `sdl2-config` which should find the proper paths.


+<div id="X11macos">
 #### macOS
+</div>

 If you're using macOS there are at least three ways to obtain it. You can
 use Homebrew or MacPorts.  If you do not wish to use either of those
@@ -2268,8 +2343,9 @@ be that you need additional SDL libraries. See the entry's index.html for
 details. If something is not noted you're welcome to report it as an issue or
 fix it and make a pull request.

-See the [FAQ 6.10 How does someone make a change to a file and submit that change
-as a GitHub pull request](#pull_request) for more information about pull requests.
+See the
+FAQ on "[GitHub pull request](#pull_request)"
+for more information about pull requests.


 <div id="faq3_9">
@@ -2582,7 +2658,9 @@ It also possible that you may have discovered a bug in an winning IOCCC
 entry.  If so, you are invited to try and fix the IOCCC entry and
 submit that fix by way of a [GitHub pull
 request](https://github.com/ioccc-src/winner/pulls).
-Please see [FAQ 5.2](#fix_an_entry) for how to submit a fix to an IOCCC entry.
+Please see
+FAQ on "[fixing an entry](#fix_an_entry)"
+for how to submit a fix to an IOCCC entry.


 <div id="faq3_14">
@@ -2861,9 +2939,9 @@ We recommend trying a method suitable for your environment first, if possible.

 This depends on your operating system for which we describe a couple below.

-In general OpenGL needs X11 to be installed and the X Window Server to be running.
-See [FAQ 3.7: How do I run an IOCCC entry that requires X11?](#X11_general) for
-general information about X11.
+In general OpenGL needs X11 to be installed and the X Window Server to be running.  See
+FAQ on "[X11](#X11)"
+for general information about X11.

 Once X11 is install and the X Window Server is running, one needs to compile
 and link with the two libraries, _GL_ and _GLU_:
@@ -3014,8 +3092,8 @@ then do:

 to compile all versions and then run the alternate version (if you have
 a PDP-11 or VAX-11 you would be able to run the original version). For more help
-on compiling entries, see also [3.0  - What Makefile rules are available to
-build or clean up IOCCC entries?](#make_rules).
+on compiling entries, see also the
+FAQ on "[IOCCC Makefile rules](#make_rules)".

 If you want to view the `index.html` file you can point your browser to the
 `index.html` file of the winning entry (e.g. `1984/mullender/index.html`) with the
@@ -3066,8 +3144,8 @@ entry:
        make everything
 ```

-For more help on compiling entries, see also [3.0  - What Makefile rules are
-available to build or clean up IOCCC entries?](#make_rules).
+For more help on compiling entries, see also the
+FAQ on "[IOCCC Makefile rules](#make_rules)".

 Of course in this case you can also switch to individual entries and look at the
 `index.html` file (or any other file in the entry) and try out the entries that
@@ -3298,7 +3376,8 @@ some cases, such as `1984/mullender`, the original code is the same as the code
 as no changes were made (there is an alt version for systems that are not
 VAX-11/PDP-11, however).

-See also [FAQ 4.2: What was changed in an IOCCC entry source code?](#what_changed)
+See also
+FAQ on "[entry source code changes](#what_changed)"


 <div id="faq4_4">
@@ -3381,8 +3460,9 @@ There were certainly other reasons as well.

 Like with files being renamed, there are multiple reasons files were added or
 removed. The addition of the `try.sh` and `try.alt.sh` scripts is the most
-significant example of files being added. These scripts, as the [FAQ about this
-says](#try), help demonstrate entries by automating commands, sometimes many
+significant example of files being added. These scripts, as the
+FAQ on "[try.sh and try.alt.sh](#try)",
+help demonstrate entries by automating commands, sometimes many
 commands and not always simple commands, that one would previously have to run
 manually (there are other benefits as well).

@@ -3417,7 +3497,9 @@ The [known bugs](bugs.html) file, order by IOCCC years, contains a
 list of known bugs & (mis)features.  If you are looking for an IOCCC entry
 to try and fix, this file is a good place to start.

-See [FAQ 5.2](#fix_an_entry) for information on how to submit a fix to
+See
+FAQ on "[fixing an entry](#fix_an_entry)"
+for information on how to submit a fix to
 an IOCCC entry.  Before you consider trying to fix an IOCCC winning entry,
 please check the [known bugs](bugs.html) file for the IOCCC entry
 in question.  Note that in several cases what you may have discovered,
@@ -3448,10 +3530,11 @@ fix. If it is accepted we'll be happy to credit you in the
 [thanks](thanks-for-help.html) file. If you're a previous author of a winning IOCCC entry we will happily
 link to your entries; if you're not we can link to your website if you wish.

-Please see [FAQ 5.2 How may I submit a fix to an IOCCC
-entry](#fix_an_entry) for information on how to submit a fix to an
-IOCCC entry.  See also the [FAQ 6.10 How does someone make a change
-to a file and submit that change as a GitHub pull request](#pull_request)
+Please see
+FAQ on "[fixing an entry](#fix_an_entry)"
+for information on how to submit a fix to an
+IOCCC entry.  See also the
+FAQ on "[GitHub pull request](#pull_request)"
 for more information about pull requests.


@@ -3494,10 +3577,11 @@ And of course, an IOCCC author may update their own entries
 against the [master branch](https://github.com/ioccc-src/winner/branches)
 of the [ioccc-src/winner repo](https://github.com/ioccc-src/winner).

-Please see [FAQ 5.2 How may I submit a fix to an IOCCC
-entry](#fix_an_entry).  See also the [FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request](#pull_request) for more information about pull requests.
+Please see
+FAQ on "[fixing an entry](#fix_an_entry)".
+See also the
+FAQ on "[GitHub pull request](#pull_request)"
+for more information about pull requests.

 Note that we're much more inclined to accept an author's fixes but the judges
 have the final say in the matter.
@@ -3510,14 +3594,18 @@ have the final say in the matter.
 </div>

 If you discover a problem with the IOCCC website that is related
-to a particular IOCCC entry, please see [FAQ 5.1](#report_bug) for
-information about reporting a bug in an IOCCC entry, and see [FAQ
-5.2](#fix_an_entry) for information on how to submit a fix to an IOCCC entry.
+to a particular IOCCC entry, please see
+FAQ on "[report entry bug](#report_bug)"
+for information about reporting a bug in an IOCCC entry, and see
+FAQ on "[fixing an entry](#fix_an_entry)"
+for information on how to submit a fix to an IOCCC entry.

 If you discover a problem with the IOCCC website (such as a broken link, which
 may or may not be specific to a particular IOCCC entry) that is **not related
 to a particular IOCCC entry**, the best way you can help is to submit a fix to
-the IOCCC website.  See [FAQ 5.4](#fix_web_site) for information on submitting fixes
+the IOCCC website.  See
+FAQ on "[fixing the website](#fix_web_site)"
+for information on submitting fixes
 to the IOCCC website.

 If you do not have an IOCCC website fix, and just wish to report a general IOCCC
@@ -3535,17 +3623,20 @@ to [open a new IOCCC issue](https://github.com/ioccc-src/winner/issues/new).
 </div>

 For IOCCC website problems that relate to a particular IOCCC entry, please
-see [FAQ 5.2](#fix_an_entry) for information on how submit a fix to an IOCCC entry.
+see
+FAQ on "[fixing an entry](#fix_an_entry)"
+for information on how submit a fix to an IOCCC entry.

 You may open a [GitHub pull request](https://github.com/ioccc-src/winner/pulls)
 against the [master branch](https://github.com/ioccc-src/winner/branches)
 of the [ioccc-src/winner repo](https://github.com/ioccc-src/winner)
 to submit a fix.

-Please see [FAQ 5.2 How may I submit a fix to an IOCCC
-entry](#fix_an_entry).  See also the [FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request](#pull_request) for more information about pull requests.
+Please see
+FAQ on "[fixing an entry](#fix_an_entry)".
+See also the
+FAQ on "[GitHub pull request](#pull_request)"
+for more information about pull requests.

 #### Some HTML files should NOT be directly modified

@@ -3576,15 +3667,17 @@ For example, in [contact.html](contact.html), one may read:
 ```

 This means that you could consider editing the referenced markdown file
-AND then run `make www` from the top level directory in your [IOCCC pull
-request](#pull_request). There are quicker ways but to be sure you get
+AND then run `make www` from the top level directory in your IOCCC pull
+request. There are quicker ways but to be sure you get
 everything built you should do this. If you modified a markdown and you do not
 see the same file as a html file then you did not complete the fix.

-Please see [FAQ 5.2 How may I submit a fix to an IOCCC
-entry](#fix_an_entry).  See also the [FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request](#pull_request) for more information about pull requests.
+Please see
+FAQ on "[fixing an entry](#fix_an_entry)".
+
+See also the
+FAQ on "[GitHub pull request](#pull_request)"
+for more information about pull requests.

 In some cases, the HTML file is **NOT** based on markdown content, but instead
 came from JSON and other data files.  So instead of the above reference to a
@@ -3604,7 +3697,9 @@ This means there is **NOT even a markdown file to edit**.  Instead one must
 modify JSON files and/or change a [bin directory tool](bin/index.html).

 If this happens, consider opening up an [IOCCC issue](https://github.com/ioccc-src/winner/issues)
-and ask for help.  See [FAQ 5.3](#fix_an_entry) for information on opening up an IOCCC issue.
+and ask for help.  See
+FAQ on "[fixing an entry](#fix_an_entry)"
+for information on opening up an IOCCC issue.


 <div id="faq5_5">
@@ -3620,9 +3715,13 @@ If you know the location of an author listed under:
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**[ZZ - Unknown location](location.html#ZZ)**

 or if you find IOCCC author location that is incorrect,
-then **please [submit a pull request](faq.html#pull_request)**,
+then **please submit a pull request**,
 or at least [inform the IOCCC judges](contact.html).

+See the
+FAQ on "[GitHub pull request](#pull_request)"
+for more information.
+
 Authors of IOCCC winning entries are kept in JSON files of the form:

 ```
@@ -3631,19 +3730,25 @@ Authors of IOCCC winning entries are kept in JSON files of the form:

 where `author_handle` is an author handle.

-See [FAQ 6.5](#author_handle_faq) for more information about author handles.
+See the
+FAQ on "[author handle](#author_handle_faq)"
+for more information about author handles.

-See [FAQ 6.6](#author_json) for information about the contents of these JSON file and
-how they are used.
+See the
+FAQ on "[author_handle.json](#author_json)"
+for information about the contents of these JSON file and how they are used.

-See [FAQ 6.13](#find_author_handle) for how to find your own _author_handle_.
+See the
+FAQ on "[finding author handles](#find_author_handle)"
+for how to find your own _author_handle_.

 The contents of these JSON files contain the best known information
-about authors of IOCCC entries.  See [FAQ 6.6](#author_json) for information
-about the contents of these JSON file and how they are used.
+about authors of IOCCC entries.  See
+FAQ on "[author_handle.json](#author_json)"
+for information about the contents of these JSON file and how they are used.

 You may update IOCCC author information in a `author_handle.json` file
-by [submitting  a pull request](faq.html#pull_request)
+by [submitting  a pull request](#pull_request)
 against the [master branch](https://github.com/ioccc-src/winner/branches)
 of the [ioccc-src/winner repo](https://github.com/ioccc-src/winner).

@@ -3692,11 +3797,12 @@ only worry about those two files. This greatly speeds things along.
 Once that command finishes a proper `git status` and `git diff` shows that
 everything is in order. In the end the safest way is to run `make www`, however.

-Please see [FAQ 5.2 How may I submit a fix to an IOCCC entry?](#fix_an_entry).
+Please see
+FAQ on "[fixing an entry](#fix_an_entry)".

-See also the [FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request](#pull_request) for more information about pull requests.
+See also the
+FAQ on "[GitHub pull request](#pull_request)"
+for more information about pull requests.

 **FYI**: The [ZZ - Unknown location](location.html#ZZ) is used for
 historic winning authors whose location or country is not known,
@@ -3720,11 +3826,12 @@ want to have the location known but not their name and/or other details.
 We would appreciate if you try to fix the broken (the link goes nowhere) or wrong
 (the link goes to something that clearly is not the original intent) web link.
 If wish to fix such links, you may open a GitHub pull request as described in
-[FAQ 5.4](#fix_web_site). In the case of dead links or invalid links it doesn't matter
+FAQ on "[fixing the website](#fix_web_site)".
+In the case of dead links or invalid links it doesn't matter
 if it's a specific winner or not; the procedure is the same: open a pull request
-to fix the problem.  See also the [FAQ 6.10 How does someone
-make a change to a file and submit that change as a GitHub pull
-request](#pull_request) for more information about pull requests.
+to fix the problem.  See also the
+FAQ on "[GitHub pull request](#pull_request)"
+for more information about pull requests.

 As far as how to find the updated link you can try using the [Internet Wayback
 Machine](https://web.archive.org) and see if you can find the last non 4xx non
@@ -3761,7 +3868,8 @@ replace that text with:
    See the **author's description of the program** (sorry the content is no longer available) for more information.
 ```

-If you just wish to report the bad link issue, see [FAQ 5.3](#report_web_problem).
+If you just wish to report the bad link issue, see
+FAQ on "[report website problem](#report_web_problem)".


 <div id="faq5_7">
@@ -3910,11 +4018,13 @@ we request that you ask the [IOCCC judges](judges.html) first.
 Please send your request using the instructions on the [contacting
 the IOCCC Judges](contact.html) page.

-Please note that the content of the IOCCC is [Copyrighted and is under
-the CC BY-SA 4.0 License](#copyright).
+Please note that the content of the IOCCC
+**Copyrighted and is under the CC BY-SA 4.0 License**.
+See the [Copyright](#copyright) at the bottom of IOCCC web pages for more details.

-See [FAQ 6.11](#license) for additional information on the
-[Copyright and CC BY-SA 4.0 License](license.html).
+See
+FAQ on "[using IOCCC content](#license)".
+For additional information on the [Copyright and CC BY-SA 4.0 License](license.html).


 <div id="faq6_4">
@@ -3972,13 +4082,19 @@ For each `author_handle`, there will be a JSON file of the form:
    author/author_handle.json
 ```

-See [FAQ 5.5](#fix_author) for information about how to update
+See the
+FAQ on "[fixing author information](#fix_author)"
+for information about how to update
 and/or correct IOCCC author information.

-See [FAQ 6.6](#author_json) for information about the contents of these JSON file and
+See the
+FAQ on "[.auth.json](#auth_json)"
+for information about the contents of these JSON file and
 how they are used.

-See [FAQ 6.13](#find_author_handle) for how to find your own _author_handle_.
+See the
+FAQ on "[finding author handle](#find_author_handle)"
+for how to find your own _author_handle_.

 Because the `author_handle` is used to form a JSON filename, the string must be
 POSIX safe string plus the use of `+` (for technical reasons beyond this
@@ -4060,8 +4176,9 @@ of the form:
    author/author_handle.json
 ```

-where _author_handle_ is an author handle.  See [FAQ 6.5](#author_handle_faq) for more
-information about an author handles.
+where _author_handle_ is an author handle.  See
+FAQ on "[author handle](#author_handle_faq)"
+for more information about an author handles.

 #### `author_handle.json` JSON file contents

@@ -4215,7 +4332,9 @@ This _JSON member_ holds the author handle of the author.
 There **MUST** be one and only one `author_handle` _JSON member_
 and the _JSON value_ **MUST** be a _JSON string_ that is also a value author handle.

-See [FAQ 6.5](#author_handle_faq) for more information about an author handles.
+See
+FAQ on "[author handle](#author_handle_faq)"
+for more information about an author handles.

 Normally the _author_handle_ _JSON value_ should **NOT** be changed
 **unless there is a strong reason to do so**.  If the  _JSON value_
@@ -4451,7 +4570,7 @@ be a _JSON string_ or it **MUST** be a _JSON null_.  The _JSON string_ just be a
 If the `mastodon` handle is a _JSON null_, them the `mastodon_url` **MUST** be a _JSON null_.
 If the `mastodon` handle is a _JSON string_, then the `mastodon_url` **MUST** be a _JSON string_.

-The `mastodon_url` is just a translation of the above mentioned [mastodon](#mastodon) handle.
+The `mastodon_url` is just a translation of the above mentioned Mastodon handle.
 For example, if the Mastodon handle is:

 ```
@@ -4474,8 +4593,9 @@ For example:

 NOTE: The _JSON null_ is **NOT** enclosed in quotes!

-See [the FAQ on what is Mastodon and why does IOCCC uses it](faq.html#try_mastodon) for more
-information on Mastodon.
+See
+FAQ on "[Mastodon](#try_mastodon)"
+for more information on Mastodon.


 ##### github
@@ -4565,9 +4685,13 @@ is a valid entry ID.
 Due to the nature of the  _So-called JSON spec_, the last value of the `winning_entry_set`
 _JSON array_ cannot end in a comma (_,_).

-See [FAQ 6.7](#author_json) for information about entry ids.
+See
+FAQ on "[author_handle.json](#author_json)"
+for information about entry ids.

-See [FAQ 5.5](#fix_author) for information about how to update
+See
+FAQ on "[fixing author information](#fix_author)"
+for information about how to update
 and/or correct IOCCC author information.


@@ -5016,7 +5140,9 @@ by going to your entry in the [authors.html](authors.html) web page and viewing
 that follows the _author_handle_: line.

 If you are not someone who has won a previous IOCCC, you will be able to select
-a potential _author_handle_ when you form your _submission_ tarball (see [FAQ 0.0](#submit)).
+a potential _author_handle_ when you form your _submission_ tarball (see
+FAQ on "[how to submit](#submit)"
+).

 **Helpful Hint**: If an _author_ clicks on their _author_handle:_
 line link, you will be taken to that author's `author_handle.json` file.
@@ -5029,15 +5155,23 @@ the [Brian_Westley.json](%%REPO_URL%%/author/Brian_Westley.json) file.
 **IMPORTANT NOTE**: An `author` who has won a previous IOCCC is encouraged to reuse their
 `author_handle` so that new winning entries can be associated with the same author.

-See [FAQ 5.5](#fix_author) for information about how to update
+See
+FAQ on "[fixing author information](#fix_author)"
+for information about how to update
 and/or correct IOCCC author information.

-See [FAQ 6.5](#author_handle_faq) for more information about author handles.
+See
+FAQ on "[author handle](#author_handle_faq)"
+for more information about author handles.

-See [FAQ 6.6](#author_json) for information about the contents of these JSON file and
+See
+FAQ on "[author_handle.json](#author_json)"
+for information about the contents of these JSON file and
 how they are used.

-See [FAQ 6.9](#terms) for more information on terms such as _author_, _entry_, and _submission_.
+See
+FAQ on "[Author, Entry, Submission](#terms)"
+for more information on terms such as _author_, _entry_, and _submission_.

 <div id="faq6_14">
 <div id="tabstops">
@@ -5080,8 +5214,8 @@ Simply move your mouse cursor over the category you want and then click on the
 item you wish to view that drops down from the category.

 This is likely how it will appear with a [tablet device in landscape
-mode](faq.html#tablet_menu), too, unless [JavaScript is
-disabled](faq.html#no_javascript_menu).
+mode](#tablet_menu), too, unless [JavaScript is
+disabled](#no_javascript_menu).


 <div id="mobile_menus">
@@ -5134,11 +5268,11 @@ to <https://ioccc-src.github.io/temp-test-ioccc/nojs-menu.html>.

 With tablets, it likely depends on the orientation you have your device in. If it's
 in portrait mode you likely will see the [menu that one will get on a mobile
-phone](faq.html#mobile_phone_menu).
+phone](#mobile_phone_menu).

 If, on the other hand, you are using landscape mode, say on an iPad Pro 11 inch
 4th generation, then you will likely see the [menu as you would on a desktop or
-laptop](faq.html#desktop_menu).
+laptop](#desktop_menu).


 <div id="1024px_menu">
@@ -5153,7 +5287,7 @@ very possibly have to **press and hold** the menu icon:
 width=24 height=24>

 to activate it. You can then use it [as you would on a mobile
-phone](faq.html#mobile_phone_menu).
+phone](#mobile_phone_menu).


 <div id="browser_bug_menu">
@@ -5171,9 +5305,9 @@ Notice how the menu icon is not even there! This happens in both portrait mode
 and landscape mode.

 In this case one will have to use the [no JavaScript
-menu](faq.html#no_javascript_menu). If you have a fix for this that **does NOT
+menu](#no_javascript_menu). If you have a fix for this that **does NOT
 affect the usability of desktops, laptops or other mobile devices**, please
-consider fixing it and [opening a pull request](faq.html#pull_request) or at
+consider fixing it and [opening a pull request](#pull_request) or at
 least [report it as an
 issue](https://github.com/ioccc-src/temp-test-ioccc/issues/new/choose) (choose
 the category _Website issue_).
@@ -413,7 +413,8 @@ then consider making pull requests against the <a href="https://github.com/ioccc
 <strong>press and hold</strong> the menu you wish to activate (in the upper right corner) in
 order to activate the pull-down. If this does not work or you prefer to use a
 plaintext menu even with JavaScript enabled, you can do so
-<a href="nojs-menu.html">here</a>. See also the <a href="faq.html#menus">FAQ on menus</a>.</p>
+<a href="nojs-menu.html">here</a>. See also the
+FAQ on “<a href="faq.html#menus">website menus</a>”.</p>
 <h1 id="obfuscate-defined">Obfuscate defined:</h1>
 <p>tr.v. -cated, -cating, -cates.
 <BR><BR>
@@ -434,7 +435,9 @@ plaintext menu even with JavaScript enabled, you can do so
 </ul>
 <h1 id="entering-the-contest">Entering the Contest</h1>
 <p>View the <a href="status.html">current status of the IOCCC</a> to see of the IOCCC is open for submissions.</p>
-<p>See <a href="faq.html#submit">the FAQ about how to enter the IOCCC</a> for more information.</p>
+<p>See
+FAQ on “<a href="faq.html#submit">how to submit</a>”
+for more information.</p>
 <h1 id="important-disclaimer">Important Disclaimer</h1>
 <p>IOCCC code is for <strong>educational and entertainment purposes only</strong>. We do <strong>NOT</strong> recommend installing any winning IOCCC entry code. Use code found the IOCCC repo and in the IOCCC web site <strong>at your own risk!</strong></p>
 <p>The <a href="index.html">IOCCC</a> and the <a href="judges.html">IOCCC judges</a> DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THEY BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.</p>
@@ -34,7 +34,8 @@ On a **touchscreen mobile device** browser **wider than 1024 pixels**,
 **press and hold** the menu you wish to activate (in the upper right corner) in
 order to activate the pull-down. If this does not work or you prefer to use a
 plaintext menu even with JavaScript enabled, you can do so
-[here](nojs-menu.html). See also the [FAQ on menus](faq.html#menus).
+[here](nojs-menu.html). See also the
+FAQ on "[website menus](faq.html#menus)".


 # Obfuscate defined:
@@ -64,7 +65,9 @@ The goals of the IOCCC:

 View the [current status of the IOCCC](status.html) to see of the IOCCC is open for submissions.

-See [the FAQ about how to enter the IOCCC](faq.html#submit) for more information.
+See
+FAQ on "[how to submit](faq.html#submit)"
+for more information.


 # Important Disclaimer
@@ -390,14 +390,17 @@
 <!-- BEFORE: 1st line of markdown file: markdown.md -->
 <h1 id="ioccc-markdown-guidelines">IOCCC markdown guidelines</h1>
 <p>The IOCCC makes extensive use of <a href="https://daringfireball.net/projects/markdown/">markdown</a>.
-For example, when <a href="faq.html#submit">submitting to the IOCCC</a>, we have people
+For example, when submitting to the IOCCC
+we have people
 submit remarks about their entry in markdown format. Every
 <a href="years.html">winning IOCCC entry</a> uses a <code>README.md</code> markdown file
 as the basis for forming the <code>index.html</code> web page for that entry.
 All generated HTML pages on the <a href="https://www.ioccc.org/index.html">Official IOCCC website</a>
 start with some markdown content.</p>
 <p>See the <a href="https://www.markdownguide.org/basic-syntax">markdown syntax</a> guide.
-See also the <a href="https://spec.commonmark.org/current/">CommonMark Spec</a>.</p>
+See also the <a href="https://spec.commonmark.org/current/">CommonMark Spec</a>.
+See the
+FAQ on “<a href="faq.html#submit">how to submit</a>”.</p>
 <p>Nevertheless, the IOCCC does have certain practices that we ask authors to follow.
 Some of these relate to use of markdown directly and others relate to injecting HTML
 into the markdown file.</p>
@@ -1,7 +1,8 @@
 # IOCCC markdown guidelines

 The IOCCC makes extensive use of [markdown](https://daringfireball.net/projects/markdown/).
-For example, when [submitting to the IOCCC](faq.html#submit), we have people
+For example, when submitting to the IOCCC
+we have people
 submit remarks about their entry in markdown format.  Every
 [winning IOCCC entry](years.html) uses a `README.md` markdown file
 as the basis for forming the `index.html` web page for that entry.
@@ -10,6 +11,8 @@ start with some markdown content.

 See the [markdown syntax](https://www.markdownguide.org/basic-syntax) guide.
 See also the [CommonMark Spec](https://spec.commonmark.org/current/).
+See the
+FAQ on "[how to submit](faq.html#submit)".

 Nevertheless, the IOCCC does have certain practices that we ask authors to follow.
 Some of these relate to use of markdown directly and others relate to injecting HTML
@@ -392,8 +392,9 @@
 <h3 id="please-follow-the-ioccc-on-mastodon">Please follow the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a></h3>
 <p>We use Mastodon to make minor announcements, in addition to announcing
 major events such as the opening of a new IOCCC, or who won.</p>
-<p>See “<a href="faq.html#try_mastodon">FAQ 6.12: What is Mastodon and why does IOCCC use it?</a>” for more
-information on Mastodon.</p>
+<p>See
+FAQ on “<a href="faq.html#try_mastodon">Mastodon</a>”
+for more information on Mastodon.</p>
 <h1 id="news">News</h1>
 <h2 id="section">2024-06-08</h2>
 <p>We continue to make good progress on the
@@ -403,7 +404,7 @@ via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</
 files</a> has
 been checked for broken links which leaves two longer files to go. These two
 files are the <a href="bugs.html">bugs.html</a>
-file and the <a href="faq.html">FAQ</a>.</p>
+file and the “<a href="faq.html">IOCCC FAQ</a>”.</p>
 <p>However, where it was thought that those two files would be looked at before the
 other html files, it has been decided that they will be done after the other
 files as it is very possible that some things in these two files will have to be
@@ -419,7 +420,7 @@ June 2024</em> have been checked for invalid links so that only new news updates
 will have to be checked.</p>
 <p>Once those are done the html files of all the entries will be looked at. As
 those are being reviewed it the <a href="bugs.html">bugs.html</a> might very well be
-updated and the <a href="faq.html">FAQ</a> might be as well. This is why, as noted above,
+updated and the “<a href="faq.html">IOCCC FAQ</a>” might be as well. This is why, as noted above,
 we have decided to review these files last, in order to save time and effort in
 not having to look at them more than once on a whole, other than possible
 entries that have to be added at the end, like the example below.</p>
@@ -5,8 +5,9 @@
 We use Mastodon to make minor announcements, in addition to announcing
 major events such as the opening of a new IOCCC, or who won.

-See "[FAQ 6.12: What is Mastodon and why does IOCCC use it?](faq.html#try_mastodon)" for more
-information on Mastodon.
+See
+FAQ on "[Mastodon](faq.html#try_mastodon)"
+for more information on Mastodon.

 <div id="news">
 # News
@@ -22,7 +23,7 @@ One of the [largest html
 files](thanks-for-help.html) has
 been checked for broken links which leaves two longer files to go. These two
 files are the [bugs.html](bugs.html)
-file and the [FAQ](faq.html).
+file and the "[IOCCC FAQ](faq.html)".

 However, where it was thought that those two files would be looked at before the
 other html files, it has been decided that they will be done after the other
@@ -41,7 +42,7 @@ will have to be checked.

 Once those are done the html files of all the entries will be looked at. As
 those are being reviewed it the [bugs.html](bugs.html) might very well be
-updated and the [FAQ](faq.html) might be as well.  This is why, as noted above,
+updated and the "[IOCCC FAQ](faq.html)" might be as well.  This is why, as noted above,
 we have decided to review these files last, in order to save time and effort in
 not having to look at them more than once on a whole, other than possible
 entries that have to be added at the end, like the example below.
@@ -395,9 +395,11 @@ and are <strong>VERY LIKELY</strong> to be updated before the next IOCCC.
 They are are provided as a <strong>VERY TENTATIVE</strong> hint at <strong>what
 MIGHT</strong> be used in the next IOCCC. In some cases they might
 even be a copy of the guidelines from the previous IOCCC.</p>
-<p>See our <a href="../faq.html#feedback">FAQ about providing feedback</a> as well
-as our <a href="../faq.html#question">FAQ about asking questions</a> about
-these guidelines.</p>
+<p>See our
+FAQ on “<a href="#feedback">rules, guidelines, tools feedback</a>”.
+as well as our
+FAQ on “<a href="../faq.html#question">asking questions</a>”
+about these guidelines.</p>
 <h1 id="the-ioccc-is-closed">The IOCCC is closed</h1>
 <p>The IOCCC is <strong>NOT</strong> accepting new submissions at this time. See the
 <a href="../years.html">IOCCC winning entries page</a> for the entries that have won the
@@ -476,8 +478,8 @@ The submit URL should be active on or slightly before <strong>2024-MMM-DD HH:MM:
 The <a href="rules.html">IOCCC rules</a>, <a href="guidelines.html">IOCCC
 guidelines</a> will be available on the <a href="https://www.ioccc.org">Official IOCCC
 website</a> on or slightly before start of this IOCCC. Please check
-<a href="../faq.html#submit">the IOCCC FAQ about how to submit</a> to see how
-to submit entries, on or after the start of this IOCCC, to be sure
+FAQ on “<a href="../faq.html#submit">how to submit</a>”
+to see how to submit entries, on or after the start of this IOCCC, to be sure
 you are using the correct versions of these items before using the
 IOCCC submission URL.
 </p>
@@ -672,8 +674,8 @@ below) fails to validate the <code>.auth.json</code> or <code>.info.json</code>
 it is an error and possibly a bug that you should <a href="https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&amp;labels=bug&amp;projects=&amp;template=bug_report.yml&amp;title=%5BBug%5D+%3Ctitle%3E">report as a bug at the
 mkiocccentry issues
 page</a>.
-<strong>PLEASE run the <code>bug_report.sh</code> script to help us out here!</strong> See the <a href="../faq.html#mkiocccentry_bugs">the FAQ
-about reporting bugs in the mkiocccentry repo</a>.
+<strong>PLEASE run the <code>bug_report.sh</code> script to help us out here!</strong> See the
+FAQ on “<a href="../faq.html#mkiocccentry_bugs">report mkiocccentry bugs</a>”.
 </p>
 <p class="leftbar">
 However, just because there are errors <strong>does not</strong> mean it is a bug in the
@@ -897,8 +899,8 @@ not pass and you used <code>mkiocccentry(1)</code> it is very possibly a bug and
 <a href="https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&amp;labels=bug&amp;projects=&amp;template=bug_report.yml&amp;title=%5BBug%5D+%3Ctitle%3E">report
 it as a bug at the mkiocccentry issues
 page</a>.
-See the <a href="../faq.html#mkiocccentry_bugs">the FAQ about reporting
-bugs in the mkiocccentry repo</a>.
+See the
+FAQ on “<a href="../faq.html#mkiocccentry_bugs">report mkiocccentry bugs</a>”.
 </p>
 <p class="leftbar">
 Assuming that <code>chkentry(1)</code> validates both <code>.auth.json</code> and
@@ -940,8 +942,8 @@ compressed tarball; if any issues are found (‘<code>feathers are stuck in the
 <code>mkiocccentry(1)</code></strong>, then it is very possibly a bug in one of the tools and you
 should <a href="https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&amp;labels=bug&amp;projects=&amp;template=bug_report.yml&amp;title=%5BBug%5D+%3Ctitle%3E">report it as a bug at the mkiocccentry issues
 page</a>. <strong>PLEASE run the
-<code>bug_report.sh</code> script to help us out here!</strong> See <a href="../faq.html#mkiocccentry_bugs">the FAQ about reporting bugs
-in the mkiocccentry repo</a>.
+<code>bug_report.sh</code> script to help us out here!</strong> See
+FAQ on “<a href="../faq.html#mkiocccentry_bugs">report mkiocccentry bugs</a>”.
 </p>
 <p class="leftbar">
 As part of its sanity checks, <code>txzchk(1)</code> will run <code>fnamchk(1)</code> on the
@@ -955,8 +957,8 @@ would prevent this from happening as it would not create such a file anyway. If
 <code>mkiocccentry(1)</code> was used it would rather suggest a bug in one of the tools and
 you should <a href="https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&amp;labels=bug&amp;projects=&amp;template=bug_report.yml&amp;title=%5BBug%5D+%3Ctitle%3E">report it as a bug at the mkiocccentry issues
 page</a>.
-See <a href="../faq.html#mkiocccentry_bugs">the FAQ about reporting bugs in the mkiocccentry
-repo</a>.
+See
+FAQ on “<a href="../faq.html#mkiocccentry_bugs">report mkiocccentry bugs</a>”.
 </p>
 <p class="leftbar">
 If verbosity level is &gt; 0, <code>txzchk(1)</code> will show the contents of the tarball which is
@@ -1045,8 +1047,9 @@ by modifying the <code>CSTD</code> Makefile variable. For example, to use <code>
 <pre><code>    CSTD= -std=c17</code></pre>
 <p class="leftbar">
 For compilers, such as <code>clang</code>, that have the <code>-Weverything</code> option,
-while you may wish to try it, you should look at <a href="../faq.html#weverything">the FAQ about clang
-Weverything</a>. We do <strong>NOT</strong> recommend that you put
+while you may wish to try it, you should look at
+FAQ on “<a href="../faq.html#weverything">clang -Weverything</a>”.
+We do <strong>NOT</strong> recommend that you put
 the use of <code>-Weverything</code> into your submission’s <code>Makefile</code> for the reasons
 cited there. This goes even if your version does not trigger a warning as some
 other version might!
@@ -1884,7 +1887,8 @@ It has been shown that receiving <strong>anonymous</strong> gifts provides the
 <a href="../judges.html">IOCCC judges</a> help make the <a href="../index.html">IOCCC</a> better for everyone. :-)
 </p>
 <p class="leftbar">
-See <a href="../faq.html#support">FAQ: How may I support the IOCCC?</a>.
+See
+FAQ on “<a href="../faq.html#support">support the IOCCC</a>”.
 </p>
 <p>More often than not, we select a small submission (usually one line) and a
 strange/creative layout submission. We sometimes also select a
@@ -1987,7 +1991,8 @@ See the <a href="../news.html">Official IOCCC website news</a> for additional in
 <p class="change marker">
 For the updates and breaking <a href="../news.html">IOCCC news</a>, you are encouraged to follow
 the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a>. See our
-<a href="../faq.html#try_mastodon">FAQ on Mastodon</a> for more information. <strong>Please be
+FAQ on “<a href="../faq.html#try_mastodon">Mastodon</a>”
+for more information. <strong>Please be
 aware</strong> that unless you are mentioned you most likely will <strong>NOT</strong> get a
 notification so you should make sure to check the page.
 </p>
@@ -8,9 +8,11 @@ They are are provided as a **VERY TENTATIVE** hint at **what
 MIGHT** be used in the next IOCCC.  In some cases they might
 even be a copy of the guidelines from the previous IOCCC.

-See our [FAQ about providing feedback](../faq.html#feedback) as well
-as our [FAQ about asking questions](../faq.html#question) about
-these guidelines.
+See our
+FAQ on "[rules, guidelines, tools feedback](#feedback)".
+as well as our
+FAQ on "[asking questions](../faq.html#question)"
+about these guidelines.


 # The IOCCC is closed
@@ -115,8 +117,8 @@ The submit URL should be active on or slightly before **2024-MMM-DD HH:MM:SS UTC
 The [IOCCC rules](rules.html), [IOCCC
 guidelines](guidelines.html) will be available on the [Official IOCCC
 website](https://www.ioccc.org) on or slightly before start of this IOCCC.  Please check
-[the IOCCC FAQ about how to submit](../faq.html#submit) to see how
-to submit entries, on or after the start of this IOCCC, to be sure
+FAQ on "[how to submit](../faq.html#submit)"
+to see how to submit entries, on or after the start of this IOCCC, to be sure
 you are using the correct versions of these items before using the
 IOCCC submission URL.
 </p>
@@ -354,8 +356,8 @@ below) fails to validate the `.auth.json` or `.info.json`
 it is an error and possibly a bug that you should [report as a bug at the
 mkiocccentry issues
 page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E).
-**PLEASE run the `bug_report.sh` script to help us out here!** See the [the FAQ
-about reporting bugs in the mkiocccentry repo](../faq.html#mkiocccentry_bugs).
+**PLEASE run the `bug_report.sh` script to help us out here!** See the
+FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".
 </p>

 <p class="leftbar">
@@ -558,8 +560,8 @@ not pass and you used `mkiocccentry(1)` it is very possibly a bug and you should
 [report
 it as a bug at the mkiocccentry issues
 page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E).
-See the [the FAQ about reporting
-bugs in the mkiocccentry repo](../faq.html#mkiocccentry_bugs).
+See the
+FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".
 </p>

 <p class="leftbar">
@@ -613,8 +615,8 @@ tarball`' :-) ) **AND if and _ONLY IF_ you used
 `mkiocccentry(1)`**, then it is very possibly a bug in one of the tools and you
 should [report it as a bug at the mkiocccentry issues
 page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E). **PLEASE run the
-`bug_report.sh` script to help us out here!** See [the FAQ about reporting bugs
-in the mkiocccentry repo](../faq.html#mkiocccentry_bugs).
+`bug_report.sh` script to help us out here!** See
+FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".
 </p>

 <p class="leftbar">
@@ -630,8 +632,8 @@ would prevent this from happening as it would not create such a file anyway. If
 `mkiocccentry(1)` was used it would rather suggest a bug in one of the tools and
 you should [report it as a bug at the mkiocccentry issues
 page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E).
-See [the FAQ about reporting bugs in the mkiocccentry
-repo](../faq.html#mkiocccentry_bugs).
+See
+FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".
 </p>

 <p class="leftbar">
@@ -753,8 +755,9 @@ by modifying the `CSTD` Makefile variable.  For example, to use `c17` instead:

 <p class="leftbar">
 For compilers, such as `clang`, that have the `-Weverything` option,
-while you may wish to try it, you should look at [the FAQ about clang
-Weverything](../faq.html#weverything).  We do **NOT** recommend that you put
+while you may wish to try it, you should look at
+FAQ on "[clang -Weverything](../faq.html#weverything)".
+We do **NOT** recommend that you put
 the use of `-Weverything` into your submission's `Makefile` for the reasons
 cited there. This goes even if your version does not trigger a warning as some
 other version might!
@@ -1768,7 +1771,8 @@ It has been shown that receiving  **anonymous** gifts provides the
 </p>

 <p class="leftbar">
-See [FAQ: How may I support the IOCCC?](../faq.html#support).
+See
+FAQ on "[support the IOCCC](../faq.html#support)".
 </p>

 More often than not, we select a small submission (usually one line) and a
@@ -1903,7 +1907,8 @@ See the [Official IOCCC website news](../news.html) for additional information.
 <p class="change marker">
 For the updates and breaking [IOCCC news](../news.html), you are encouraged to follow
 the [IOCCC on Mastodon](https://fosstodon.org/@ioccc).  See our
-[FAQ on Mastodon](../faq.html#try_mastodon) for more information. **Please be
+FAQ on "[Mastodon](../faq.html#try_mastodon)"
+for more information. **Please be
 aware** that unless you are mentioned you most likely will **NOT** get a
 notification so you should make sure to check the page.
 </p>
@@ -395,9 +395,11 @@ and are <strong>VERY LIKELY</strong> to be updated before the next IOCCC.
 They are are provided as a <strong>VERY TENTATIVE</strong> hint at <strong>what
 MIGHT</strong> be used in the next IOCCC. In some cases they might
 even be a copy of the rules from the previous IOCCC.</p>
-<p>See our <a href="../faq.html#feedback">FAQ about providing feedback</a> as well
-as our <a href="../faq.html#question">FAQ about asking questions</a> about
-these rules.</p>
+<p>See our
+FAQ on “<a href="#feedback">rules, guidelines, tools feedback</a>”.
+as well as our
+FAQ on “<a href="../faq.html#question">about asking questions</a>”
+about these rules.</p>
 <h1 id="the-ioccc-is-closed">The IOCCC is closed</h1>
 <p>The IOCCC is <strong>NOT</strong> accepting new submissions at this time. See the
 <a href="../years.html">IOCCC winning entries page</a> for the entries that have won the
@@ -472,7 +474,8 @@ provisional <strong>BETA</strong> versions and <strong>may be adjusted <em>AT AN
 <p>When the IOCCC is open, the submission URL is:
 <a href="https://submit.ioccc.org">https://submit.ioccc.org</a>; at all other
 times that link is likely to be unresponsive.</p>
-<p>Please check the <a href="../faq.html#submit">How to enter FAQ</a>
+<p>Please check the
+FAQ on “<a href="../faq.html#submit">how to submit</a>”
 for <strong>important information</strong> on how to submit to the IOCCC.</p>
 <p class="leftbar">
 The submit URL should be active on or slightly before <strong>2024-MMM-DD HH:MM:SS UTC</strong>.<br>
@@ -482,7 +485,7 @@ The submit URL should be active on or slightly before <strong>2024-MMM-DD HH:MM:
 <p>The official <a href="rules.html">IOCCC rules</a> and <a href="guidelines.html">IOCCC guidelines</a> will be
 available on the <a href="../index.html">official IOCCC website</a> on or slightly before
 the start of this IOCCC. The <code>mkiocccentry</code> toolkit may be obtained at any time
-at the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a>.</p>
+at the <a href="https://github.com/ioccc-src/mkiocccentry">report mkiocccentry bugs</a>.</p>
 <p><strong>Please recheck on or after the start of this IOCCC to be sure you
 are using the correct versions of these items <em>before using the IOCCC
 submission URL</em></strong>.</p>
@@ -570,7 +573,8 @@ as a command like argument to the <code>iocccsize(1)</code> tool. For example:
 <h2 id="rule-3">Rule 3</h2>
 </div>
 <p>Submissions should be performed using the instructions outlined at:
-the <a href="../faq.html#submit">How to enter FAQ</a>.</p>
+the
+FAQ on “<a href="../faq.html#submit">how to submit</a>”</p>
 <p>To submit to an open IOCCC, you must use the <a href="https://submit.ioccc.org/">IOCCC submit
 server</a>. Unless the IOCCC is open, that link will
 likely be unresponsive.</p>
@@ -696,8 +700,9 @@ In order to register for the IOCCC, you <strong>MUST</strong> have a valid email
 enough time for one automated exchange of email as part of your
 submission.</p>
 <p class="leftbar">
-See <a href="../faq.html#register">the FAQ on how to register for the IOCCC</a> in the
-<a href="../faq.html">FAQ</a> for details.
+See
+FAQ on “<a href="../faq.html#register">how to register</a>”
+for details.
 </p>
 <div id="rule16">
 <h2 id="rule-16">Rule 16</h2>
@@ -824,14 +829,18 @@ those requirements.
 The <code>Makefile</code> <strong>MUST</strong> be a <strong>non</strong>-empty file in <strong><a href="https://www.gnu.org/software/make/manual/make.html">GNU
 Makefile</a></strong> form. See the
 <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example">Makefile.example</a>,
-the <a href="../faq.html#submission_makefiles">FAQ about your submission’s Makefile</a> and
-the <a href="../faq.html#make_compatibility">FAQ about IOCCC Makefile compatibility</a> for help.
+the
+FAQ on “<a href="../faq.html#submission_makefiles">submission Makefile</a>”
+and the
+FAQ on “<a href="../faq.html#make_compatibility">Makefile compatibility</a>”
+for help.
 </p>
 <p class="leftbar">
 The <code>remarks.md</code> <strong>MUST</strong> be a <strong>non</strong>-empty file in markdown form. See also
-<a href="#rule18">Rule 18</a> and our <a href="../faq.html#remarks_md">FAQ about what to put in your
-remarks.md</a> and the <a href="../faq.html#markdown">FAQ about IOCCC best markdown
-practices</a>.
+<a href="#rule18">Rule 18</a> and our
+FAQ on “<a href="../faq.html#remarks_md">remarks.md</a>”
+and the
+FAQ on “<a href="../faq.html#markdown">markdown practices</a>”.
 </p>
 <p class="leftbar">
 See also the <a href="https://www.markdownguide.org/basic-syntax">markdown syntax</a> guide
@@ -957,8 +966,8 @@ If you run into a problem with one or more of these tools, <strong>PLEASE</stron
 as a bug at the mkiocccentry issues
 page</a>,
 <strong>making sure to run <code>bug_report.sh</code></strong>. See the <a href="guidelines.html">guidelines</a>
-for help here and also read <a href="../faq.html#mkiocccentry_bugs">the FAQ about reporting bugs in the mkiocccentry
-repo</a>.
+for help here and also read
+FAQ on “<a href="../faq.html#mkiocccentry_bugs">mkiocccentry repo bugs</a>”.
 </p>
 <p class="leftbar">
 At the risk of stating the obvious: submissions that violate <a href="#rule17">Rule
@@ -991,8 +1000,7 @@ Basics</a>.
 We currently use <a href="https://pandoc.org">pandoc</a> to convert markdown to HTML.
 </p>
 <p class="leftbar">
-Please see our <a href="../faq.html#remarks_md">FAQ about what to put in your
-remarks.md</a> and the <a href="../markdown.html">IOCCC markdown
+Please see our FAQ “<a href="../faq.html#remarks_md">remarks.md</a>” and the <a href="../markdown.html">IOCCC markdown
 guidelines</a> for additional markdown guidance.
 </p>
 <div id="rule20">
@@ -1104,7 +1112,8 @@ You should be sure you have the current <a href="rules.html">IOCCC rules</a> and
 <p class="leftbar">
 For the updates and breaking IOCCC news, you are encouraged to follow
 the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a> account. See our
-<a href="../faq.html#try_mastodon">FAQ about Mastodon</a> for more information. Please do note that unless
+FAQ on “<a href="../faq.html#try_mastodon">Mastodon</a>”
+for more information. Please do note that unless
 you are mentioned by us you will <strong>NOT</strong> get a notification from the app <em>so you
 should refresh the page <strong>even if you do follow us</strong></em>.
 </p>
@@ -8,9 +8,11 @@ They are are provided as a **VERY TENTATIVE** hint at **what
 MIGHT** be used in the next IOCCC.  In some cases they might
 even be a copy of the rules from the previous IOCCC.

-See our [FAQ about providing feedback](../faq.html#feedback) as well
-as our [FAQ about asking questions](../faq.html#question) about
-these rules.
+See our
+FAQ on "[rules, guidelines, tools feedback](#feedback)".
+as well as our
+FAQ on "[about asking questions](../faq.html#question)"
+about these rules.


 # The IOCCC is closed
@@ -112,7 +114,8 @@ When the IOCCC is open, the submission URL is:
 [https://submit.ioccc.org](https://submit.ioccc.org); at all other
 times that link is likely to be unresponsive.

-Please check the [How to enter FAQ](../faq.html#submit)
+Please check the
+FAQ on "[how to submit](../faq.html#submit)"
 for **important information** on how to submit to the IOCCC.

 <p class="leftbar">
@@ -125,7 +128,7 @@ Please wait to submit your entries until after that time.
 The official [IOCCC rules](rules.html) and [IOCCC guidelines](guidelines.html) will be
 available on the [official IOCCC website](../index.html) on or slightly before
 the start of this IOCCC. The `mkiocccentry` toolkit may be obtained at any time
-at the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry).
+at the [report mkiocccentry bugs](https://github.com/ioccc-src/mkiocccentry).

 **Please recheck on or after the start of this IOCCC to be sure you
 are using the correct versions of these items _before using the IOCCC
@@ -249,7 +252,8 @@ as a command like argument to the `iocccsize(1)` tool. For example:
 </div>

 Submissions should be performed using the instructions outlined at:
-the [How to enter FAQ](../faq.html#submit).
+the
+FAQ on "[how to submit](../faq.html#submit)"

 To submit to an open IOCCC, you must use the [IOCCC submit
 server](https://submit.ioccc.org/). Unless the IOCCC is open, that link will
@@ -429,8 +433,9 @@ enough time for one automated exchange of email as part of your
 submission.

 <p class="leftbar">
-See [the FAQ on how to register for the IOCCC](../faq.html#register) in the
-[FAQ](../faq.html) for details.
+See
+FAQ on "[how to register](../faq.html#register)"
+for details.
 </p>

 <div id="rule16">
@@ -554,15 +559,19 @@ those requirements.
 The `Makefile` **MUST** be a **non**-empty file in **[GNU
 Makefile](https://www.gnu.org/software/make/manual/make.html)** form. See the
 [Makefile.example](https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example),
-the [FAQ about your submission's Makefile](../faq.html#submission_makefiles) and
-the [FAQ about IOCCC Makefile compatibility](../faq.html#make_compatibility) for help.
+the
+FAQ on "[submission Makefile](../faq.html#submission_makefiles)"
+and the
+FAQ on "[Makefile compatibility](../faq.html#make_compatibility)"
+for help.
 </p>

 <p class="leftbar">
 The `remarks.md` **MUST** be a **non**-empty file in markdown form.  See also
-[Rule 18](#rule18) and our [FAQ about what to put in your
-remarks.md](../faq.html#remarks_md) and the [FAQ about IOCCC best markdown
-practices](../faq.html#markdown).
+[Rule 18](#rule18) and our
+FAQ on "[remarks.md](../faq.html#remarks_md)"
+and the
+FAQ on "[markdown practices](../faq.html#markdown)".
 </p>

 <p class="leftbar">
@@ -690,8 +699,8 @@ If you run into a problem with one or more of these tools, **PLEASE** [report it
 as a bug at the mkiocccentry issues
 page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E),
 **making sure to run `bug_report.sh`**. See the [guidelines](guidelines.html)
-for help here and also read [the FAQ about reporting bugs in the mkiocccentry
-repo](../faq.html#mkiocccentry_bugs).
+for help here and also read
+FAQ on "[mkiocccentry repo bugs](../faq.html#mkiocccentry_bugs)".
 </p>

 <p class="leftbar">At the risk of stating the obvious: submissions that violate [Rule
@@ -735,8 +744,7 @@ We currently use [pandoc](https://pandoc.org) to convert markdown to HTML.
 </p>

 <p class="leftbar">
-Please see our [FAQ about what to put in your
-remarks.md](../faq.html#remarks_md) and the [IOCCC markdown
+Please see our FAQ "[remarks.md](../faq.html#remarks_md)" and the [IOCCC markdown
 guidelines](../markdown.html) for additional markdown guidance.
 </p>

@@ -890,7 +898,8 @@ See the [Official IOCCC website news](../news.html) for additional information.
 <p class="leftbar">
 For the updates and breaking IOCCC news, you are encouraged to follow
 the [IOCCC on Mastodon](https://fosstodon.org/@ioccc) account.  See our
-[FAQ about Mastodon](../faq.html#try_mastodon) for more information. Please do note that unless
+FAQ on "[Mastodon](../faq.html#try_mastodon)"
+for more information. Please do note that unless
 you are mentioned by us you will **NOT** get a notification from the app _so you
 should refresh the page **even if you do follow us**_.
 </p>