diff --git a/pages/interop/tutorials/deploy-superchain-erc20.mdx b/pages/interop/tutorials/deploy-superchain-erc20.mdx
index 4ce59b162..e7d031631 100644
--- a/pages/interop/tutorials/deploy-superchain-erc20.mdx
+++ b/pages/interop/tutorials/deploy-superchain-erc20.mdx
@@ -45,34 +45,36 @@ This requirement abstracts away the complexity of cross-chain validation.
Achieving this requires deterministic deployment methods. There are multiple ways to do this.
Here we will use the [SuperchainERC20 Starter Kit](/app-developers/starter-kit).
-### What you'll do
+
-* Use the [SuperchainERC20 Starter Kit](/app-developers/starter-kit) to deploy an `SuperchainERC20` token on the devnet.
+About this tutorial
-### What you'll learn
+**What you'll learn**
* How to deploy `SuperchainERC20` tokens on different chains at the same address.
-## Prerequisites
-
-Before starting this tutorial, ensure your development environment meets the following requirements:
-
-### Technical knowledge
+**Technical knowledge**
* Understanding of smart contract development
* Familiarity with blockchain concepts
-### Development environment
+**Development environment**
* Unix-like operating system (Linux, macOS, or WSL for Windows)
* Git for version control
-### Required tools
+**Required tools**
The tutorial uses these primary tools:
* Foundry: For sending transactions to blockchains.
+
+
+### What you'll do
+
+* Use the [SuperchainERC20 Starter Kit](/app-developers/starter-kit) to deploy an `SuperchainERC20` token on the devnet.
+
## Step by step explanation
@@ -83,7 +85,7 @@ The tutorial uses these primary tools:
### Prepare for deployment
The Starter Kit already deploys a `SuperchainERC20` token to [Supersim](/interop/tools/supersim).
- Here we will deploy it to the [Interop devnet](/interop/tools/devnet).
+ Here are the required changes to deploy it to the [Interop devnet](/interop/tools/devnet).
1. Edit `packages/contracts/foundry.toml` to add the RPC endpoints for the devnet (add the bottom two rows).
@@ -157,9 +159,10 @@ The tutorial uses these primary tools:
Sanity check
1. Set `TOKEN_ADDRESS` to the address where the token is deployed.
+ Your address will be different.
```sh
- TOKEN_ADDRESS=0x322f4aF25D370BE2A2C74eEFf0DD0d2AF2e7eD75
+ TOKEN_ADDRESS=
```
2. Set `PRIVATE_KEY` to the private key for the owner address.
@@ -169,7 +172,7 @@ The tutorial uses these primary tools:
```
3. Mint tokens for an address you control on both chains.
- The owner address is the easiest to use.
+ It is the easiest to use the owner address.
```sh
OWNER_ADDRESS=`cast wallet address --private-key $PRIVATE_KEY`
diff --git a/words.txt b/words.txt
index efac7610b..3c2e5f9f6 100644
--- a/words.txt
+++ b/words.txt
@@ -97,8 +97,6 @@ Devnet
devnet
Devnets
devnets
-Devs
-
direnv
DISABLETXPOOLGOSSIP
disabletxpoolgossip