repo links

README.md

@@ -10,12 +10,12 @@ documentation for the open source projects that Hypermode leads:
 
 - [Modus](https://github.com/hypermodeinc/modus) - serverless framework for
   building functions and APIs, powered by WebAssembly
-- [Dgraph](https://github.com/dgraph-io/dgraph) - distributed, transactional
+- [Dgraph](https://github.com/hypermodeinc/dgraph) - distributed, transactional
   graph database for real-time use cases
-- [Badger](https://github.com/dgraph-io/badger) - embeddable key-value store in
-  Go
-- [Ristretto](https://github.com/dgraph-io/ristretto) - embeddable memory-bound
-  cache in Go
+- [Badger](https://github.com/hypermodeinc/badger) - embeddable key-value store
+  in Go
+- [Ristretto](https://github.com/hypermodeinc/ristretto) - embeddable
+  memory-bound cache in Go
 
 ## Found an issue?
 

badger/overview.mdx

@@ -15,5 +15,5 @@ non-Go-based key-value stores like RocksDB.
 ## Changelog
 
 We keep the
-[repo Changelog](https://github.com/dgraph-io/badger/blob/main/CHANGELOG.md) up
-to date with each release.
+[repo Changelog](https://github.com/hypermodeinc/badger/blob/main/CHANGELOG.md)
+up to date with each release.

badger/troubleshooting.mdx

@@ -17,8 +17,9 @@ acquire read locks over the value log files to avoid value log GC removing the
 file from underneath. As a side effect, this also blocks a new value log GC file
 from being created, when the value log file boundary is hit.
 
-Please see GitHub issues [#293](https://github.com/dgraph-io/badger/issues/293)
-and [#315](https://github.com/dgraph-io/badger/issues/315).
+Please see GitHub issues
+[#293](https://github.com/hypermodeinc/badger/issues/293) and
+[#315](https://github.com/hypermodeinc/badger/issues/315).
 
 There are multiple workarounds during iteration:
 
@@ -70,8 +71,8 @@ the SEEK key, reverse iteration goes to the first key which is equal or lesser
 than the SEEK key. Therefore, SEEK key would not be part of the results. You can
 typically add a `0xff` byte as a suffix to the SEEK key to include it in the
 results. See the following issues:
-[#436](https://github.com/dgraph-io/badger/issues/436) and
-[#347](https://github.com/dgraph-io/badger/issues/347).
+[#436](https://github.com/hypermodeinc/badger/issues/436) and
+[#347](https://github.com/hypermodeinc/badger/issues/347).
 
 ## Which instances should I use for Badger?
 
@@ -152,8 +153,8 @@ running `CGO_ENABLED=0 go build`. This builds Badger without the support for
 ZSTD compression algorithm.
 
 As of Badger versions
-[v2.2007.4](https://github.com/dgraph-io/badger/releases/tag/v2.2007.4) and
-[v3.2103.1](https://github.com/dgraph-io/badger/releases/tag/v3.2103.1) the
+[v2.2007.4](https://github.com/hypermodeinc/badger/releases/tag/v2.2007.4) and
+[v3.2103.1](https://github.com/hypermodeinc/badger/releases/tag/v3.2103.1) the
 DataDog ZSTD library was replaced by pure Golang version and Cgo is no longer
 required. The new library is
 [backwards compatible in nearly all cases](https://discuss.dgraph.io/t/use-pure-go-zstd-implementation/8670/10):

community-and-support.mdx

@@ -19,7 +19,7 @@ relevant GitHub repository:
 
 - [Modus](https://github.com/hypermodeinc/modus/issues)
 - [Hyp CLI](https://github.com/hypermodeinc/hyp-cli/issues)
-- [Badger](https://github.com/dgraph-io/badger/issues)
+- [Badger](https://github.com/hypermodeinc/badger/issues)
 
 All paid Hypermode packages include commercial support. Customers can reach out
 via the Hypermode Console or through email at