diff --git a/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx b/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx
index c4118bc68..5dd5f0d12 100644
--- a/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx
+++ b/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx
@@ -422,8 +422,14 @@ Once you've configured your network, it's time to deploy the L1 contracts necess
 The `op-deployer` tool simplifies the creation of genesis and rollup configuration files (`genesis.json` and `rollup.json`).
 These files are crucial for initializing the execution client (`op-geth`) and consensus client (`op-node`) for your network.
 
+```bash
+
+forge script scripts/deploy/Deploy.s.sol:Deploy --private-key $GS_ADMIN_PRIVATE_KEY --broadcast --rpc-url $L1_RPC_URL --slow
+
+```
 The recommended flow for creating a genesis file and rollup configuration file on the OP Stack is as follows:
 
+
 1.  **Deploy the L1 contracts** using [op-deployer](/operators/chain-operators/tools/op-deployer).
 2.  **Generate** both the L2 genesis file (`genesis.json`) and the rollup configuration file (`rollup.json`) using op-deployer's `inspect` commands.
 3.  **Initialize** your off-chain components (e.g., execution client, consensus client).