Update "Running a Local Development Environment" Tutorial

pages/app-developers/building-apps.mdx

@@ -61,7 +61,7 @@ Not only is it faster, but such EVMs often have extra features, such as the [abi
 
 ### Debug before deploying
 
-After you are done with that development, debug your decentralized application using either a [development network](/stack/dev-net) or a [Sepolia test network](/superchain/networks).
+After you are done with that development, debug your decentralized application using either a [development network](/operators/chain-operators/tutorials/chain-dev-net) or a [Sepolia test network](/superchain/networks).
 This lets you debug parts that are OP Stack chains specific such as calls to bridges to transfer ETH or tokens between layers.
 
 Only when you have a version that works well on a test network should you deploy to the production network, where every transaction has a cost.

pages/operators/chain-operators/tutorials/chain-dev-net.mdx

@@ -144,9 +144,6 @@ af4abdbbe939   op-el-1-op-geth-op-node-rollup-1                 engine-rpc: 8551
 aa69f73e96c1   vc-1-geth-lighthouse                             metrics: 8080/tcp -> http://127.0.0.1:33642   RUNNING
 ```
 
-Also take note of the last log line above this message, which contains the address of the standard bridge. You'll
-need this address to deposit funds on your L2.
-
 This might look complicated, but it's just a list of the services that were started up by Kurtosis. For each service, you
 can see:
 
@@ -157,37 +154,63 @@ can see:
 
 At this point your chain is up and running. Let's move on to the next section to learn how to interact with it.
 
+<Callout type="info">
+  You can also use the Kurtosis Web UI to monitor and interact with your services by running:
+  ```bash
+  kurtosis web
+  ```
+  This will open a browser window with a dashboard showing all your running enclaves and services.
+</Callout>
+
 ## Interact with your network
 
 You now have a fully functioning OP Stack Rollup. You can connect your wallet to this chain the same way you'd connect
 your wallet to any other EVM chain. You can find your node's RPC URL by running `kurtosis enclave inspect <enclave name>`.
 Your enclave name is outputted at the end of the `kurtosis run` command above. The RPC url is the `rpc` port name in any
 of the execution client services identified by `op-el`.
 
-### Depositing funds onto your network
+### Using pre-funded accounts on L2
+
+<Callout type="info">
+  Important: The setup script automatically pre-funds accounts on the L2 chain directly. You don't need to bridge funds from L1 to L2 to get started.
+</Callout>
 
-Your network was configured to pre-fund development addresses using the `test test test test test test test test test test test junk`
-mnemonic. To get ETH onto your L2, you import one of the private keys from that mnemonic into your favorite wallet or use
+Your network is configured to pre-fund development addresses on L2 using the `test test test test test test test test test test test junk`
+mnemonic. You can import one of the private keys from that mnemonic into your favorite wallet or use
 a CLI tool like `cast`. For the purposes of this tutorial, we'll use `cast` and assume you want to use the first address
 generated by that mnemonic.
 
-To move ETH onto your L2, run the following command. Make sure to replace the values in angle brackets with real values:
+First, check your L2 balance to confirm you have funds:
 
 ```bash
-cast send --mnemonic 'test test test test test test test test test test test junk' --mnemonic-path "m/44'/60'/0'/0/0" \
-    --to "<standard bridge address>" --amount "<amount in ETH>eth" --rpc-url "http://127.0.0.1:<rpc port of el-1-geth-lighthouse service>"
+# Find your L2 node's RPC port
+# Look for a service starting with "op-el" (like op-el-1-op-geth-op-node-rollup-1) and note its RPC port
+# For example: rpc: 8545/tcp -> http://127.0.0.1:33643
+
+# Check your balance on L2
+export ADDRESS="0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266"  # First address from the test mnemonic
+export L2_RPC_URL="http://127.0.0.1:<L2-RPC-PORT>"  # Replace with your actual L2 RPC port
+cast balance "$ADDRESS" --rpc-url "$L2_RPC_URL"
 ```
 
-Wait \~30 seconds, then check your balance on L2 by running the following command:
+You should see that this account already has ETH on L2.
+
+### Interacting with your L2
+
+Now that you've confirmed you have funds on L2, you can start using them to interact with your rollup:
 
 ```bash
-export ETH_RPC_URL="http://127.0.0.1:<rpc port of el-1-geth-lighthouse service>"
-export ADDRESS="0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266"
-cast balance "$ADDRESS"
+# Example: Sending a transaction on L2
+cast send --mnemonic 'test test test test test test test test test test test junk' \
+    <RECIPIENT-ADDRESS> \
+    --value 0.01ether --rpc-url "$L2_RPC_URL"
+
+# Example: Deploying a contract on L2 (if you have Foundry installed)
+# forge create --rpc-url "$L2_RPC_URL" \
+#     --private-key 0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80 \
+#     <CONTRACT-NAME>
 ```
 
-Your balance should match the amount you sent.
-
 ## See Your Rollup in Action
 
 You can interact with your Rollup the same way you'd interact with any other EVM chain.
@@ -196,5 +219,5 @@ Send some transactions, deploy some contracts, and see what happens!
 ## Next Steps
 
 *   Check out the [protocol specs](https://specs.optimism.io/) for more detail about the rollup protocol.
-*   If you run into any problems, please visit the [Chain Operators Troubleshooting Guide](/operators/chain-operators/management/troubleshooting)
-    or [file an issue](https://github.com/ethereum-optimism/optimism/issues) for help.
+*   If you run into any problems, please visit the [chain operators troubleshooting guide](/operators/chain-operators/management/troubleshooting)
+*   If you run into any problems, please [file an issue](https://github.com/ethereum-optimism/optimism/issues) or join the [Optimism Discord](https://discord.optimism.io/) for help.

public/_redirects

@@ -78,7 +78,8 @@
 /builders/node-operators/network-upgrades/*       /operators/node-operators/network-upgrades
 /builders/node-operators/*                        /operators/node-operators/:splat
 /operators/node-operators/tutorials/mainnet        /operators/node-operators/tutorials/run-node-from-source
-/operators/node-operators/tutorials/testnet        /operators/node-operators/tutorials/run-node-from-source
+/operators/node-operators/tutorials/testnet        /operators/node-operators/tutorials/run-node-from-source 
+/stack/dev-net                                     /chain-operators/tutorials/chain-dev-net
 
 # ----------------------------------------------------------------------------
 # Stack Documentation Migration

words.txt

@@ -115,7 +115,6 @@ ETHERBASE
 etherbase
 Ethernity
 Ethernow
-ethpandaops
 ETHSTATS
 ethstats
 EVMTIMEOUT
@@ -264,7 +263,6 @@ offchain
 opchaina
 opchainb
 OPCM
-opcm
 Openfort
 oplabs
 opnode's