Merge pull request #2777 from xexyl/update-faq

Various fixes and updates to FAQ
2024-12-27 10:11:27 -08:00
commit 739c6570dd
@@ -609,14 +609,15 @@ then follow the directions on <strong><a href="next/register.html">How to regist
 <p>Once you have <a href="next/register.html">registered for the IOCCC</a>,
 and once the contest is <strong><a href="status.html#open">OPEN</a></strong>, one of the
 <a href="judges.html">IOCCC judges</a> will send via email within a few days,
-your <a href="https:/submit.ioccc.org">IOCCC submit server</a> <strong>Username</strong> and
+your <a href="https://submit.ioccc.org">IOCCC submit server</a> <strong>Username</strong> and
 <strong>Initial password</strong>.</p>
 <p><strong>PLEASE NOTE</strong>: After registering, it could take up to a <strong>few days</strong>
 before an <a href="judges.html">IOCCC judge</a> sends the that email, so <strong>PLEASE
-be patient</strong>.</p>
+be patient</strong>. This means that you should <strong>GIVE YOURSELF TIME</strong> before the
 contest closes!</p>
 <p><strong>IMPORTANT NOTE</strong>: Unless the contest is <a href="status.html#open">open</a>,
-the you will <strong>NOT</strong> receive your <strong>Username</strong> and <strong>Initial password</strong>
+then you will <strong>NOT</strong> receive your <strong>Username</strong> and <strong>Initial password</strong>
-by email. For example, if contest is <a href="status.html#pending">pending</a>,
+by email. For example, if the contest is <a href="status.html#pending">pending</a>,
 you will have to <strong>WAIT UNTIL THE CONTEST IS <a href="status.html#open">OPEN</a></strong>.</p>
 <p>Please check the <a href="status.html">current status of the IOCCC</a> and
 visit the <a href="next/register.html">How to register for the IOCCC</a> for detailed instructions.</p>
@@ -628,7 +629,7 @@ for assistance.</p>
 <h4 id="login-to-the-submit-server-and-change-your-password">4. Login to the submit server and change your password</h4>
 </div>
 <p>Using the <strong>Username</strong> and <strong>Initial password</strong> you receive via
-email in <a href="#step_3">step 3</a>, you need to login to the <a href="https:/submit.ioccc.org">IOCCC submit
+email in <a href="#step_3">step 3</a>, you need to login to the <a href="https://submit.ioccc.org">IOCCC submit
 server</a>.</p>
 <p><strong>IMPORTANT NOTE</strong>: You must change your password <strong>WITHIN 72 HOURS</strong>
 from when one of the <a href="judges.html">IOCCC judges</a> sent that email.</p>
@@ -2510,7 +2511,7 @@ member</em>. For example:</p>
 be a <em>JSON string</em> or it <strong>MUST</strong> be a <em>JSON null</em>.</p>
 <p>In some cases the author may wish to record a special URL for their IOCCC entry,
 or a 2nd URL such as a work or school or personal home page. For example,
-Cody as of <em>Thu Nov 30 23:51:12 UTC 2023</em> used:</p>
+<a href="authors.html#Cody_Boone_Ferguson">Cody Boone Ferguson</a> as of <em>Thu Nov 30 23:51:12 UTC 2023</em> used:</p>
 <pre><code>    &quot;alt_url&quot; : &quot;https://ioccc.xexyl.net&quot;</code></pre>
 <p>If the author wishes to not specify an alternate URL, or if the alternate URL is
 unknown, it should be the <em>JSON null</em> as the <em>JSON value</em> of this <em>JSON
@@ -2537,7 +2538,7 @@ will always be <code>null</code> anyway.</p>
 <h5 id="mastodon">mastodon</h5>
 <pre><code>    &quot;mastodon&quot; : &quot;@mame@ruby.social&quot;</code></pre>
 <p>This <em>JSON member</em> holds the
-<a href="https://en.wikipedia.org/wiki/Mastodon_(social_network)">Mastodon social network</a>
+<a href="https://en.wikipedia.org/wiki/Mastodon_(social_network)">Mastodon instance</a>
 handle of the author.</p>
 <p>There <strong>MUST</strong> be one and only one <code>mastodon</code> <em>JSON member</em> and the <em>JSON value</em> <strong>MUST</strong>
 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
