improve word flow around FAQ references

This commit is contained in:
Landon Curt Noll committed 2024-07-21 16:17:20 -07:00
1 parent f7e7610370
commit 89e66b96c5
41 files changed
+289 -213

No files matched your search

+11 -11
View File
@@ -391,13 +391,13 @@
<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
<li><strong>Fix a winning IOCCC entry</strong> - See our
FAQ on “<a href="faq.html#fix_an_entry">fix entry</a>”</li>
<li><strong>Update winning author information</strong> - See
<li><strong>Update winning author information</strong> - See our
FAQ on “<a href="faq.html#fix_author">fixing author information</a>”</li>
<li><strong>Correct a website problem</strong> - See
<li><strong>Correct a website problem</strong> - See our
FAQ on “<a href="faq.html#fix_web_site">fixing the website</a>”
or
or our
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
@@ -406,11 +406,11 @@ 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
<li><strong>Report a bug in an IOCCC winning entry</strong> - See our
FAQ on “<a href="faq.html#report_bug">report entry bug</a>”</li>
<li><strong>Report an IOCCC website problem</strong> - See
<li><strong>Report an IOCCC website problem</strong> - See our
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
<li><strong>Report a broken or wrong web link</strong> - See our
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
@@ -421,11 +421,11 @@ 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
<li><strong>Comment or make a suggestion on IOCCC rules</strong> - See our
FAQ on “<a href="faq.html#feedback">rules feedback</a>”</li>
<li><strong>Comment or make a suggestion on IOCCC guidelines</strong> - See
<li><strong>Comment or make a suggestion on IOCCC guidelines</strong> - See our
FAQ on “<a href="faq.html#feedback">guidelines feedback</a>”</li>
<li><strong>Comment or make a suggestion on IOCCC tools</strong> - See
<li><strong>Comment or make a suggestion on IOCCC tools</strong> - See our
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
@@ -437,7 +437,7 @@ 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
<p>See the
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>