Add missing backticks, fix typo, change sandbox reference

Author: lsgunnlsgunn

README.md

@@ -325,7 +325,7 @@ CHAINWEB=testnet forge script --multi script/Counter.s.sol:CounterScript \
 
 ## Sample configuration and deployment
 
-The following sample `chainweb.config.json` file demonstrates the configuration settings for the default `anvil` environment, a local development `sandbox` environment, and the Chainweb EVM `testnet` network.
+The following sample `chainweb.config.json` file demonstrates the configuration settings for the default `anvil` environment, a local development `evm-local` environment, and the Chainweb EVM `testnet` network.
 
 ```json
 {
@@ -334,7 +334,7 @@ The following sample `chainweb.config.json` file demonstrates the configuration
         "chainwebChainIdOffset": 20,
         "chainIdOffset": 62600
     },
-    "sandbox": {
+    "evm-local": {
         "numberOfChains": 2,
         "chainwebChainIdOffset": 20,
         "chainIdOffset": 1789,
@@ -349,10 +349,10 @@ The following sample `chainweb.config.json` file demonstrates the configuration
 }
 ```
 
-To deploy the Counter contract using the `sandbox` configuration settings and the private key for one of the predefined development wallet accounts:
+To deploy the Counter contract using the `evm-local` configuration settings and the private key for one of the predefined development wallet accounts:
 
 ```bash
-CHAINWEB=sandbox forge script --multi script/Counter.s.sol:CounterScript \
+CHAINWEB=evm-local forge script --multi script/Counter.s.sol:CounterScript \
   --private-key "0xe711c50150f500fdebec57e5c299518c2f7b36271c138c55759e5b4515dc7161" \
   --broadcast --legacy
 ```
@@ -491,7 +491,7 @@ If you attempt to verify a contract with the same bytecode as a contract that ha
 [address] is already verified. Skipping verification.
 ```
 
-To test contract verification on multiple chains, you must change the bytecode, redeploy, then run the verify-contract command on the redployed contract.
+To test contract verification on multiple chains, you must change the bytecode, redeploy, then run the `verify-contract` command on the redeployed contract.
 
 You can change the bytecode by adding a constant at the top of the contract like this: