Deployed 3625d2f to dev with MkDocs 1.6.0 and mike 2.1.0

dev/repo-guides/release-nnf-sw/readme/index.html

@@ -1214,7 +1214,7 @@ <h2 id="release-nearnodeflashgithubio">Release <code>NearNodeFlash.github.io</co
 <p><strong>Please review and update the documentation for changes you may have made.</strong></p>
 <p>After nnf-deploy has a release tag, you may release the documentation. Use the same steps found above in "Release Each Component". Note that the default branch for this repo is "main" instead of "master".</p>
 <p>Give this release a tag that matches the nnf-deploy release, to show that they go together. Create the release by using the "Create release" or "Draft a new release" button in the GUI, or by using the <code>gh release create</code> CLI command. Whether using the GUI or the CLI, mark the release as "latest" and select the appropriate option to generate release notes.</p>
-<p>Wait for the <code>mike</code> tool in .github/workflow/release.yaml to finish building the new doc. You can check its status by going to the <code>gh-pages</code> branch in the repo. When you visit the release at <a href="https://nearnodeflash.github.io">https://nearnodeflash.github.io</a> you should see the new release in the drop-down menu and the new release should be the default display.</p>
+<p>Wait for the <code>mike</code> tool in <code>.github/workflow/release.yaml</code> to finish building the new doc. You can check its status by going to the <code>gh-pages</code> branch in the repo. When you visit the release at <a href="https://nearnodeflash.github.io">https://nearnodeflash.github.io</a>, you should see the new release in the drop-down menu and the new release should be the default display.</p>
 <p><strong>The software is now released!</strong></p>
 <h2 id="clone-a-release">Clone a release</h2>
 <p>The follow commands clone release <code>v0.0.7</code> into <code>nnf-deploy-v0.0.7</code></p>