Add coming soon labels and update EVM on Flow naming (#636)

* doc: add coming soon label

* doc: nit

* doc: update naming evm on flow

docs/evm/build/accounts.md

@@ -12,27 +12,21 @@ Are you a Cadence developer looking for information about Accounts on Cadence? I
 
 # Accounts
 
-There are three types of accounts on FlowEVM.
+There are three types of accounts used for EVM on Flow.
 
 1. **Externally Owned Accounts (EOA)**: EOAs are controlled by private individuals using cryptographic keys and can initiate transactions directly. They are the primary account type for users to interact with the blockchain, holding and sending cryptocurrency or calling smart contract functions.
 2. **Contract Accounts**: These accounts hold smart contract code and are governed by this code's logic. Unlike EOAs, Contract Accounts do not initiate transactions on their own but can execute transactions in response to calls they receive from EOAs or other contracts.
 3. **Cadence Owned Accounts (COA)**
 
-EOAs and Contract accounts on FlowEVM function the same as on other EVM networks.  Read more about EOAs and Contract 
-accounts on the [Ethereum docs](https://ethereum.org/developers/docs/accounts). EVM developers can use FlowEVM without
-having to use COAs. However, in order to leverage Flow features for FlowEVM developers need to use COAs.
+EOAs and Contract accounts function the same as on other EVM networks.  Read more about EOAs and Contract accounts on the [Ethereum docs](https://ethereum.org/developers/docs/accounts). EVM developers can use EVM on Flow without having to use COAs. However, in order to leverage all the features of Cadence, developers will need to utilize Cadence Owned Accounts.
 
 ## Cadence Owned Accounts
 
-Cadence Owned Accounts (COAs) are a new account type on FlowEVM which mediates interactions between FlowEVM and Cadence 
-environments. COAs are intended for use by end-users, the same as EOAs. However, COAs execute FlowEVM transactions as 
-directed from Cadence whereas EOAs run FlowEVM transactions identically to other EVMs via the JSON-RPC endpoint. 
-Unlike EOAs, COAs do not have a key but are assigned a 20-byte EVM address upon creation from Cadence. 
+Cadence Owned Accounts (COAs) are a new account type on Flow which mediates interactions between EVM and Cadence  environments. COAs are intended for use by end-users, the same as EOAs. However, COAs execute EVM transactions as directed from Cadence whereas EOAs run EVM transactions identically to other EVMs via the JSON-RPC endpoint.
+Unlike EOAs, COAs do not have a key but are assigned a 20-byte EVM address upon creation from Cadence.
 
-COAs exist in Cadence as a Resource type which is in turn owned by a Flow account on the Cadence VM. COAs facilitate 
-the execution of FlowEVM transactions using its `run` method. They also enable the deployment of Solidity contracts from
-Cadence, as well as other utility functions to interact with FlowEVM.
+COAs exist in Cadence as a Resource type which is in turn owned by a Flow account on the Cadence VM. COAs facilitate the execution of EVM transactions using its `run` method. They also enable the deployment of Solidity contracts from Cadence, as well as other utility functions to interact with EVM.
 
 For more information on Cadence Owned Accounts, see the [FlowEVM FLIP](https://github.com/onflow/flips/pull/225/files)
 
-![FlowEVM-Account-Model](flow-evm-account-model.png)
+![FlowEVM-Account-Model](flow-evm-account-model.png)

docs/evm/build/networks.md

@@ -12,30 +12,30 @@ FlowEVM has the following public RPC nodes available:
 
 | Name            | Value                                   |
 |-----------------|-----------------------------------------|
-| Network Name    | Flow Previewnet                      |
-| Description     | The public RPC URL for FlowEVM Preview  |
+| Network Name    | Previewnet                              |
+| Description     | The public RPC URL for Flow Previewnet  |
 | RPC Endpoint    | https://previewnet.evm.nodes.onflow.org |
 | Chain ID        | 646                                     |
 | Currency Symbol | FLOW                                    |
-| Block Explorer  | https://previewnet.flowdiver.io          |
+| Block Explorer  | https://previewnet.flowdiver.io         |
 
-# Testnet
+# Testnet (Coming Soon)
 
 | Name            | Value                                  |
 |-----------------|----------------------------------------|
-| Network Name    | Testnet                        |
-| Description     | The public RPC URL for testnet |
+| Network Name    | Testnet                                |
+| Description     | The public RPC URL for Flow Testnet         |
 | RPC Endpoint    | https://testnet.evm.nodes.onflow.org   |
-| Chain ID        | Coming Soon                            |
+| Chain ID        | 646                                    |
 | Currency Symbol | FLOW                                   |
 | Block Explorer  | https://testnet.flowdiver.io           |
 
-# Mainnet
+# Mainnet (Coming Soon)
 
 | Name            | Value                                  |
 |-----------------|----------------------------------------|
-| Network Name    | Mainnet                        |
-| Description     | The public RPC URL for mainnet |
+| Network Name    | Mainnet                                |
+| Description     | The public RPC URL for Flow Mainnet    |
 | RPC Endpoint    | https://mainnet.evm.nodes.onflow.org   |
 | Chain ID        | 747                                    |
 | Currency Symbol | FLOW                                   |

docs/evm/build/wallets-and-configurations.md

@@ -67,4 +67,4 @@ Users who first come to your dApp's website will need to first approve a connect
 
 After they approve, your app be connected to the FlowEVM network. 
 
-By using this approach to add the FlowEVM network to Metamask, you can avoid manual user data entry and ensure that users are ready to interact with your dApp!
+By using this approach to add the FlowEVM network to Metamask, you can avoid manual user data entry and ensure that users are ready to interact with your dApp!