@@ -2548,11 +2549,11 @@ used by the author.</p>
 See the “Mastodon Address” section of that page in particular.</p>
 <p>The IOCCC Mastodon handle is:</p>
 <pre><code>    @ioccc@fosstodon.org</code></pre>
-<p>The IOCCC uses the Mastodon social network for announcements such
+<p>The IOCCC uses Mastodon for announcements such
 as the opening and closing of a new IOCCC, changes to the IOCCC web
 site, updates during the judging process, and when new IOCCC entries
 are selected. We recommend you follow us on Mastodon.</p>
-<p>If the author wishes to not specify an Mastodon handle, or if the Mastodon handle is
+<p>If the author wishes to not specify a Mastodon handle, or if the Mastodon handle is
 unknown, it should be the <em>JSON null</em> as the <em>JSON value</em> of this <em>JSON member</em>.
 For example:</p>
 <pre><code>    &quot;mastodon&quot; : null</code></pre>
@@ -2567,7 +2568,7 @@ If the <code>mastodon</code> handle is a <em>JSON string</em>, then the <code>ma
 <p>The <code>mastodon_url</code> is just a translation of the above mentioned Mastodon handle.
 For example, if the Mastodon handle is <code>@user@server.domain</code>, then the
 <code>mastodon_url</code> would be <code>https://server.domain/@user</code>.</p>
-<p>If the author wishes to not specify an Mastodon URL, or if the Mastodon URL is
+<p>If the author wishes to not specify a Mastodon URL, or if the Mastodon URL is
 unknown, it should be the <em>JSON null</em> as the <em>JSON value</em> of this <em>JSON member</em>.
 For example:</p>
 <pre><code>    &quot;mastodon_url&quot; : null</code></pre>
@@ -3284,9 +3285,9 @@ further down for different instructions. Otherwise: in particular you must:</p>
 deprecated</a>.</p>
 <p>According to this <a href="https://www.linuxfordevices.com/tutorials/linux/install-xorg-on-linux">Linux for Devices tutorial on
 XOrg</a> as
-of 2023 Mar 25:</p>
+of 2023 Mar 25 (quote verbatim):</p>
 <blockquote>
-<p>Recently, RHEL developers categorized <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.0_release_notes/deprecated_functionality">Xorg was put in the ‘deprecated’
+<p>Recently, RHEL developers categorized Xorg <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.0_release_notes/deprecated_functionality">Xorg was put in the ‘deprecated’
 software</a>,
 as its development has mostly halted. Subsequent updates will completely replace
 it with Wayland, a more modern windowing system.. Although Wayland is not fully
@@ -3918,9 +3919,10 @@ or no longer work on modern computers or modern operating systems, though again
 a great deal of these were fixed for modern systems.</p>
 <p>There are some cases where certain compilers or even certain versions are
 necessary for the program to function in part or even completely.</p>
-<p>Some IOCCC entries might operating system services that may not be present on
+<p>Some IOCCC entries might need operating system services that might not be present on
 your system, as well.</p>
-<p>In some cases the IOCCC entry simply has bugs or (Mis)features.</p>
+<p>In some cases the IOCCC entry simply has <a href="bugs.html">bugs or
 (Mis)features</a>.</p>
 <p>If you are having problems compiling or running an IOCCC entry,
 we recommend that you look in <a href="bugs.html">bugs.html</a> to see if
 there is a known bugs or (Mis)feature. In some cases what you
@@ -4460,7 +4462,7 @@ against fixing it</strong>, then please consider opening a <a href="https://gith
 request</a> against the master
 <a href="https://github.com/ioccc-src/winner/branches">branch</a> of the <a href="https://github.com/ioccc-src/winner">ioccc-src/winner
 repo</a>.</p>
-<p>BTW: A <strong>problem</strong> is not limited to the code itself. Fixing typos in files
+<p><strong>BTW</strong>: A <strong>problem</strong> is not limited to the code itself. Fixing typos in files
 such as “<em>index.html</em>” files (via its respective <code>README.md</code> file), fixing
 issues in a “<em>Makefile</em>”, or otherwise correcting an IOCCC entry is <strong>VERY MUCH
 WELCOME</strong>! Please use the same <a href="https://github.com/ioccc-src/winner/pulls">GitHub pull
