diff --git a/bin/README.md b/bin/README.md
index 08079b99b..b16d3ccdb 100644
--- a/bin/README.md
+++ b/bin/README.md
@@ -103,7 +103,7 @@ If this tool claims that a file is missing that does exist,
 look for a malformed markdown line and/or use of markdown
 that is **NOT** an IOCCC markdown best practice.
 
-See [IOCCC markdown best practices](markdown.html) for more info.
+See [IOCCC markdown best practices](../markdown.html) for more info.
 
 
 ### [gen-authors.sh](%%DOCROOT_SLASH%%bin/gen-authors.sh)
@@ -757,7 +757,7 @@ on the [experimental web site](https://ioccc-src.github.io/temp-test-ioccc/).
 
 Instead of editing the default HTML files in order to fix a special web page,
 consider making a copy of the default file and modifying the [md2html config
-file](md2html.cfg) to refer to the copy instead.  That way your special case
+file](%%DOCROOT_SLASH%%inc/md2html.cfg) to refer to the copy instead.  That way your special case
 situation will not impact **MOST** of the HTML content.
 
 
diff --git a/bin/index.html b/bin/index.html
index 148a5f532..75126b4be 100644
--- a/bin/index.html
+++ b/bin/index.html
@@ -426,7 +426,7 @@ might generate an error about a file that does exist.
 If this tool claims that a file is missing that does exist,
 look for a malformed markdown line and/or use of markdown
 that is <strong>NOT</strong> an IOCCC markdown best practice.</p>
-<p>See <a href="markdown.html">IOCCC markdown best practices</a> for more info.</p>
+<p>See <a href="../markdown.html">IOCCC markdown best practices</a> for more info.</p>
 <h3 id="gen-authors.sh"><a href="../bin/gen-authors.sh">gen-authors.sh</a></h3>
 <p>Generate the top level <code>/authors.html</code> page.</p>
 <p>Usage:</p>
@@ -752,7 +752,7 @@ on the <a href="https://ioccc-src.github.io/temp-test-ioccc/">experimental web s
 <pre><code>    *.default.html</code></pre>
 <p>… contain default content used to form IOCCC HTML / IOCCC web pages.</p>
 <p>Instead of editing the default HTML files in order to fix a special web page,
-consider making a copy of the default file and modifying the <a href="md2html.cfg">md2html config
+consider making a copy of the default file and modifying the <a href="../inc/md2html.cfg">md2html config
 file</a> to refer to the copy instead. That way your special case
 situation will not impact <strong>MOST</strong> of the HTML content.</p>
 <h1 id="why-we-do-not-use-certain-well-known-html-technologies">Why we do not use certain well-known HTML technologies</h1>