diff --git a/app-developers/guides/bridging/messaging.mdx b/app-developers/guides/bridging/messaging.mdx
index 35317ea12..a4cb6251e 100644
--- a/app-developers/guides/bridging/messaging.mdx
+++ b/app-developers/guides/bridging/messaging.mdx
@@ -197,7 +197,7 @@ Each message from L2 to L1 requires three transactions:
 1.  An L2 transaction that *initiates* the transaction, which is priced the same as any other transaction made on OP Mainnet.
 
 2.  An L1 transaction that *proves* the transaction.
-    This transaction can only be submitted after L2 block, including your L2 transaction, is proposed on L1.
+    This transaction can only be submitted after the L2 block, including your L2 transaction, is proposed on L1.
     This transaction is expensive because it includes verifying a [Merkle trie](/connect/resources/glossary#merkle-patricia-trie) inclusion proof on L1.
 
 3.  An L1 transaction that *finalizes* the transaction.
diff --git a/app-developers/guides/bridging/standard-bridge.mdx b/app-developers/guides/bridging/standard-bridge.mdx
index 916a5c774..ae4ef4f29 100644
--- a/app-developers/guides/bridging/standard-bridge.mdx
+++ b/app-developers/guides/bridging/standard-bridge.mdx
@@ -68,7 +68,7 @@ After providing a sufficient allowance, the user calls the [`bridgeERC20To`](htt
     *   `address _to`: Address of the recipient of these tokens, usually the sender's address.
     *   `uint256 _amount`: Number of tokens to transfer.
     *   `uint32 _minGasLimit`: Gas to use to complete the transfer on the receiving side.
-    *   `bytes calldata _extraData`: Optional identify extra data.
+    *   `bytes calldata _extraData`: Optional identity extra data.
   
     <Info>
       Users can also trigger the [`bridgeERC20`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L168-L191) function instead of `bridgeERC20To` to avoid needing to specify the `address _to` parameter.
@@ -154,7 +154,7 @@ Unlike when bridging native tokens, users do not need to provide an approval to
     *   `address _to`: Address of the recipient of these tokens, usually the sender's address.
     *   `uint256 _amount`: Number of tokens to transfer.
     *   `uint32 _minGasLimit`: Gas to use to complete the transfer on the receiving side.
-    *   `bytes calldata _extraData`: Optional identify extra data.
+    *   `bytes calldata _extraData`: Optional identity extra data.
 
   </Step>
   
diff --git a/app-developers/guides/interoperability/get-started.mdx b/app-developers/guides/interoperability/get-started.mdx
index 88ff654f8..61b0e36a1 100644
--- a/app-developers/guides/interoperability/get-started.mdx
+++ b/app-developers/guides/interoperability/get-started.mdx
@@ -30,7 +30,7 @@ The SuperchainERC20 Starter Kit allows you to focus on what to deploy, not how t
 
 | Tool                                                                                       | Description                                                             |
 | ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------- |
-| [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) | One stop shop to grab testnet ETH for any Superchain network.           |
+| [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) | One-stop shop to grab testnet ETH for any Superchain network.           |
 | [Supersim](/interop/tools/supersim)                                                        | Local multi-chain testing environment for smart contracts.              |
 | [Super CLI](https://github.com/ethereum-optimism/super-cli)                                | Command-line tool for seamless multichain app deployment and testing.   |
 | [Superchain Relayer](https://github.com/ethereum-optimism/superchain-relayer)              | UI for monitoring and managing cross-chain transactions.                |