diff --git a/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx b/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx
index 70a9b35f8..eb41c7ec6 100644
--- a/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx
+++ b/src/content/docs/en/developers/guides/bridge-erc20-through-the-custom-gateway.mdx
@@ -342,8 +342,8 @@ Now let’s switch to the Scroll chain and initialize `MyL2Gateway`, following s
 First, call the `initialize` function from `MyL2Gateway`:
 
 - `_counterpart`: The address of `MyL1Gateway` we just launched on Sepolia.
-- `_router`: Set it to `0x9aD3c5617eCAa556d6E166787A97081907171230`, the `L2GatewayRouter` contract on Scroll.
-- `_messenger`: Set it `0xBa50f5340FB9F3Bd074bD638c9BE13eCB36E603d`, the `L2ScrollMessenger` contract on Scroll.
+- `_router`: Set it to `0x4C0926FF5252A435FD19e10ED15e5a249Ba19d79`, the `L2GatewayRouter` contract on Scroll.
+- `_messenger`: Set it `0x781e90f1c8Fc4611c9b7497C3B47F99Ef6969CbC`, the `L2ScrollMessenger` contract on Scroll.
 
 Next, call `updateTokenMapping` on the `MyL2Gateway` contract:
 
diff --git a/src/content/docs/en/developers/guides/scroll-messenger-cross-chain-interaction.mdx b/src/content/docs/en/developers/guides/scroll-messenger-cross-chain-interaction.mdx
index 15d26035e..8a276a748 100644
--- a/src/content/docs/en/developers/guides/scroll-messenger-cross-chain-interaction.mdx
+++ b/src/content/docs/en/developers/guides/scroll-messenger-cross-chain-interaction.mdx
@@ -79,12 +79,12 @@ contract GreeterOperator {
 We pass the message by executing `executeFunctionCrosschain` and passing the following parameters:
 
 - `scrollMessengerAddress`: This will depend on where you deployed the `GreeterOperator` contract.
-  - If you deployed it on Sepolia use `0x50c7d3e7f7c656493D1D76aaa1a836CedfCBB16A`. If you deployed on Scroll use `0xBa50f5340FB9F3Bd074bD638c9BE13eCB36E603d`.
+  - If you deployed it on Sepolia use `0x50c7d3e7f7c656493D1D76aaa1a836CedfCBB16A`. If you deployed on Scroll use `0x781e90f1c8Fc4611c9b7497C3B47F99Ef6969CbC`.
 - `targetAddress`: The address of the `Greeter` contract on the opposite chain.
 - `value`: In this case, it is `0` because the `setGreeting`is not payable.
 - `greeting`: This is the parameter that will be sent through the message. Try passing `“This message was crosschain!”`
 - `gasLimit`:
-  - If you are sending the message from L1 to L2, around `5000` gas limit should be more than enough.
+  - If you are sending the message from L1 to L2, around `1000000` gas limit should be more than enough.
   - If you are sending the message from L2 to L1, pass `0`, as the transaction be completed by executing an additional transaction on L1.
 
 ### Relay the Message when sending from L2 to L1
diff --git a/src/content/docs/es/developers/guides/bridge-erc20-through-the-custom-gateway.mdx b/src/content/docs/es/developers/guides/bridge-erc20-through-the-custom-gateway.mdx
index 154103898..e459343ad 100644
--- a/src/content/docs/es/developers/guides/bridge-erc20-through-the-custom-gateway.mdx
+++ b/src/content/docs/es/developers/guides/bridge-erc20-through-the-custom-gateway.mdx
@@ -341,8 +341,8 @@ Ahora cambiemos a la cadena Scroll e inicialicemos `MyL2Gateway`, siguiendo paso
 Primero, llama a la función `initialize` de `MyL2Gateway`:
 
 - `_counterpart`: La dirección de `MyL1Gateway` que acabamos de lanzar en Sepolia.
-- `_router`: Coloca `0x9aD3c5617eCAa556d6E166787A97081907171230`, el contrato `L2GatewayRouter` de Scroll.
-- `_messenger`: Coloca `0xBa50f5340FB9F3Bd074bD638c9BE13eCB36E603d`, el contrato `L2ScrollMessenger` de Scroll.
+- `_router`: Coloca `0x4C0926FF5252A435FD19e10ED15e5a249Ba19d79`, el contrato `L2GatewayRouter` de Scroll.
+- `_messenger`: Coloca `0x781e90f1c8Fc4611c9b7497C3B47F99Ef6969CbC`, el contrato `L2ScrollMessenger` de Scroll.
 
 A continuación, llama a `updateTokenMapping` en el contrato `MyL2Gateway`:
 
diff --git a/src/content/docs/es/developers/guides/scroll-messenger-cross-chain-interaction.mdx b/src/content/docs/es/developers/guides/scroll-messenger-cross-chain-interaction.mdx
index fa0c65f71..02af805cd 100644
--- a/src/content/docs/es/developers/guides/scroll-messenger-cross-chain-interaction.mdx
+++ b/src/content/docs/es/developers/guides/scroll-messenger-cross-chain-interaction.mdx
@@ -78,12 +78,12 @@ contract GreeterOperator {
 Pasamos el mensaje ejecutando `executeFunctionCrosschain` y pasando los siguientes parámetros:
 
 - `scrollMessengerAddress`: Esto dependerá de dónde hayas desplegado el contrato `GreeterOperator`.
-  - Si lo desplegaste en Sepolia utiliza `0x50c7d3e7f7c656493D1D76aaa1a836CedfCBB16A`. Si lo has desplegado en Scroll utiliza `0xBa50f5340FB9F3Bd074bD638c9BE13eCB36E603d`.
+  - Si lo desplegaste en Sepolia utiliza `0x50c7d3e7f7c656493D1D76aaa1a836CedfCBB16A`. Si lo has desplegado en Scroll utiliza `0x781e90f1c8Fc4611c9b7497C3B47F99Ef6969CbC`.
 - `targetAddress`: La dirección del contrato `Greeter` en la cadena opuesta.
 - `value`: En este caso es `0` porque el `setGreeting` no es de tipo `payable`.
 - `greeting`: Es el parámetro que se enviará a través del mensaje. Prueba pasar `"¡Este mensaje fue ejecutado de manera crosschain!"`.
 - `gasLimit`:
-  - Si estás enviando el mensaje de L1 a L2, alrededor de un límite de gas de `5000` debería ser más que suficiente.
+  - Si estás enviando el mensaje de L1 a L2, alrededor de un límite de gas de `1000000` debería ser más que suficiente.
   - Si estás enviando el mensaje de L2 a L1, pasa `0`, ya que la transacción se completará ejecutando una transacción adicional en L1.
 
 ### Retransmisión del mensaje al enviar de L2 a L1