@@ -4498,10 +4500,10 @@ have to be logged into your account.</p>
 <p>To help you out here is a navigation menu in this FAQ entry:</p>
 <ul>
 <li><a href="#creating-a-github-account">Creating a GitHub account</a></li>
-<li><a href="#installing-an-ssh-key">Installing an ssh key to GitHub</a></li>
+<li><a href="#installing-an-ssh-key-to-github">Installing an ssh key to GitHub</a></li>
 <li><a href="#forking-the-ioccc-winner-repo">Forking the IOCCC winner repo</a></li>
 <li><a href="#cloning-the-ioccc-winner-repo">Cloning the IOCCC winner repo</a></li>
-<li><a href="#making-changes-fixes-etc">Making changes, fixes etc.</a></li>
+<li><a href="#making-changes-fixes-etc.">Making changes, fixes etc.</a></li>
 <li><a href="#committing-your-changes">Committing your changes</a></li>
 <li><a href="#opening-a-pull-request">Opening a pull request</a></li>
 <li><a href="#what-to-do-after-a-merge">What to do after a merge</a></li>
@@ -4638,7 +4640,7 @@ title</em> could have:</p>
 script that discusses this and gives supposed examples.</p>
 </blockquote>
 <p>Once you’ve done this you should click on <em>Create pull request</em>.</p>
-<p>IMPORTANT NOTE: although the <a href="https://www.ioccc.org/judges.html">Judges</a> will
+<p><strong>IMPORTANT NOTE</strong>: although the <a href="https://www.ioccc.org/judges.html">Judges</a> will
 give more deference to the authors of edited entries the
 <a href="https://www.ioccc.org/judges.html">Judges</a> also retain the final editorial say
 in the matter.</p>
@@ -4763,7 +4765,9 @@ of the <a href="https://github.com/ioccc-src/winner">ioccc-src/winner repo</a>.<
 FAQ on “<a href="#pull_request">GitHub pull request</a>”
 for more information.</p>
 <p><strong>IMPORTANT NOTE</strong>: As these files are JSON you should verify that
-they are validly formed (e.g., you didn’t make a typo).</p>
+they are validly formed (e.g., you didn’t make a typo). See the
 FAQ on “<a href="#jparse">how to validate JSON files</a>”
 for more help.</p>
 <p>Before you form your GitHub pull request that modifies a
 <code>author_handle.json</code> file, please run the <code>make www</code> command. This
 unfortunately takes quite a while but it is the safest way to do
@@ -4905,7 +4909,7 @@ least in most cases; other terms might be used, including on a rare occasion
 <em>spoiler</em>, this depending on context.</p>
 <p>We ask that the <strong>deobfuscated</strong> code be <strong>identical in functionality</strong>
 to the winning IOCCC entry code.</p>
-<p><strong><em>PLEASE</em> NOTE</strong>: Be aware that IOCCC entry code may contain <strong>extremely subtle and
+<p><strong><em>PLEASE</em> NOTE</strong>: Beware that IOCCC entry code may contain <strong>extremely subtle and
 obscure side effects</strong> (i.e., features). Those wishing to contribute a
 <strong>deobfuscated</strong> version of code should <strong>strive to mimic</strong> the original (or
 existing) IOCCC entry code as much as possible. Some authors can be contacted
@@ -5100,7 +5104,7 @@ entries that have won the IOCCC, sometimes in the same IOCCC contest year.</p>
 refer to what is now an <em>author</em>. In a number of historical cases,
 such as old rules and old guidelines, terms such as <em>winner</em> may still be
 found. Moreover, out of habit, the IOCCC judges sometimes use old
-names such as <em>winner</em> when they should use <em>author</em>. Sorry (tm Canada)! :-)</p>
+names such as <em>winner</em> when they should use <em>author</em>. Sorry (tm Canada :-) )!</p>
 <ul>
 <li>Entry</li>
 </ul>
