fix lint issues

Author: krofax

pages/builders/app-developers/bridging/standard-bridge.mdx

@@ -191,11 +191,11 @@ The Standard Bridge contracts can also be used to bridge ETH from Ethereum to OP
 The ETH bridging process is generally less complex than the ERC-20 bridging process.
 Users simply need to trigger and send ETH to the [`bridgeETH`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L143-L150) or [`bridgeETHTo`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L152-L166) functions on either blockchain.
 
-  <Callout>
-    Users can also deposit ETH from Ethereum to OP Mainnet by sending a basic ETH transfer from an EOA to the `L1StandardBridgeProxy`. 
-    This works because the `L1StandardBridgeProxy` contains a [`receive`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L119-L121) function.
-    You can find the mainnet and testnet addresses on the [Contract Addresses](/chain/addresses) page.
-  </Callout>
+<Callout>
+  Users can also deposit ETH from Ethereum to OP Mainnet by sending a basic ETH transfer from an EOA to the `L1StandardBridgeProxy`.
+  This works because the `L1StandardBridgeProxy` contains a [`receive`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L119-L121) function.
+  You can find the mainnet and testnet addresses on the [Contract Addresses](/chain/addresses) page.
+</Callout>
 
 ## Tutorials
 
@@ -221,18 +221,16 @@ You can easily find the bridged representation of a token for OP Mainnet on the
 If you want to find the bridged representation of a token for another chain, use the following steps.
 
 <Steps>
+  {<h3>Find the token you want to bridge</h3>}
 
-{<h3>Find the token you want to bridge</h3>}
+  The Superchain Token List is organized by the token's address and native blockchain.
+  [Search the token list](https://github.com/ethereum-optimism/ethereum-optimism.github.io/blob/master/optimism.tokenlist.json) for the token you want to bridge to confirm that it's included in the list.
+  Make sure that the chain ID in the entry matches the chain ID of the blockchain you're bridging from.
+  Retrieve the token's name and symbol from the list.
 
-The Superchain Token List is organized by the token's address and native blockchain.
-[Search the token list](https://github.com/ethereum-optimism/ethereum-optimism.github.io/blob/master/optimism.tokenlist.json) for the token you want to bridge to confirm that it's included in the list.
-Make sure that the chain ID in the entry matches the chain ID of the blockchain you're bridging from.
-Retrieve the token's name and symbol from the list.
+  {<h3>Find the bridged representation of the token</h3>}
 
-{<h3>Find the bridged representation of the token</h3>}
-
-Once you've found the token you want to bridge, look for the token's name and symbol in the list.
-Find the entry that matches the name and symbol of the token you want to bridge and where the chain ID matches the chain ID of the blockchain you're bridging to.
-The address of this entry is the address of the bridged representation of the token you want to bridge.
-
-</Steps>
+  Once you've found the token you want to bridge, look for the token's name and symbol in the list.
+  Find the entry that matches the name and symbol of the token you want to bridge and where the chain ID matches the chain ID of the blockchain you're bridging to.
+  The address of this entry is the address of the bridged representation of the token you want to bridge.
+</Steps>

pages/chain/tokenlist.mdx

@@ -20,7 +20,7 @@ This page is automatically generated from the Superchain Token List.
 
 ### USDC on OP Mainnet
 
-<Callout type="warning">
+<Callout>
 The legacy bridged version of USDC (USDC.e) at address `0x7f5c764cbc14f9669b88837ca1490cca17c31607` is being deprecated on OP Mainnet. 
 Users and developers should migrate to using the native USDC token issued directly by [Circle](https://www.circle.com/en/), the issuer of [USDC](https://www.circle.com/en/usdc?gad_source=1).
 </Callout>