improve FAQ on What platform should I assume for my entry

Added `faq.html#SUS` link.

Ran `make gen_top_html` to perform the above.

faq.html

@@ -435,15 +435,14 @@ For example:</p>
             rm -f $@
             cp -f prog $@</code></pre>
 <div id="faq0_4">
+<div id="SUS">
 <h3 id="faq-0.4-what-platform-should-i-assume-for-my-entry">FAQ 0.4: What platform should I assume for my entry?</h3>
 </div>
-<p>Your entry must compile with GCC and run under at least one flavor of UNIX (e.g.
+</div>
-Linux or Solaris). To improve chances to win, it should work under both BSD and
+<p>Your entry must compile with <strong>clang</strong> or <strong>gcc</strong> and run under at least one flavor of a UNIX
-SysV style UNIX (think <strong>stty cbreak</strong>), and should not depend on “Endianness”.
+system that conforms to the <a href="https://en.wikipedia.org/wiki/Single_UNIX_Specification">SUS</a>,
-If it can compile and run on Windows and/or Mac (see
+otherwise known as the <a href="https://unix.org/version4/">The Single UNIX Specification Version 4</a>
-<a href="2000/thadgavin/index.html">2000/thadgavin</a> for one example, amongst others),
+or <a href="https://unix.org/online.html">later SUS</a>.</p>
-even better. Being able to compile with other compilers like clang is also a
-good thing.</p>
 <div id="faq0_5">
 <div id="feedback">
 <h3 id="faq-0.5-how-may-i-comment-or-make-a-suggestion-on-ioccc-rules-guidelines-and-tools">FAQ 0.5: How may I comment or make a suggestion on IOCCC rules, guidelines and tools?</h3>

faq.md

@@ -386,16 +386,15 @@ For example:
 
 
 <div id="faq0_4">
+<div id="SUS">
 ### FAQ 0.4: What platform should I assume for my entry?
 </div>
+</div>
 
-Your entry must compile with GCC and run under at least one flavor of UNIX (e.g.
+Your entry must compile with **clang** or **gcc** and run under at least one flavor of a UNIX
-Linux or Solaris). To improve chances to win, it should work under both BSD and
+system that conforms to the [SUS](https://en.wikipedia.org/wiki/Single_UNIX_Specification),
-SysV style UNIX (think **stty cbreak**), and should not depend on "Endianness".
+otherwise known as the [The Single UNIX Specification Version 4](https://unix.org/version4/)
-If it can compile and run on Windows and/or Mac  (see
+or [later SUS](https://unix.org/online.html).
-[2000/thadgavin](2000/thadgavin/index.html) for one example, amongst others),
-even better. Being able to compile with other compilers like clang is also a
-good thing.
 
 
 <div id="faq0_5">