Merge branch 'nebari-dev:develop' into eks-cluster-encryption

CONTRIBUTING.md

@@ -30,4 +30,4 @@ This [blog post by Matthew Rocklin](https://matthewrocklin.com/blog/work/2018/02
 
 [nebari-docs-issues]: https://github.com/nebari-dev/nebari-docs/issues
 [nebari-issues]: https://github.com/nebari-dev/nebari/issues
-[nebari-community]: https://nebari.dev/docs/community
+[nebari-community]: https://www.nebari.dev/community/introduction

README.md

@@ -181,5 +181,5 @@ If you're using Nebari and would like professional support, please get in touch
 [nebari-issues]: https://github.com/nebari-dev/nebari/issues
 [nebari-faqs]: https://www.nebari.dev/docs/faq
 [gh-discussions]: https://github.com/nebari-dev/nebari/discussions
-[docs-get-started]: https://www.nebari.dev/docs/category/get-started
+[docs-get-started]: https://www.nebari.dev/docs/get-started
 [docs-deploy]: https://www.nebari.dev/docs/get-started/deploy

SECURITY.md

@@ -8,4 +8,4 @@ You should feel comfortable upgrading if you're using our documented public APIs
 
 ## Reporting a Vulnerability
 
-If you think you found a vulnerability, please report it at [nebari/security](https://github.com/nebari-dev/nebari/security/new). Please do not report security vulnerabilities on our public issue tracker. Exposing vulnerabilities publicly without giving maintainers a chance to release a fix puts users at risk.
+If you think you found a vulnerability, please report it at [nebari/security](https://github.com/nebari-dev/nebari/security/advisories/new). Please do not report security vulnerabilities on our public issue tracker. Exposing vulnerabilities publicly without giving maintainers a chance to release a fix puts users at risk.