improve next rules and guidelines

Changed version from "2024-06-11-v28"
to "2024-06-15-v28'.

Changed all places where a date was used.

Improved the "XXX - date/time is TBD - XXX" message format.

Removed more stuff about tweeting that we no longer do.

Added a few missing | change marks.

As we fixed a rules typo, we went ahead and merged in a few of the
new rules that were pending.

next/guidelines.html

@@ -404,7 +404,7 @@ granted provided this this copyright and notice are included in its entirety
 and remains unaltered. All other uses must receive prior permission in
 writing by <a href="../contact.html">contacting the judges</a>.</p>
 <h2 id="guidelines-version">Guidelines version</h2>
-<p><strong><code>|</code></strong> This guidelines file is version <strong>2024-06-11-v28</strong>.</p>
+<p><strong><code>|</code></strong> This guidelines file is version <strong>2024-06-15-v28</strong>.</p>
 <p><strong>IMPORTANT</strong>: Be <strong>SURE</strong> to read the <a href="rules.html">IOCCC rules</a>.</p>
 <h3 id="change-marks">Change marks</h3>
 <p><strong><code>|</code></strong> <strong>← Lines that start with this symbol indicate a change from the previous IOCCC</strong></p>
@@ -421,8 +421,8 @@ allowed</em>. Even so, you are safer if you remain within the guidelines.</p>
 <p>You should read the current <a href="rules.html">IOCCC rules</a>, prior to submitting entries.
 The rules are typically published along with these guidelines.</p>
 <h1 id="whats-new-this-ioccc">WHAT’S NEW THIS IOCCC</h1>
-<p><strong><code>|</code></strong> This IOCCC runs from <strong>2024-MMM-DD HH:MM:SS UTC</strong> to <strong>YYYY-MMM-DD HH:MM:SS UTC</strong>.
-** XXX - This date and time is TDB - XXX **.</p>
+<p><strong><code>|</code></strong> This IOCCC runs from <strong>2024-MMM-DD HH:MM:SS UTC</strong> to <strong>YYYY-MMM-DD HH:MM:SS UTC</strong>.<br>
+<strong><code>|</code></strong> <strong>XXX - date/time is TBD - XXX</strong></p>
 <p><strong><code>|</code></strong> The reason for the times of day are so that key IOCCC events are <strong>calculated</strong>
 for be a <strong>fun</strong>ctional UTC time. :-)</p>
 <p>Until the start of this IOCCC, these rules, guidelines and iocccsize.c
@@ -431,8 +431,8 @@ toolkit</a>)
 tool should be considered provisional <strong>BETA</strong> versions and <strong>may be
 adjusted <em>AT ANY TIME</em></strong>.</p>
 <p>The IOCCC submission URL is <a href="https://submit.ioccc.org/" class="uri">https://submit.ioccc.org/</a>.</p>
-<p><strong><code>|</code></strong> The submit URL should be active on or slightly before <strong>2024-MMM-DD HH:MM:SS UTC</strong>.
-<strong>XXX - This date and time is TDB - XXX </strong>.</p>
+<p><strong><code>|</code></strong> The submit URL should be active on or slightly before <strong>2024-MMM-DD HH:MM:SS UTC</strong>.<br>
+<strong><code>|</code></strong> <strong>XXX - date/time is TBD - XXX</strong></p>
 <p>Please wait to submit your entries until after that time.</p>
 <p>The official rules, guidelines and iocccsize.c (invoked by the mkiocccentry)
 tool will be available on the official IOCCC website on or slightly before start
@@ -997,26 +997,6 @@ reveal the number of entries that we received.</p>
 <p>During the judging process, a process that spans multiple sessions
 over a few weeks, post general updates from our <a href="https://fosstodon.org/@ioccc">Mastodon
 account</a>.</p>
-<p>Once we have selected the winners, for each category we will tweet:</p>
-<ul>
-<li>category name</li>
-<li>name(s) of the authors (or anonymous if requested)</li>
-<li>twitter handle(s) (if provided and if anonymity was not requested)</li>
-<li>country code(s) of the author(s)</li>
-</ul>
-<p>After the initial announcement, we attempt to send email to the
-authors of the winning entries. One reason we do this is to give
-the authors a chance to comment on the way we have presented their
-entry. They are given the chance to correct mistakes and typos. We
-often accept their suggestions/comments about our remarks as well.
-This is done prior to posting the winners to the wide world.</p>
-<h2 id="an-important-update-to-how-winners-are-announced">An important update to how winners are announced</h2>
-<p>The IOCCC no longer uses twitter. IOCCC entries will be announced by a git
-commit to the <a href="https://github.com/ioccc-src/winner">IOCCC entries repo</a> that, in
-turn, updates the <a href="https://www.ioccc.org/index.html">official IOCCC website</a>.</p>
-<p>In addition a note is posted to the IOCCC Mastodon account
-(<a href="https://fosstodon.org/@ioccc" class="uri">https://fosstodon.org/@ioccc</a>).</p>
-<h2 id="back-to-the-judging-process">Back to the Judging process</h2>
 <p>Judging consists of a number of elimination rounds. During a round,
 the collection of entries are divided into two roughly equal piles;
 the pile that advances on to the next round, and the pile that does
@@ -1104,7 +1084,7 @@ you are mentioned you will not get a notification.</p>
 <p><strong><code>|</code></strong> The <a href="../judges.html">IOCCC judges</a> will begin to prepare to release the source code of the new IOCCC winners.</p>
 <p><strong><code>|</code></strong> The <a href="../judges.html">IOCCC judges</a> will post the winning source to the <a href="https://github.com/ioccc-src/winner">IOCCC winner repo</a> as well as to the <a href="https://www.ioccc.org/index.html">Official IOCCC winner website</a>.</p>
 <p><strong><code>|</code></strong> The <a href="../news.html">IOCCC news</a> will also contain an announcement of the winners.</p>
-<h2 id="an-important-update-to-how-winners-are-announced-1">An important update to how winners are announced</h2>
+<h2 id="an-important-update-to-how-winners-are-announced">An important update to how winners are announced</h2>
 <p>The IOCCC no longer uses twitter. IOCCC entries will be announced
 by a git commit to the IOCCC entries repo:</p>
 <pre><code>    https://github.com/ioccc-src/winner</code></pre>