chore: migrate docs to centralized docs repo

.github/PULL_REQUEST_TEMPLATE.md

@@ -8,8 +8,8 @@ Please explain the changes you made here.
 - [ ] For all _code_ changes, an entry added to the `CHANGELOG.md` file describing and linking to
       this PR
 - [ ] Tests added for new functionality, or regression tests for bug fixes added as applicable
-- [ ] For public APIs, new features, etc., PR on
-      [docs repo](https://github.com/dgraph-io/dgraph-docs) staged and linked here
+- [ ] For public APIs, new features, etc., PR on [docs repo](https://github.com/hypermodeinc/docs)
+      staged and linked here
 
 **Instructions**
 

README.md

@@ -273,6 +273,10 @@ Below is a list of known projects that use Badger:
   local metadata KV store implementation
 - [Goptivum](https://github.com/smegg99/Goptivum) - Goptivum is a better frontend and API for the
   Vulcan Optivum schedule program
+- [ActionManager](https://mftlabs.io/actionmanager) - A dynamic entity manager based on rjsf schema
+  and badger db
+- [MightyMap](https://github.com/thisisdevelopment/mightymap) - Mightymap: Conveys both robustness
+  and high capability, fitting for a powerful concurrent map.
 
 If you are using Badger in a project please send a pull request to add it to the list.
 

SECURITY.md

@@ -1,7 +1,7 @@
 # Reporting Security Concerns
 
-We take the security of Badger very seriously. If you believe you have found a security vulnerability
-in Badger, we encourage you to let us know right away.
+We take the security of Badger very seriously. If you believe you have found a security
+vulnerability in Badger, we encourage you to let us know right away.
 
 We will investigate all legitimate reports and do our best to quickly fix the problem. Please report
 any issues or vulnerabilities via GitHub Security Advisories instead of posting a public issue in