Update create-subnet walkthrough

Update walkthrough as CLI options have changed

Signed-off-by: Michael Standen <[email protected]>

content/docs/tooling/create-deploy-subnets/create-subnet.mdx

@@ -43,43 +43,32 @@ The following sections walk through each question in the wizard.
 
 ### Choose Your VM[​](#choose-your-vm "Direct link to heading")
 
-Select `SubnetEVM`.
+Select `Subnet-EVM`.
 
-### Enter Your Subnet's ChainID[​](#enter-your-subnets-chainid "Direct link to heading")
-
-Choose a positive integer for your EVM-style ChainID.
-
-In production environments, this ChainID needs to be unique and not shared with any other chain. You can visit [chainlist](https://chainlist.org/) to verify that your selection is unique. Because this is a development Subnet, feel free to pick any number. Stay away from well-known ChainIDs such as 1 (Ethereum) or 43114 (Avalanche C-Chain) as those may cause issues with other tools.
+### Choose Blockchain Configuration[​](#choose-blockchain-configuration "Direct link to heading")
 
-### Token Symbol[​](#token-symbol "Direct link to heading")
+Select the `defaults for a test environment` to reduce the number of settings to select from.
 
-Enter a string to name your Subnet's native token. The token symbol doesn't necessarily need to be unique. Example token symbols are AVAX, JOE, and BTC.
+For advanced users, select `I don't want to use default values` to see the full list of configuration options.
+The full list of options are not covered in this guide.
 
 ### Subnet-EVM Version[​](#subnet-evm-version "Direct link to heading")
 
-Select `Use latest version`.
-
-### Gas Fee Configuration[​](#gas-fee-configuration "Direct link to heading")
+Select `Use latest release version`.
 
-This question determines how to set gas fees on your Subnet.
-
-Select `Low disk use / Low Throughput 1.5 mil gas/s (C-Chain's setting)`.
-
-### Airdrop[​](#airdrop "Direct link to heading")
-
-Select `Airdrop 1 million tokens to the default address (do not use in production)`.
+### Enter Your Subnet's ChainID[​](#enter-your-subnets-chainid "Direct link to heading")
 
-This address's private key is well-known, so DO NOT send any production funds to it. Attackers would likely drain the funds instantly.
+Choose a positive integer for your EVM-style ChainID.
 
-When you are ready to start more mature testing, select `Customize your airdrop` to distribute funds to additional addresses.
+In production environments, this ChainID needs to be unique and not shared with any other chain. You can visit [chainlist](https://chainlist.org/) to verify that your selection is unique. Because this is a development Subnet, feel free to pick any number. Stay away from well-known ChainIDs such as 1 (Ethereum) or 43114 (Avalanche C-Chain) as those may cause issues with other tools.
 
-### Precompiles[​](#precompiles "Direct link to heading")
+### Token Symbol[​](#token-symbol "Direct link to heading")
 
-Precompiles are Avalanche's way of customizing the behavior of your Subnet. They're strictly an advanced feature, so you can safely select `No` for now.
+Enter a string to name your Subnet's native token. The token symbol doesn't necessarily need to be unique. Example token symbols are AVAX, JOE, and BTC.
 
 ### Wrapping up[​](#wrapping-up "Direct link to heading")
 
-If all worked successfully, the command prints `Successfully created subnet configuration`.
+If all worked successfully, the command prints `Successfully created blockchain configuration`.
 
 You've successfully created your first Subnet configuration. Now it's time to deploy it.
 
@@ -216,4 +205,4 @@ FAQ[​](#faq "Direct link to heading")
 
 **How is the Subnet ID determined upon creation?**
 
-The Subnet ID is the hash of the transaction that created the Subnet.
+The Subnet ID is the hash of the transaction that created the Subnet.