@@ -5116,7 +5120,7 @@ directory <code>YYYY/entry</code>.</p>
 refer to what is now an <em>entry</em>. In a number of historical cases,
 such as old rules and old guidelines, terms such as <em>winner</em> may still be
 found. Moreover, out of habit, the IOCCC judges sometimes use old
-names such as <em>winner</em> when they should use <em>entry</em>. Sorry (tm Canada)! :-)</p>
+names such as <em>winner</em> when they should use <em>entry</em>. Sorry (tm Canada :-) )!</p>
 <ul>
 <li>Submission</li>
 </ul>
@@ -5345,13 +5349,13 @@ this bad!</em></p>
 <a href="http://groups.google.com/groups?q=Obfuscated&amp;hl=en&amp;lr=&amp;ie=UTF-8&amp;as_drrb=b&amp;as_mind=1&amp;as_minm=1&amp;as_miny=1983&amp;as_maxd=18&amp;as_maxm=4&amp;as_maxy=1984&amp;selm=789%40nsc.UUCP&amp;rnum=3&amp;filter=0%22">flame to
 net.lang.c</a>
 inviting people to try and out obfuscate the UN*X source code we had just been working on.</p>
-<p>BTW: I (Landon Curt Noll) had to post this <a href="http://groups.google.com/groups?q=Obfuscated&amp;hl=en&amp;lr=&amp;ie=UTF-8&amp;as_drrb=b&amp;as_mind=1&amp;as_minm=1&amp;as_miny=1983&amp;as_maxd=18&amp;as_maxm=4&amp;as_maxy=1984&amp;selm=795%40nsc.UUCP&amp;rnum=10&amp;filter=0">typo
+<p><strong>BTW</strong>: I (Landon Curt Noll) had to post this <a href="http://groups.google.com/groups?q=Obfuscated&amp;hl=en&amp;lr=&amp;ie=UTF-8&amp;as_drrb=b&amp;as_mind=1&amp;as_minm=1&amp;as_miny=1983&amp;as_maxd=18&amp;as_maxm=4&amp;as_maxy=1984&amp;selm=795%40nsc.UUCP&amp;rnum=10&amp;filter=0">typo
 correction</a>.
 Thus began the tradition of putting typos in the contest rules and guidelines
 … to make them more obfuscated of course! :-)</p>
-<p>BTW: This posting was made back in the days when AT&amp;T was the evil giant.
+<p><strong>BTW</strong>: This posting was made back in the days when AT&amp;T was the evil giant.
 Now, Microsoft makes AT&amp;T look mild and kind in comparison. :-( (IMHO) ).</p>
-<p>BTW: See the story about the ‘<a href="1993/cmills/index.html">Bill Gates</a>’ award. :-)</p>
+<p><strong>BTW</strong>: See the story about the ‘<a href="1993/cmills/index.html">Bill Gates</a>’ award. :-)</p>
 <p>OK, back to the story.</p>
 <p>We (Larry and I) received a number of entries by email.
 When we began to receive messages from outside of the US, Larry and I
@@ -5366,14 +5370,14 @@ were posted on 17 April 1984.</p>
 <li><a href="http://groups.google.com/groups?q=Obfuscated&amp;hl=en&amp;lr=&amp;ie=UTF-8&amp;as_drrb=b&amp;as_mind=1&amp;as_minm=1&amp;as_miny=1983&amp;as_maxd=18&amp;as_maxm=4&amp;as_maxy=1984&amp;selm=844%40nsc.UUCP&amp;rnum=6&amp;filter=0">2nd place</a></li>
 <li><a href="http://groups.google.com/groups?q=Obfuscated&amp;hl=en&amp;lr=&amp;ie=UTF-8&amp;as_drrb=b&amp;as_mind=1&amp;as_minm=1&amp;as_miny=1983&amp;as_maxd=18&amp;as_maxm=4&amp;as_maxy=1984&amp;selm=845%40nsc.UUCP&amp;rnum=5&amp;filter=0">1st place</a></li>
 </ol>
