Node 9.1.0 & CNTools major bump

upgrade/index.html

@@ -1044,7 +1044,7 @@ <h3 id="steps-for-upgrading">Steps for Upgrading<a class="headerlink" href="#ste
 </ul>
 <div class="admonition warning">
 <p class="admonition-title">Beware</p>
-<p>When upgrading node, depending on node versions (especially for major release) - you'd likely have to wait for node to revalidate/replay ledger. This can take a few hours. Please always plan ahead, do it first on a relay to ensure you've got "${CNODE_HOME}/db" folder ready to copy over (while source and target node have been shutdown) - prior to starting on upgrade on new machine. If mithril for target node version is ready, you can also use <a href="../Scripts/mithril-client.md">mithril-client</a> to download snapshot instead of replaying, which may save you some time</p>
+<p>When upgrading node, depending on node versions (especially for major release) - you'd likely have to wait for node to revalidate/replay ledger. This can take a few hours. Please always plan ahead, do it first on a relay to ensure you've got "${CNODE_HOME}/db" folder ready to copy over (while source and target node have been shutdown) - prior to starting on upgrade on new machine. If mithril for target node version is ready, you can also use <a href="../Scripts/mithril-client/">mithril-client</a> to download snapshot instead of replaying, which may save you some time</p>
 </div>
 <ul>
 <li>Once guild-deploy script has been run, source your bashrc file again (or restart session), and ensure <code>"${HOME}"/.local/bin</code> is part of your <span HOME="HOME" class="arithmatex">\(PATH environment variable. If your shell does not auto-run bashrc, you may want to set it a call to "\)</span>"/.bashrc in your <code>.profile</code></li>