Update README_src.adoc (#36)

* Update README_src.adoc

* Minor edits

* Minor edits

* Update md

Author: Sacha Lansky

README.md

@@ -28,52 +28,52 @@ The tags not mentioning the build version always point to the latest one. In the
 
 There are a few other helpers you may want to check out when using `srtool`:
 
--   [srtool-cli](https://github.com/chevdor/srtool-cli): This Rust executable supersedes the preiviously recommended alias solution. It brings many benefits and is moreover much easier to use.
+-   [srtool-cli](https://github.com/chevdor/srtool-cli): This Rust executable supersedes the previously recommended alias solution. It brings many benefits and is much easier to use.
 
--   [srtool-app](https://gitlab.com/chevdor/srtool-app): The basic features of `srtool` as here available from a simple GUI accessible from a few clicks and available on multiple platforms.
+-   [srtool-app](https://gitlab.com/chevdor/srtool-app): The basic features of `srtool` in a simple GUI, available on multiple platforms.
 
 -   [srtool-actions](https://github.com/chevdor/srtool-actions): This Github actions makes it much easier to integrate `srtool` in your CI.
 
 -   …​ and more to come
 
 ![Frame 1 256](resources/Frame%201_256.png)
 
-`srtool` is a tool for chain builders, it is widely used in CI such as Github Actions, it can also be used by anyone who wants to indenpendantly check and audit the runtime of a chain or a parachain.
+`srtool` is a tool for chain builders, it is widely used in CI such as Github Actions, it can also be used by anyone who wants to independently check and audit the runtime of a chain or a parachain.
 
-You may also want to have a look at [subwasm](https://github.com/chevdor/subwasm) as it is now part of the tooling included in `srtool`. `subwasm` can also be used independantly upon building your wasm with `srtool`.
+You may also want to have a look at [subwasm](https://github.com/chevdor/subwasm) as it is now part of the tooling included in `srtool`. `subwasm` can also be used independently upon building your wasm with `srtool`.
 
 ## History
 
-The project was initially developped from <https://gitlab.com/chevdor>.
-It now moved to Github under the [Parity Technologies](https://www.github.com/paritytech) organisation to simplify the developement and the integration with other Parity products such as Polkadot and Kusama.
+The project was initially developed by <https://gitlab.com/chevdor>.
+It has now moved to Github under the [Parity Technologies](https://www.github.com/paritytech) organisation to simplify the developement and the integration with other Parity products such as Polkadot and Kusama.
 
-The last version hosted on Gitlab has been built using Rust Stable 1.56.1. It is tagged as v0.9.18 and there is no plan on updating the Gitlab repository further. New versions will be available from <https://www.github.com/paritytech/srtool>. The functionnalities remain the same so you can (and should!) simply swap `chevdor/srtool` for `paritytech/srtool` in your workflows. The [srtool-actions](https://github.com/chevdor/srtool-actions) will remain available as `chevdor/srtool-actions@<version>` and will be updated to point at the paritytech image.
+The last version hosted on Gitlab has been built using Rust Stable 1.56.1. It is tagged as v0.9.18 and there is no plan on updating the Gitlab repository further. New versions will be available from [this repository](https://www.github.com/paritytech/srtool) only. The functionalities remain the same so you can (and should!) simply swap `chevdor/srtool` for `paritytech/srtool` in your workflows. The [srtool-actions](https://github.com/chevdor/srtool-actions) will remain available as `chevdor/srtool-actions@<version>` and will be updated to point at the paritytech image.
 
 ## Install
 
 ### Install the srtool-cli
 
-Since the `srtool-cli` (<https://github.com/chevdor/srtool-cli>) exists, there is no reason to be using an alias anymore. Using the cli over the alias brings many advantages and will save you time.
+Since the [`srtool-cli`](https://github.com/chevdor/srtool-cli) exists, there is no reason to be using an alias anymore. Using the cli over the alias brings many advantages and will save you time.
 
-The `srtool-cli` is a command line utility written in Rust, you can read more at [github.com/chevdor/srtool-cli](https://github.com/chevdor/srtool-cli), the installation process is described in more details there.
+The `srtool-cli` is a command line utility written in Rust. You can read more about the installation process [here](https://github.com/chevdor/srtool-cli).
 
 ### Using an alias
 
-This method is legacy and deprecated, prefer the `srtool-cli` utility mentioned above. This information is left here however for documentation purpose but all the functions are now availabe in the `srtool-cli`.
+This method is legacy and deprecated. It is recommended to use the `srtool-cli` utility mentioned above. This information is left here for documentation purposes only — all the functions are now availabe in the `srtool-cli`.
 
 Creating an alias helps hiding the docker complexity behind one simple command. We will see more powerful options but this one is simple enough.
 
         export RUSTC_VERSION=1.56.1; export PACKAGE=kusama-runtime; alias srtool='docker run --rm -it -e PACKAGE=$PACKAGE -v $PWD:/build -v $TMPDIR/cargo:/cargo-home paritytech/srtool:$RUSTC_VERSION'
 
-Note that defining the alias as done above will hardcode the runtime. Using `kusama-runtime` as show above means you will **always** check the kusama runtime. If you need more, check the next chapter.
+Note that defining the alias as done above will hardcode the runtime. Using `kusama-runtime` as shown above means you will **always** check the Kusama runtime. If you need more, check the next chapter.
 
 If you want to check what your alias is, use `type srtool`
 
 The command to invoke a build will then be `srtool build`.
 
 ## Use
 
-Now that you defined the srtool alias, you can use it as shown below:
+Now that you have defined the srtool alias, you can use it as shown below:
 
 **See the help**
 
@@ -85,7 +85,7 @@ Now that you defined the srtool alias, you can use it as shown below:
 
 **Typical run**
 
-Invoking `srtool build` with:
+Invoking `srtool build` with
 
     $ srtool build
 
@@ -100,7 +100,7 @@ will output something that looks like this:
 
             Finished release [optimized] target(s) in 37.43s
 
-some times later …​
+and finally …​
 
     ✨ Your Substrate WASM Runtime is ready! ✨
     Summary:
@@ -131,7 +131,7 @@ If you prefer a json output, srtool has you covered:
 
     $ srtool build --json
 
-Will give you such an output:
+The output will look something like:
 
     {
         "gen": "srtool v0.9.18",
@@ -239,7 +239,7 @@ Will give you such an output:
 
 ### Outdated repo
 
-If you run into issues while running `srtool`, make sure you are using a decently recent version of Polkadot/Substrate:
+If you run into issues while running `srtool`, make sure you’re using a decently recent version of Polkadot/Substrate:
 
 Then run the following commands:
 
@@ -258,11 +258,11 @@ Run the following command:
     alias srtool
 
 And make sure that you see `$PWD:/build/` and not `/home/your_name/:/build`.
-If you are running into this issue, your `.bash_profile` likely contains double quotes (") where you should have used single ones (').
+If you’re running into this issue, your `.bash_profile` likely contains double quotes (") where you should have used single ones (').
 
 ### Other cases
 
-If you still run into troubles, please open a new issue and describe the error you see and the steps you took.
+If you still run into any trouble, please open a new issue and describe the error you see and the steps you took.
 
 ## Proposal field
 
@@ -273,23 +273,23 @@ What is important in the output of srtool is the `Proposal` field:
         Proposal : 0x5931690e71e9d3d9f04a43d8c15e45e0968e563858dd87ad6485b2368a286a8f
         ... more blabla ...
 
-The `Proposal` field value should should match the value of the proposal you can see in the Polkadot UI.
+The `Proposal` field value should match the value of the proposal you can see in the Polkadot UI.
 
 ## IPFS Hash
 
-Starting with version 0.9.8, the IPFS hash is computed and added to the output. `srtool` is only computing the hash. It does not publish the the file to IPFS nor connect to IPFS.
+Starting with version 0.9.8, the IPFS hash is computed and added to the output. `srtool` is only computing the hash. It neither publishes the file to IPFS nor connects to IPFS.
 
 **Advanced usage**
 
-if you feel fancy, you may also run:
+If you’re feeling fancy, you may also run:
 
     srtool bash
 
-and look around the `/srtool` folder
+and look around the `/srtool` folder.
 
 ## ZSH/ Zinit users
 
-If you are using `zsh` and `zinit`, you may benefit from using the srtool snippet I am maintaining.
+If you’re using `zsh` and `zinit`, you may benefit from using the srtool snippet maintained [here](https://gitlab.com/chevdor/dotfiles/-/tree/master/zsh-plugins).
 
 To do so, add the following to your `zshconfig`:
 
@@ -321,22 +321,22 @@ So say you want to build a builder for rustc 1.56.1:
 
 You can see the list of available scripts in the `/scripts` folder:
 
--   `help`: Show some help
+-   `help`: Show some help.
 
 -   `version`: Show some version.
 
--   `info`: Show systems infos that are available before running a build
+-   `info`: Show available system info before running a build.
 
--   `build`: Run the actual build
+-   `build`: Run the actual build.
 
-The `info` and `version` scripts pass any arguments you pass to the script to `jq`. So you can play with `c` (compact), `-M`(monochrome), `-C` color output. For instance `docker run --rm -it -v $PWD:/build chevdor/srtool:1.56.1 info -cM` shows a monochrome output on a single line.
+The `info` and `version` scripts pass any arguments you pass to the script to `jq`. So you can play with `c` (compact), `-M` (monochrome), `-C` color output. For instance `docker run --rm -it -v $PWD:/build chevdor/srtool:1.56.1 info -cM` shows a monochrome output on a single line.
 
 ## Build your custom chain / parachain
 
 Building the runtime for your custom chain may not work with the default used for Kusama, Polkadot and Co.
-You can however help `srtool` making the right choices using ENV VARs. You will need to make a new alias as shown below
+You can however help `srtool` make the right choices using ENV VARs. You will need to make a new alias as shown below.
 
-Here is for instance how to build the runtime for the substrate-node-template:
+Here’s how to build the runtime for the substrate-node-template, for instance:
 
     alias mysrtool='docker run --rm -it --name mysrtool -e RUNTIME_DIR=runtime -e BUILD_OPTS=" " -e PACKAGE=$PACKAGE -v $PWD:/build -v /tmp/cargo:/cargo-home chevdor/srtool:$RUSTC_VERSION'
 
@@ -346,7 +346,7 @@ Using `srtool-cli` makes the above much easier…​
 
 ## Export the runtime
 
-In order to easily export your runtime, it will be copied in the container into the `/out` folder.
+To easily export your runtime, it will be copied in the container into the `/out` folder.
 If you mount this docker volume, you will find the wasm on your local filesystem once the run is complete.
 
     docker run ... -v /tmp/out:/out ...