-<p>BTW: The (dis)honorable mention wished to remain anonymous.
+<p><strong>BTW</strong>: The (dis)honorable mention wished to remain anonymous.
 While many have asked who it was, we have continued to follow the
 author’s wish to remain anonymous.</p>
 <p>A few years ago, we asked the author if they still wanted to remain anonymous.
 They said: ‘<em>Yes, I want to keep my anonymity. But you can tell them that I am well known for my connection to the
 C language</em>’. It was not until 2001 that another <a href="2001/anonymous/index.html">anonymous
 entry</a> received an award.</p>
-<p>BTW: The <a href="1984/mullender/index.html">1984/mullender</a> remains one of my (Landon Curt Noll) all time favorites.</p>
+<p><strong>BTW</strong>: The <a href="1984/mullender/index.html">1984/mullender</a> remains one of my (Landon Curt Noll) all time favorites.</p>
 <p>The name used in the posting of the <a href="http://groups.google.com/groups?q=Obfuscated&amp;hl=en&amp;lr=&amp;ie=UTF-8&amp;as_drrb=b&amp;as_mind=1&amp;as_minm=1&amp;as_miny=1983&amp;as_maxd=18&amp;as_maxm=4&amp;as_maxy=1984&amp;selm=837%40nsc.UUCP&amp;rnum=2&amp;filter=0">1st winning IOCCC
 entry</a>
 posting was <strong>I</strong>nternational <strong>O</strong>bfuscated <strong>C</strong> <strong>C</strong>ode <strong>C</strong>ontest or
@@ -5493,7 +5497,8 @@ going back to <a href="https://github.com/ioccc-src/temp-test-ioccc/commit/28efc
 the repo was forked on <strong>Sun Sep 18 17:30:00 2022 -0700</strong>. The
 first <a href="https://github.com/ioccc-src/temp-test-ioccc/commit/edbc3089e1b755d85a020af7975bbc7df3737a5f">push into the temp-test-ioccc
 repo</a>
-occurred on Sun Sep 18 11:15:49 2022 -0700.</p>
+occurred on Sun Sep 18 11:15:49 2022 -0700, by <a href="authors.html#Cody_Boone_Ferguson">Cody Boone
 Ferguson</a>.</p>
 <p>At this same time, the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a> went live.</p>
 <p>Edits were made by an <a href="https://www.ioccc.org/judges.html">IOCCC judge</a>
 to their local <a href="https://git-scm.com">git</a> repository and <a href="https://github.com/ioccc-src/temp-test-ioccc/commit/2f20ae8451ada03f4601ac727d10e1d8630861a8">were pushed into the temp-test-ioccc
@@ -5545,9 +5550,9 @@ from <code>winners.html</code>, via the <a href="https://github.com/ioccc-src/te
 <h4 id="y-mm-dd-the-great-fork-merge">202y mm dd The Great Fork Merge <!-- XXX - Fill in the date when Great Fork Merge happens --></h4>
 </div>
 <!-- XXX - Update the commit count just before Great Fork Merge happens -->
-<p>As of 2024 Oct 20 <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc
+<p>As of 2024 Dec 27 <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc
 repo</a>
-there were <a href="https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master">5975 commits ahead</a>
+there was <a href="https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master">6141+ commits ahead</a>
 of the <a href="https://github.com/ioccc-src/winner">IOCCC winner repo</a>.</p>
 <!-- XXX - Fill in the date when Great Fork Merge happens -->
 <p>On 202y mm dd, the temporary repo was merged back into the <a href="https://github.com/ioccc-src/winner">IOCCC winner
