diff --git a/docusaurus.config.js b/docusaurus.config.js
index bb338a0a..7e26f814 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -117,6 +117,10 @@ const config = {
                 label: 'Introduction',
                 to: '/docs/intro',
               },
+				{
+				  to: '/security/intro',
+				  label: 'Security Handbook',
+				},
             ],
           },
           {
diff --git a/security/development.md b/security/development.md
index dab47d30..7838e276 100644
--- a/security/development.md
+++ b/security/development.md
@@ -35,6 +35,6 @@ Our automated pipelines have the ability to catch regressions when that
  behaviour is detectable.
  
 The greatest challenge is in defining how such regressions are detected for the
-[ui](./ui.md) - where behaviour isn't as strictly defined as it is for the
+[ui](/security/category/cwtch-ui) - where behaviour isn't as strictly defined as it is for the
  individual libraries.
  
\ No newline at end of file
diff --git a/security/intro.md b/security/intro.md
index 0f29d132..fcab0df7 100644
--- a/security/intro.md
+++ b/security/intro.md
@@ -47,7 +47,7 @@ messages while a contact is offline.
 
 This made adoption of Ricochet a difficult proposition; with even those in
 environments that would be served best by metadata resistance unaware that it
-exists [[ermoshina2017can]](www.academia.edu/download/53192589/ermoshina-12.pdf)
+exists [[ermoshina2017can]](https://www.academia.edu/download/53192589/ermoshina-12.pdf)
 [[renaud2014doesn]](https://eprints.gla.ac.uk/116203/1/116203.pdf).
 
 Additionally, any solution to decentralized, metadata resistant communication faces [fundamental problems](https://code.briarproject.org/briar/briar/-/wikis/Fundamental-Problems)