diff --git a/.maintain/node-template-release/src/main.rs b/.maintain/node-template-release/src/main.rs index b250f22b0c..2ec1ac9975 100644 --- a/.maintain/node-template-release/src/main.rs +++ b/.maintain/node-template-release/src/main.rs @@ -235,7 +235,7 @@ fn main() { let commit_id = get_git_commit_id(&options.node_template); let top_level_cargo_toml_path = node_template_path.join("Cargo.toml"); - // Check if top level Cargo.toml exists. If not, create one in the destination + // Check if top-level Cargo.toml exists. If not, create one in the destination if !cargo_tomls.contains(&top_level_cargo_toml_path) { // create the top_level_cargo_toml OpenOptions::new() diff --git a/README.md b/README.md index 5f12fbba11..65baeec81e 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Frontier is the EVM backbone of Polkadot. Frontier provides a compatibility layer of EVM, so that you can run any Ethereum dapps on Polkadot, unmodified. Using Frontier, you get access to all of the Ethereum RPC APIs you are already familiar with, and therefore you can continue -to develop your dapps in your favourite Ethereum developer tools. As a bonus, +to develop your dapps in your favorite Ethereum developer tools. As a bonus, you can even run many Ethereum L2s inside Frontier! Frontier is also a migration framework. Besides the common strategy of direct @@ -118,4 +118,4 @@ If the affected crate does not yet have `-dev` suffix: and add `-dev` suffix. If your pull request introduces a new crate, please set its version to -`1.0.0-dev`. \ No newline at end of file +`1.0.0-dev`. diff --git a/docs/frame/evm.md b/docs/frame/evm.md index 0133e387c3..1433a1d4af 100644 --- a/docs/frame/evm.md +++ b/docs/frame/evm.md @@ -11,7 +11,7 @@ underlying EVM engine. ## Execution lifecycle -There are a separate set of accounts managed by the EVM +There is a separate set of accounts managed by the EVM module. Substrate based accounts can call the EVM Module to deposit or withdraw balance from the Substrate base-currency into a different balance managed and used by the EVM module. Once a user has populated diff --git a/docs/index.md b/docs/index.md index e64b2a4d9a..219e1060d7 100755 --- a/docs/index.md +++ b/docs/index.md @@ -10,7 +10,7 @@ features: - title: RPC Compatibility details: All existing Ethereum RPC methods work, so none of your dapps will break. - title: Substrate Module - details: Frontier can be easily integrated in your existing Substrate application as a runtime module. + details: Frontier can be easily integrated into your existing Substrate application as a runtime module. footer: Made by Parity & Wei & PureStake with ❤️ --- diff --git a/docs/node-template-release.md b/docs/node-template-release.md index 09ab3bb526..0a8e18d66c 100644 --- a/docs/node-template-release.md +++ b/docs/node-template-release.md @@ -19,7 +19,7 @@ ``` 3. Expand the output tar gzipped file that is created in the top level working dir of Frontier and - replace files in current Frontier Node Template by running the following command: + replace files in the current Frontier Node Template by running the following command: ```bash # Note the file will be placed in the top level working dir of Frontier diff --git a/docs/overview.md b/docs/overview.md index c6c9eb567a..0cf6083a47 100644 --- a/docs/overview.md +++ b/docs/overview.md @@ -6,7 +6,7 @@ independently. ## EVM execution only In many situations, a Substrate blockchain may only want to include -EVM execution capatibilities. In this way, it functions similarly to +EVM execution capabilities. In this way, it functions similarly to `pallet-contracts`, integrates with Substrate better and is less intrusive. The module, and its EVM execution capatibilties, can be added or removed at any moment via forkless upgrades. With EVM diff --git a/template/README.md b/template/README.md index 3f8cdab8b8..442527e461 100644 --- a/template/README.md +++ b/template/README.md @@ -71,7 +71,7 @@ Alice's EVM account will be funded with a large amount of Ether. The [Polkadot UI](https://polkadot.js.org/apps/#?rpc=ws://127.0.0.1:9944) can be used to see the details of Alice's EVM account. In order to view an EVM account, use the `Developer` tab of the Polkadot UI `Settings` app to define the EVM `Account` type as below. It is also necessary to define the -`Address` and `LookupSource` to send transaction, and `Transaction` and `Signature` to be able to +`Address` and `LookupSource` to send transactions, and `Transaction` and `Signature` to be able to inspect blocks: ```json