@@ -205,16 +205,17 @@ then follow the directions on **[How to register for the IOCCC](next/register.ht
 Once you have [registered for the IOCCC](next/register.html),
 and once the contest is **[OPEN](status.html#open)**, one of the
 [IOCCC judges](judges.html) will send via email within a few days,
-your [IOCCC submit server](https:/submit.ioccc.org) **Username** and
+your [IOCCC submit server](https://submit.ioccc.org) **Username** and
 **Initial password**.
 **PLEASE NOTE**: After registering, it could take up to a **few days**
 before an [IOCCC judge](judges.html) sends the that email, so **PLEASE
-be patient**.
+be patient**. This means that you should **GIVE YOURSELF TIME** before the
 contest closes!
 **IMPORTANT NOTE**: Unless the contest is [open](status.html#open),
-the you will **NOT** receive your **Username** and **Initial password**
+then you will **NOT** receive your **Username** and **Initial password**
-by email.  For example, if contest is [pending](status.html#pending),
+by email.  For example, if the contest is [pending](status.html#pending),
 you will have to **WAIT UNTIL THE CONTEST IS [OPEN](status.html#open)**.
 Please check the [current status of the IOCCC](status.html) and
@@ -232,7 +233,7 @@ for assistance.
 Using the **Username** and **Initial password** you receive via
 email in [step 3](#step_3), you need to login to the [IOCCC submit
-server](https:/submit.ioccc.org).
+server](https://submit.ioccc.org).
 **IMPORTANT NOTE**: You must change your password **WITHIN 72 HOURS**
 from when one of the [IOCCC judges](judges.html) sent that email.
@@ -2535,7 +2536,7 @@ be a _JSON string_ or it **MUST** be a _JSON null_.
 In some cases the author may wish to record a special URL for their IOCCC entry,
 or a 2nd URL such as a work or school or personal home page.  For example,
-Cody as of  _Thu Nov 30 23:51:12 UTC 2023_ used:
+[Cody Boone Ferguson](authors.html#Cody_Boone_Ferguson) as of _Thu Nov 30 23:51:12 UTC 2023_ used:
 ``` <!---json-->
    "alt_url" : "https://ioccc.xexyl.net"
@@ -2590,7 +2591,7 @@ will always be `null` anyway.
 ```
 This _JSON member_ holds the
-[Mastodon social network](https://en.wikipedia.org/wiki/Mastodon_&lpar;social_network&rpar;)
+[Mastodon instance](https://en.wikipedia.org/wiki/Mastodon_&lpar;social_network&rpar;)
 handle of the author.
 There **MUST** be one and only one `mastodon` _JSON member_ and the _JSON value_ **MUST**
@@ -2608,12 +2609,12 @@ The IOCCC Mastodon handle is:
    @ioccc@fosstodon.org
 ```
-The IOCCC uses the Mastodon social network for announcements such
+The IOCCC uses Mastodon for announcements such
 as the opening and closing of a new IOCCC, changes to the IOCCC web
 site, updates during the judging process, and when new IOCCC entries
 are selected.  We recommend you follow us on Mastodon.
-If the author wishes to not specify an Mastodon handle, or if the Mastodon handle is
+If the author wishes to not specify a Mastodon handle, or if the Mastodon handle is
 unknown, it should be the _JSON null_ as the _JSON value_ of this _JSON member_.
 For example:
@@ -2641,7 +2642,7 @@ The `mastodon_url` is just a translation of the above mentioned Mastodon handle.
 For example, if the Mastodon handle is `@user@server.domain`, then the
 `mastodon_url` would be `https://server.domain/@user`.
-If the author wishes to not specify an Mastodon URL, or if the Mastodon URL is
+If the author wishes to not specify a Mastodon URL, or if the Mastodon URL is
 unknown, it should be the _JSON null_ as the _JSON value_ of this _JSON member_.
 For example:
@@ -3594,10 +3595,10 @@ deprecated](https://access.redhat.com/documentation/en-us/red_hat_enterprise_lin
 According to this [Linux for Devices tutorial on
 XOrg](https://www.linuxfordevices.com/tutorials/linux/install-xorg-on-linux) as
-of 2023 Mar 25:
+of 2023 Mar 25 (quote verbatim):
-> Recently, RHEL developers categorized [Xorg was put in the ‘deprecated’
+> Recently, RHEL developers categorized Xorg [Xorg was put in the ‘deprecated’
 software](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.0_release_notes/deprecated_functionality),
 as its development has mostly halted. Subsequent updates will completely replace
 it with Wayland, a more modern windowing system.. Although Wayland is not fully
@@ -4718,10 +4719,11 @@ a great deal of these were fixed for modern systems.
 There are some cases where certain compilers or even certain versions are
 necessary for the program to function in part or even completely.
-Some IOCCC entries might operating system services that may not be present on
+Some IOCCC entries might need operating system services that might not be present on
 your system, as well.
-In some cases the IOCCC entry simply has bugs or (Mis)features.
+In some cases the IOCCC entry simply has [bugs or
 &lpar;Mis&rpar;features](bugs.html).
 If you are having problems compiling or running an IOCCC entry,
 we recommend that you look in [bugs.html](bugs.html) to see if
@@ -5440,7 +5442,7 @@ 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).
-BTW: A **problem** is not limited to the code itself.  Fixing typos in files
+**BTW**: A **problem** is not limited to the code itself.  Fixing typos in files
 such as "_index.html_" files (via its respective `README.md` file), fixing
 issues in a "_Makefile_", or otherwise correcting an IOCCC entry is **VERY MUCH
 WELCOME**!  Please use the same [GitHub pull
@@ -5490,10 +5492,10 @@ have to be logged into your account.
 To help you out here is a navigation menu in this FAQ entry:
 - [Creating a GitHub account](#creating-a-github-account)
- [Installing an ssh key to GitHub](#installing-an-ssh-key)
+- [Installing an ssh key to GitHub](#installing-an-ssh-key-to-github)
 - [Forking the IOCCC winner repo](#forking-the-ioccc-winner-repo)
 - [Cloning the IOCCC winner repo](#cloning-the-ioccc-winner-repo)
- [Making changes, fixes etc.](#making-changes-fixes-etc)
+- [Making changes, fixes etc.](#making-changes-fixes-etc.)
 - [Committing your changes](#committing-your-changes)
 - [Opening a pull request](#opening-a-pull-request)
 - [What to do after a merge](#what-to-do-after-a-merge)
@@ -5709,7 +5711,7 @@ and then the text field that is labelled _Add a description_ would have:
 Once you've done this you should click on _Create pull request_.
-IMPORTANT NOTE: although the [Judges](https://www.ioccc.org/judges.html) will
+**IMPORTANT NOTE**: although the [Judges](https://www.ioccc.org/judges.html) will
 give more deference to the authors of edited entries the
 [Judges](https://www.ioccc.org/judges.html) also retain the final editorial say
 in the matter.
@@ -5897,7 +5899,9 @@ FAQ on "[GitHub pull request](#pull_request)"
 for more information.
 **IMPORTANT NOTE**: As these files are JSON you should verify that
-they are validly formed (e.g., you didn't make a typo).
+they are validly formed (e.g., you didn't make a typo). See the
 FAQ on "[how to validate JSON files](#jparse)"
 for more help.
 Before you form your GitHub pull request that modifies a
 `author_handle.json` file, please run the `make www` command.  This
@@ -6092,7 +6096,7 @@ _spoiler_, this depending on context.
 We ask that the **deobfuscated** code be **identical in functionality**
 to the winning IOCCC entry code.
-**_PLEASE_ NOTE**: Be aware that IOCCC entry code may contain **extremely subtle and
+**_PLEASE_ NOTE**: Beware that IOCCC entry code may contain **extremely subtle and
 obscure side effects** (i.e., features).  Those wishing to contribute a
 **deobfuscated** version of code should **strive to mimic** the original (or
 existing) IOCCC entry code as much as possible. Some authors can be contacted
@@ -6347,7 +6351,7 @@ entries that have won the IOCCC, sometimes in the same IOCCC contest year.
 refer to what is now an _author_.  In a number of historical cases,
 such as old rules and old guidelines, terms such as _winner_ may still be
 found.  Moreover, out of habit, the IOCCC judges sometimes use old
-names such as _winner_ when they should use _author_.  Sorry (tm Canada)! :-)
+names such as _winner_ when they should use _author_.  Sorry (tm Canada :-) )!
 - Entry
@@ -6366,7 +6370,7 @@ directory `YYYY/entry`.
 refer to what is now an _entry_.  In a number of historical cases,
 such as old rules and old guidelines, terms such as _winner_ may still be
 found.  Moreover, out of habit, the IOCCC judges sometimes use old
-names such as _winner_ when they should use _entry_.  Sorry (tm Canada)! :-)
+names such as _winner_ when they should use _entry_.  Sorry (tm Canada :-) )!
 - Submission
@@ -6692,15 +6696,15 @@ After a few minutes we wandered back into my office where I posted a
 net.lang.c](http://groups.google.com/groups?q=Obfuscated&hl=en&lr=&ie=UTF-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1983&as_maxd=18&as_maxm=4&as_maxy=1984&selm=789%40nsc.UUCP&rnum=3&filter=0")
 inviting people to try and out obfuscate the UN\*X source code we had just been working on.
-BTW: I (Landon Curt Noll) had to post this [typo
+**BTW**: I (Landon Curt Noll) had to post this [typo
 correction](http://groups.google.com/groups?q=Obfuscated&hl=en&lr=&ie=UTF-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1983&as_maxd=18&as_maxm=4&as_maxy=1984&selm=795%40nsc.UUCP&rnum=10&filter=0).
 Thus began the tradition of putting typos in the contest rules and guidelines
 ... to make them more obfuscated of course! :-)
-BTW: This posting was made back in the days when AT&amp;T was the evil giant.
+**BTW**: This posting was made back in the days when AT&amp;T was the evil giant.
 Now, Microsoft makes AT&amp;T look mild and kind in comparison. :-( (IMHO) ).
-BTW: See the story about the '[Bill Gates](1993/cmills/index.html)' award. :-)
+**BTW**: See the story about the '[Bill Gates](1993/cmills/index.html)' award. :-)
 OK, back to the story.
@@ -6719,7 +6723,7 @@ There were 4 entries that won in 1984:
 3. [2nd place](http://groups.google.com/groups?q=Obfuscated&hl=en&lr=&ie=UTF-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1983&as_maxd=18&as_maxm=4&as_maxy=1984&selm=844%40nsc.UUCP&rnum=6&filter=0)
 4. [1st place](http://groups.google.com/groups?q=Obfuscated&hl=en&lr=&ie=UTF-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1983&as_maxd=18&as_maxm=4&as_maxy=1984&selm=845%40nsc.UUCP&rnum=5&filter=0)
-BTW: The (dis)honorable mention wished to remain anonymous.
+**BTW**: The (dis)honorable mention wished to remain anonymous.
 While many have asked who it was, we have continued to follow the
 author's wish to remain anonymous.
@@ -6728,7 +6732,7 @@ They said: '_Yes, I want to keep my anonymity.  But you can tell them that I am
 C language_'. It was not until 2001 that another [anonymous
 entry](2001/anonymous/index.html) received an award.
-BTW: The [1984/mullender](1984/mullender/index.html) remains one of my (Landon Curt Noll) all time favorites.
+**BTW**: The [1984/mullender](1984/mullender/index.html) remains one of my (Landon Curt Noll) all time favorites.
 The name used in the posting of the [1st winning IOCCC
 entry](http://groups.google.com/groups?q=Obfuscated&hl=en&lr=&ie=UTF-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1983&as_maxd=18&as_maxm=4&as_maxy=1984&selm=837%40nsc.UUCP&rnum=2&filter=0)
@@ -6886,7 +6890,8 @@ going back to [2020 Dec
 the repo was forked on **Sun Sep 18 17:30:00 2022 -0700**.  The
 first [push into the temp-test-ioccc
 repo](https://github.com/ioccc-src/temp-test-ioccc/commit/edbc3089e1b755d85a020af7975bbc7df3737a5f)
-occurred on Sun Sep 18 11:15:49 2022 -0700.
+occurred on Sun Sep 18 11:15:49 2022 -0700, by [Cody Boone
 Ferguson](authors.html#Cody_Boone_Ferguson).
 At this same time, the [temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/) went live.
@@ -6945,9 +6950,9 @@ from `winners.html`, via the [gen-authors.sh](%%REPO_URL%%/bin/gen-authors.sh) t
 </div>
 <!-- XXX - Update the commit count just before Great Fork Merge happens -->
-As of 2024 Oct 20 [temp-test-ioccc
+As of 2024 Dec 27 [temp-test-ioccc
 repo](https://github.com/ioccc-src/temp-test-ioccc)
-there were [5975 commits ahead](https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master)
+there was [6141+ commits ahead](https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master)
 of the [IOCCC winner repo](https://github.com/ioccc-src/winner).
 <!-- XXX - Fill in the date when Great Fork Merge happens -->