Community — Scroll brings together users and builders.
- We know the challenges of building in the open and getting user engagement before mainnet release! Scroll has a
- blossoming community of users and builders, and with a Discord community of over 100,000 users eager to try out
- applications on our testnet, we’re excited to connect builders with users that can provide real-world feedback.
+ We know the challenges of building in the open and getting user engagement! Scroll has a blossoming community of
+ users and builders, and with a Discord community of over 500,000 members eager to try out applications on our
+ testnet or mainnet, we’re excited to connect builders with users that can provide real-world feedback.
diff --git a/src/content/docs/en/developers/l1-and-l2-bridging/the-scroll-messenger.mdx b/src/content/docs/en/developers/l1-and-l2-bridging/the-scroll-messenger.mdx
index 10ee9b867..fb21fb219 100644
--- a/src/content/docs/en/developers/l1-and-l2-bridging/the-scroll-messenger.mdx
+++ b/src/content/docs/en/developers/l1-and-l2-bridging/the-scroll-messenger.mdx
@@ -24,11 +24,15 @@ the messenger smart contract deployed on L1, `L1ScrollMessenger`. To send a mess
## Finalizing transactions on L1
Any upcoming transactions from L2 need to be finalized using the `relayMessageWithProof` function on the Scroll Messenger
-contract. We call this process "submitting an Execute Withdrawal transaction," and it is required for both sending arbitrary messages and transferring assets through a gateway or the router. When you use `relayMessageWithProof`, you'll have to provide a Merkle inclusion proof showing your transaction is included in the trie of "withdrawal" messages, along with other parameters. Producing this proof and these values can be done locally and permissionlessly, but at the moment, the easiest way to retrieve these parameters is through our backend API hosted at https://sepolia-api-bridge.scroll.io/api/.
+contract. We call this process "submitting an Execute Withdrawal transaction," and it is required for both sending arbitrary messages and transferring assets through a gateway or the router. When you use `relayMessageWithProof`, you'll have to provide a Merkle inclusion proof showing your transaction is included in the trie of "withdrawal" messages, along with other parameters. Producing this proof and these values can be done locally and permissionlessly, but at the moment, the easiest way to retrieve these parameters is through our backend APIs:
+
+- Scroll Sepolia API: https://sepolia-api-bridge.scroll.io/api/
+- Scroll API: https://mainnet-api-bridge.scroll.io/api/