Add better link system for try / Makefile.example

The guidelines now link to both GitHub (viewing option) and directly to
the files Makefile.example, try.sh and try.alt.sh, as does the FAQ.

I made sure to keep the version of the guidelines and rules the same (as
in major.minor) but updated the date, as these changes are part of the
previous commit.

next/rules.html

@@ -466,7 +466,7 @@ writing by <a href="../contact.html">contacting the judges</a>.</p>
 </div>
 <p>Jump to: <a href="#">top</a></p>
 <p class="leftbar">
-These <a href="rules.html">IOCCC rules</a> are version <strong>28.12 2024-12-04</strong>.
+These <a href="rules.html">IOCCC rules</a> are version <strong>28.12 2024-12-05</strong>.
 </p>
 <p><strong>IMPORTANT</strong>: Be sure to read the <a href="guidelines.html">IOCCC guidelines</a>.</p>
 <p>Jump to: <a href="#">top</a></p>
@@ -905,7 +905,7 @@ those requirements.
 <p class="leftbar">
 The <code>Makefile</code> <strong>MUST</strong> be a <strong>non</strong>-empty file in <strong><a href="https://www.gnu.org/software/make/manual/make.html">GNU
 Makefile</a></strong> form. See the
-<a href="Makefile.example">Makefile.example</a>,
+<a href="guidelines.html#makefile">Makefile section in the guidelines</a>,
 the
 FAQ on “<a href="../faq.html#submission_makefiles">submission Makefile</a>”
 and the
@@ -1092,8 +1092,9 @@ make(1) compatibility the IOCCC
 supports</a> for more details.</p>
 <p class="leftbar">
 You are <strong>ENCOURAGED</strong> to use
-<a href="Makefile.example">Makefile.example</a>,
-renamed as <code>Makefile</code> of course, for help in constructing your <code>Makefile</code>.
+Makefile example, renamed as <code>Makefile</code> of course, for help in constructing your
+<code>Makefile</code>. See the <a href="guidelines.html#makefile">Makefile section</a> in the
+guidelines for more details.
 </p>
 <p>The target of the Makefile must be called <code>prog</code>. The original
 C source file must be called <code>prog.c</code>.</p>