diff --git a/docs/pages/concepts/onboarding-faqs/index.mdx b/docs/pages/concepts/onboarding-faqs/index.mdx
index f423fcf90..8c10bd455 100644
--- a/docs/pages/concepts/onboarding-faqs/index.mdx
+++ b/docs/pages/concepts/onboarding-faqs/index.mdx
@@ -259,7 +259,7 @@
 
 - Expected order → trade latency would be:
   - Time for order to get from the node it was submitted to, to the proposer, so location dependent.
-  - Order match -> trade, probably at least 1 block so ~1.1s, could be more than 1 block.
+  - Order match -> trade, probably at least 1 block so ~0.8s, could be more than 1 block.
 
 </details>
 
@@ -347,7 +347,7 @@
 <details>
 <summary>1. How will trading rewards work on dYdX Chain?</summary>
 
-- Trading rewards are not controlled by dYdX. dYdX recommends that trading rewards could be calculated primarily based on total taker fees paid, along with a few other variables. The full proposed formula can be found [here](/concepts/trading/rewards). These rewards could be distributed on a block by block basis (1-2 seconds).
+- Trading rewards are not controlled by dYdX. dYdX recommends that trading rewards could be calculated primarily based on total taker fees paid, along with a few other variables. The full proposed formula can be found [here](/concepts/trading/rewards),
 
 </details>
 
diff --git a/docs/pages/repositories.mdx b/docs/pages/repositories.mdx
index 29649c420..eab0b599f 100644
--- a/docs/pages/repositories.mdx
+++ b/docs/pages/repositories.mdx
@@ -10,6 +10,8 @@ Please find the open source repositories on our [GitHub](https://github.com/dydx
 * [iOS](https://github.com/dydxprotocol/v4-native-ios)
 * [Android](https://github.com/dydxprotocol/v4-native-android)
 * [Terraform](https://github.com/dydxprotocol/v4-infrastructure)
+* [dYdX Technical Docs](https://github.com/dydxprotocol/v4-documentation)
+* [Pocket protector TG bot docs](https://docs.pocketprotector.xyz/)
 
 When contributing, please ensure your commits are verified. You can follow these steps to do so:
 * [Generate a new signing key](https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key) for work use and [turn on Vigilant Mode](https://docs.github.com/en/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits)