Deployed ee6fef0 to develop with MkDocs 1.6.1 and mike 2.1.3

develop/security/index.html

@@ -1079,16 +1079,16 @@ <h2 id="supported-versions">Supported Versions</h2>
 will be updated at that time.</p>
 <p>Note: with the v2.x release, v1.x is no longer supported.</p>
 <h2 id="code-signing">Code signing</h2>
-<p>All commits by me are signed by my <a href="../commit-sign-key.asc/">commit signing GPG key</a>.</p>
+<p>All commits by me are signed by my <a href="/docs/commit-sign-key.asc.md">commit signing GPG key</a>.</p>
 <h2 id="binary-signatures">Binary signatures</h2>
-<p>All releases have a corresponding detactched GPG signature using my <a href="../code-sign-key.asc/">code signing GPG key</a>.</p>
+<p>All releases have a corresponding detactched GPG signature using my <a href="/docs/code-sign-key.asc.md">code signing GPG key</a>.</p>
 <h2 id="reporting-a-vulnerability">Reporting a Vulnerability</h2>
 <h2 id="reporting-a-vulnerability_1">Reporting a Vulnerability</h2>
 <p>Please open a <a href="https://github.com/synfinatic/aws-sso-cli/issues/new?assignees=&amp;labels=security&amp;projects=&amp;template=bug_report.md&amp;title=">security ticket in GitHub</a>.
 If you believe the public visibility of the information of the bug would
 place other <code>aws-sso</code> users at risk, then you may email me at:
 <code>[email protected]</code>.  GPG encrypting your email in those situations is
-encouraged and you should use <a href="../commit-sign-key.asc/">this GPG Key</a>.</p>
+encouraged and you should use <a href="/docs/commit-sign-key.asc.md">this GPG Key</a>.</p>
 <h2 id="security-model">Security Model</h2>
 <p><code>aws-sso</code> relies on <a href="https://github.com/99designs/keyring">99designs/keyring</a>
 to store and retrieve secrets in 3rd party secure key stores which are