update custom gas token docs w PR feedback

Author: K-Ho

pages/builders/app-developers/tutorials/standard-bridge-custom-token.mdx

@@ -9,7 +9,7 @@ import { Callout, Steps } from 'nextra/components'
 # Bridging Your Custom ERC-20 Token Using the Standard Bridge
 
 <Callout type="info">
-**This tutorial is for developers who want to bridge a new ERC-20 token to an OP Stack chain.**
+**This tutorial is for developers who want to bridge a new ERC-20 token to an OP Stack chain. This is not related to the "Custom Gas Token" feature for new OP Stack chains**
 If you want to bridge existing tokens, you can skip to the tutorial on [Bridging ERC-20 tokens with the Optimism SDK](./cross-dom-bridge-erc20).
 </Callout>
 

pages/builders/chain-operators/management/custom-gas-token.mdx

@@ -41,6 +41,7 @@ An OP Stack chain that uses the custom gas token feature enables an end user to
   *   must be transferrable only via a call to the token address itself
   *   must only be able to set allowance via a call to the token address itself
   *   must not have a callback on transfer, and more generally a user must not be able to make a transfer to themselves revert
+  *   a user must not be able to make a transfer have unexpected side effects
 
   <Callout type="warning">
     You will NOT be able to change the address of the custom gas token after it is set during deployment.
@@ -100,6 +101,26 @@ An OP Stack chain that uses the custom gas token feature enables an end user to
 
   Ensure that the end to end system is running.
 
+  ### Validating your deployment
+
+  This calls the `WETH` predeploy which should be considered wrapped native asset in the context of custom gas token. It should return the name of the token prefixed by `"Wrapped "`
+
+  ```bash
+  cast call --rpc-url $L2_ETH_RPC_URL 0x4200000000000000000000000000000000000006 'name()(string)'
+  ```
+
+  This calls the `L1Block` predeploy should return `true`.
+
+  ```bash
+  cast call --rpc-url $L2_ETH_RPC_URL 0x4200000000000000000000000000000000000015 'isCustomGasToken()(bool)
+  ```
+
+  This calls the L1 `SystemConfig` contract and should return `true`.
+
+  ```bash
+  cast call --rpc-url $L1_ETH_RPC_URL <SYSTEM_CONFIG_ADDRESS> 'isCustomGasToken()(bool)
+  ```
+
   ### Depositing Custom Gas Token into the Chain
 
   *   To deposit the custom gas token into the chain, users must use the **`OptimismPortalProxy.depositERC20Transaction`** method

pages/stack/protocol/features/custom-gas-token.mdx

@@ -62,12 +62,13 @@ The custom token being used must adhere to the following constraints to be able
 *   must be transferrable only via a call to the token address itself
 *   must only be able to set allowance via a call to the token address itself
 *   must not have a callback on transfer, and more generally a user must not be able to make a transfer to themselves revert
+*   a user must not be able to make a transfer have unexpected side effects
+
 
 
 ## Next Steps
 
 *   Ready to get started? Read our guide on how to [deploy your custom gas token chain](/builders/chain-operators/management/custom-gas-token).
-*   For bridges or developers building on a custom gas token chain, read our tutorial on [depositing custom gas tokens into a chain](/builders/app-developers/tutorials/standard-bridge-custom-token).
 *   For more info about how the custom gas token feature works under the hood, [check out the specs](https://specs.optimism.io/protocol/granite/custom-gas-token.html).
 
 ## FAQs