Update README.md

Author: savvar9991

README.md

@@ -17,7 +17,7 @@
 
 </div>
 
-Astar Network is an interoperable blockchain based the Substrate framework and the hub for dApps within the Polkadot Ecosystem.
+Astar Network is an interoperable blockchain based on the Substrate framework and the hub for dApps within the Polkadot Ecosystem.
 With Astar Network and Shiden Network, people can stake their tokens to a Smart Contract for rewarding projects that provide value to the network.
 
 For contributing to this project, please read our [Contribution Guideline](./CONTRIBUTING.md).
@@ -30,7 +30,7 @@ Execute the following command from your terminal to set up the development envir
 
 ```bash
 # install Substrate development environment via the automatic script
-$ curl https://getsubstrate.io -sSf | bash -s -- --fast
+$ curl https://docs.substrate.io/install/ -sSf | bash -s -- --fast
 
 # clone the Git repository
 $ git clone --recurse-submodules https://github.com/AstarNetwork/Astar.git
@@ -112,7 +112,7 @@ The runtime crate version will align its major and minor versions with the Rust
 All dependencies should be listed inside the workspace's root `Cargo.toml` file.
 This allows us to easily change version of a crate used by the entire repo by modifying the version in a single place.
 
-Right now, if **non_std** is required, `default-features = false` must be set in the root `Cargo.toml` file (related to this [issue](https://github.com/rust-lang/cargo/pull/11409)). Otherwise, it will have no effect, causing your compilation to fail.
+Right now, if **no_std** is required, `default-features = false` must be set in the root `Cargo.toml` file (related to this [issue](https://github.com/rust-lang/cargo/pull/11409)). Otherwise, it will have no effect, causing your compilation to fail.
 Also `package` imports aren't properly propagated from root to sub-crates, so defining those should be avoided.
 
 Defining _features_ in the root `Cargo.toml` is additive with the features defined in concrete crate's `Cargo.toml`.
@@ -122,7 +122,7 @@ Defining _features_ in the root `Cargo.toml` is additive with the features defin
 1. Check if the dependency is already defined in the root `Cargo.toml`
     1. if **yes**, nothing to do, just take note of the enabled features
     2. if **no**, add it (make sure to use `default-features = false` if dependency is used in _no_std_ context)
-2. Add `new_dependecy = { workspace = true }` to the required crate
+2. Add `new_dependency = { workspace = true }` to the required crate
 3. In case dependency is defined with `default-features = false` but you need it in _std_ context, add `features = ["std"]` to the required crate.
 
 ## Further Reading