improve how markdown code language is commented

We added a space between the markdown triple code mark
and language that was enclosed in HTML comments.

So a line of the form:

````
```<!---c--->
````

became:

````
``` <!---c--->
````

This was done to **help** some code see that the HTML comment
string was not a markdown code specifier.   Not all code
understands this after this changed.  For example, `pandoc(1)`
still forms HTML classes of the form "&lt;!---c--&gt;"
when it encounters the above mentioned change.

We also fixed a problem with `2019/dogon/README.md` regarding
a markdown code block.

We also fixed a problem with `2020/yang/README.md` regarding
a markdown code block.

faq.html

@@ -130,6 +130,7 @@
 <li><a href="#faq0_2">0.2 - What should I put in my entry’s Makefile?</a></li>
 <li><a href="#faq0_3">0.3 - May I use a different source or compiled filename than prog.c or prog?</a></li>
 <li><a href="#faq0_4">0.4 - What platform should I assume for my entry?</a></li>
+<li><a href="#faq0_5">0.5 - How may I comment or make a suggestion on IOCCC rules, guidelines and tools?</a></li>
 </ul>
 <h2 id="section-1---history-of-the-ioccc">Section 1 - <a href="#faq1">History of the IOCCC</a></h2>
 <ul>
@@ -405,6 +406,26 @@ If it can compile and run on Windows and/or Mac (see
 <a href="years.html#2000_thadgavin">2000/thadgavin</a> for one example, amongst others),
 even better. Being able to compile with other compilers like clang is also a
 good thing.</p>
+<h3 id="faq-0.5-how-may-i-comment-or-make-a-suggestion-on-ioccc-rules-guidelines-and-tools"><a name="faq0_5"></a><a name="feedback"></a>FAQ 0.5: How may I comment or make a suggestion on IOCCC rules, guidelines and tools?</h3>
+<p>The <a href="judges.html">IOCCC judges</a> to welcome feedback on the <a href="next/rules.html">IOCCC
+rules</a>, <a href="next/guidelines.html">IOCCC guidelines</a>
+and on the <a href="https://github.com/ioccc-src/mkiocccentry">IOCCC mkiocccentry tools</a>.</p>
+<p>To comment on the <a href="next/rules.html">IOCCC rules</a> or the
+<a href="next/guidelines.html">IOCCC guidelines</a> please view the
+<a href="https://github.com/ioccc-src/temp-test-ioccc/discussions">GitHub discussions for this repo</a>.
+If there is an on-going discussion that seems relevant to what you
+have to say, consider adding comments to that particular discussion.
+Otherwise consider opening a <a href="https://github.com/ioccc-src/temp-test-ioccc/discussions/new/choose">new IOCCC repo
+discussion</a>.</p>
+<p>To comment on <a href="https://github.com/ioccc-src/mkiocccentry">IOCCC mkiocccentry tools</a>,
+please view the <a href="https://github.com/ioccc-src/mkiocccentry/discussions">mkiocccentry repo discussions</a>.
+If there is an on-going discussion that seems relevant to what you
+have to say, consider adding comments to that particular discussion.
+Otherwise consider opening a <a href="https://github.com/ioccc-src/mkiocccentry/discussions/new/choose">new mkiocccentry
+discussion</a>.</p>
+<p>As a very last resort and/or if you feel the need to engage in a private
+discussion with the <a href="judges.html">IOCCC judges</a>, then see
+<a href="contact.html">How to contact the IOCCC</a>.</p>
 <h2 id="section-1-history-of-the-ioccc"><a name="faq1"></a>Section 1: History of the IOCCC</h2>
 <h3 id="faq-1.0-how-did-the-ioccc-get-started"><a name="faq1_0"></a><a name="ioccc_start"></a>FAQ 1.0: How did the IOCCC get started?</h3>
 <p>One day (1984 March 23 to be exact), Larry Bassel and I (Landon Curt