set tentative IOCCC28 dates, update rules and guidelines

We set dates and times for when IOCCC28 will go into pending state,
open state, and judging state.  These dates are subject to change until
the content enters the open state.

Modified both `next/guidelines.md` and `next/rules.md` as per the
IOCCC28 dates and times.

Improve the `next/guidelines.md` and `next/rules.md` text around IOCCC28 dates and times.

We processed the XXX's in markdown files that needed processing.

Fixed a minor typo in `bin/cvt-submission.sh`.

Made some minor formatting improvements to `faq.md`, `next/register.md`,
`next/rules.md`, `next/guidelines.md`, `README.md` and `index.md`.

Updated "Rule 3" in `next/rules.md` in regards to the above.

Updated "Rule 8" in `next/rules.md` in regards to the above.

Changed `faq.md`  version from **28.1.8 2024-12-07**
to **28.2.0 2024-12-28**.

Changed `next/guidelines.md` version from **28.29 2024-12-27**
to **28.30 2024-12-28**.

Changed `next/rules.md` version from **28.14 2024-12-07**
to **28.15 2024-12-28**.

TODO: Review these changes.

bin/README.md

@@ -359,7 +359,7 @@ This tool will form `YYYY/dir/README.md` if needed, from `YYYY/dir/remarks.md`,
 **NOTE**: This interactive tool (unless `-i input_data` is used) does
 **NOT** perform all of the steps needed to make a directory for a new winning
 IOCCC entry.  For example, files such as `YYYY/dir/README.md` and/or `YYYY/dir/index.html`
-might contain "_triple X_" comments (`<!--XXXX-->`), indicating where the [Judges](../judges.html)
+might contain "_triple X_" comments, indicating where the [Judges](../judges.html)
 need to add content.  Moreover, the `Makefile` and `.gitignore` files
 need to be examined for suitability, etc.
 
@@ -913,7 +913,7 @@ It will form `YYYY/README.md` if needed, from `template/README.md.year`.
 
 **NOTE**: This tool does **NOT** perform all of the steps needed to make a new IOCCC year directory.
 For example, files such as `YYYY/README.md` and/or `YYYY/index.html`
-might contain "_triple X_" comments (`<!-- XXX -->`) indicating where the
+might contain "_triple X_" comments indicating where the
 [Judges](../judges.html) need to add content.
 
 Usage:

bin/cvt-submission.sh

@@ -2193,7 +2193,7 @@ if [[ -z $NOOP ]]; then
 	if [[ -f $YYYY_DIR/remarks.md ]]; then
 	    cat "$YYYY_DIR/remarks.md" >> "$README_MD"
 	else
-	    echo "$X_3 - mo remarks.md file was found" >> "$README_MD"
+	    echo "$X_3 - no remarks.md file was found" >> "$README_MD"
 	fi
 	sed -e "s/$X_3-YEAR-$X_3/$YEAR_DIR/" "$TEMPLATE_README_MD_TAIL" >> "$README_MD"
     fi

bin/index.html

@@ -646,7 +646,7 @@ to be restored as follows:</p>
 <p><strong>NOTE</strong>: This interactive tool (unless <code>-i input_data</code> is used) does
 <strong>NOT</strong> perform all of the steps needed to make a directory for a new winning
 IOCCC entry. For example, files such as <code>YYYY/dir/README.md</code> and/or <code>YYYY/dir/index.html</code>
-might contain “<em>triple X</em>” comments (<code>&lt;!--XXXX--&gt;</code>), indicating where the <a href="../judges.html">Judges</a>
+might contain “<em>triple X</em>” comments, indicating where the <a href="../judges.html">Judges</a>
 need to add content. Moreover, the <code>Makefile</code> and <code>.gitignore</code> files
 need to be examined for suitability, etc.</p>
 <p><strong>HINT</strong>: Executing this tool on your submission will <strong>NOT</strong> make you an IOCCC winner. :-)</p>
@@ -965,7 +965,7 @@ It will form <code>YYYY/Makefile</code> and/or <code>YYYY/.year</code> if needed
 It will form <code>YYYY/README.md</code> if needed, from <code>template/README.md.year</code>.</p>
 <p><strong>NOTE</strong>: This tool does <strong>NOT</strong> perform all of the steps needed to make a new IOCCC year directory.
 For example, files such as <code>YYYY/README.md</code> and/or <code>YYYY/index.html</code>
-might contain “<em>triple X</em>” comments (<code>&lt;!-- XXX --&gt;</code>) indicating where the
+might contain “<em>triple X</em>” comments indicating where the
 <a href="../judges.html">Judges</a> need to add content.</p>
 <p>Usage:</p>
 <pre><code>    bin/new-year.sh -v 1 YYYY</code></pre>