Fix typos

applications/Syncra.md

@@ -16,7 +16,7 @@ Syncra simplifies this process. We're working on a no-code solution to create, m
 
 ![](https://i.imgur.com/Pe1Z26r.png)
 
-Transparency is inherent in blockchain technology, but many situations require privacy, especially in DAOs when it comes to tough decisions. Also in times when connecting particular wallet address to a person or entity can by relatively easy, or even required (KYC, ID verification, Identity providers). With Syncra, we want to provide a solution for confidential voting where votes are hidden by default, but everything happens on-chain. Leveraging a modular approach, we want to enhance privacy, provide an easy way for treasury management, and offer on-chain automation, ultimately providing this service for the entire Substrate ecosystem.
+Transparency is inherent in blockchain technology, but many situations require privacy, especially in DAOs when it comes to tough decisions. Also in times when connecting particular wallet address to a person or entity can be relatively easy, or even required (KYC, ID verification, Identity providers). With Syncra, we want to provide a solution for confidential voting where votes are hidden by default, but everything happens on-chain. Leveraging a modular approach, we want to enhance privacy, provide an easy way for treasury management, and offer on-chain automation, ultimately providing this service for the entire Substrate ecosystem.
 
 Having Syncra in the PolkaDOT ecosystem is a necessary piece of the puzzle. Just as Tally, Aragon, and Snapshot exist on EVM, Syncra exists on Substrate.
 
@@ -47,7 +47,7 @@ Modular-dao is a set of traits with default implementations built using [ink!](h
 
 ### How does it work?
 
-The traits with default implementations consists of:
+The traits with default implementations consist of:
 
 - **Votes** - trait that provides 3 basic methods that allow to get voting power for of an address and delegate votes. The default implementation is done with combination of PSP22 token. However, **Votes** can represent any type of the "strategy" (for example PSP34-based).
 - **Governor** - extends **Votes** and **AccessControl**. The base for the DAO. Provides proposal creation and execution functionalities.
@@ -78,7 +78,7 @@ Known drawbacks are the security concerns, related with storing private keys on
 
 ### Data Model
 
-Syncra uses IPFS as well as MongoDB for storing additional data about DAOs, proposals, and user stats. The purpose is to minimise the data footprint on the blockchain itself, as storing data onchain is costly, and not very performant. Only the critical data is stored inside of the the DAO Smart Contract’s. 
+Syncra uses IPFS as well as MongoDB for storing additional data about DAOs, proposals, and user stats. The purpose is to minimise the data footprint on the blockchain itself, as storing data onchain is costly, and not very performant. Only the critical data is stored inside of the DAO Smart Contract’s. 
 
 DAOs, Proposals titles, and descriptions are stored on the IPFS, and then corresponding IPFS hashes are set on the DAO contract's storage. In this way, users can be sure that the data about the given DAO or Proposal won’t be modified, nor fade-away if the server ever goes down. The same applies to storing images, as we use web3 storage for image upload.
 
@@ -90,7 +90,7 @@ In the scope of this grant, several core parts will be implemented, as the exten
 
 ### MVP (Pre-Grant)
 
-The MVP of the Syncra Platform, that we are going to start with, will consist the following parts:
+The MVP of the Syncra Platform, that we are going to start with, will consist of the following parts:
 
 1. Frontend Application with the connection to Wallet, Smart Contracts, and Backend
 2. Set of Smart Contracts based on PSP22 voting strategy
@@ -145,9 +145,9 @@ Documentation will published on the [GH Pages](https://pages.github.com/)
 
 #### Risks
 
-There are several known risk that we are aware of, and will try our best to find solutions to prevent those scenarios from happening. Nevertheless, it is worth noticing those potential fields, which could have been improved for better safety.
+There are several known risks that we are aware of, and will try our best to find solutions to prevent those scenarios from happening. Nevertheless, it is worth noticing those potential fields, which could have been improved for better safety.
 
-* Storing Account Private Keys for Off-Chain Automation Relayer - since for sending transactions to the Smart Contracts, we need an actual on-chain Address, the seeds for that account, has to be stored somewhere on the Cloud. In this way, no human interaction is needed to create a signature. In our solution, we have no other option then just store those keys on one of the Cloud services. In such scenarios, there is always a risk of a data breach, that could compromise the access to the account, with the access to the funds stored for covering gas fees on it.
+* Storing Account Private Keys for Off-Chain Automation Relayer - since for sending transactions to the Smart Contracts, we need an actual on-chain Address, the seeds for that account, has to be stored somewhere on the Cloud. In this way, no human interaction is needed to create a signature. In our solution, we have no other option than just store those keys on one of the Cloud services. In such scenarios, there is always a risk of a data breach, that could compromise the access to the account, with the access to the funds stored for covering gas fees on it.
 
 * Smart Contracts Security Hole - we expect our Smart Contracts to be initially audited by [Kudelski Security](https://kudelskisecurity.com/) as a part of AlephZero grant. However, there is still a risk that something will not be caught during the audit, and we will also extend those Smart Contracts during this Project as for the purpose of creating OpenZeppelins like standards. During the development, some additional security issues may occur.
 
@@ -157,7 +157,7 @@ There are several known risk that we are aware of, and will try our best to find
 
 Given the importance of scalable, and customisable DAO infrastructure, which many protocols needs, we want to introduce Syncra. As a easy to use, modular, reliable, and customisable platform we believe, that is crucial element of the ecosystem. Leveraging undisclosed voting, treasury management, on-chain automation, and many others we might bring a real value.
 
-Our project aim to be the ecosystem standard for DAOs on Polkadot, Kusama, Aleph Zero and any Subsrate based ecosystem.
+Our project aims to be the ecosystem standard for DAOs on Polkadot, Kusama, Aleph Zero and any Substrate based ecosystem.
 
 ## Team
 
@@ -286,4 +286,4 @@ Web3 Foundation Website, and Personal Recommendation.
 
 ### Previous grants you may have applied for
 
-- Aleph Zero Grants program
+- Aleph Zero Grants program

applications/Tellor.md

@@ -23,7 +23,7 @@ oracle consumer smart contracts deployed on the same EVM parachain will use the
 while oracle consumer parachains will interact with the controller contracts via XCM. EVM/WASM smart contracts on any other smart contract parachain could also consume oracle data via the oracle pallet once installed there.
 
 The controller smart contracts will interact with the oracle pallet via Solidity precompiles, precompiled contracts which handle the call translation from Solidity to native Substrate pallets, and XCM. 
-The XCM pallets then handle cross-chain messaging, effectively enabling the smart contracts to invoke dispatchable functions within the oracle pallet installed on other parachains, as well as allow the pallet to invoke functions available within the controller smart contracts.
+The XCM pallets then handle cross-chain messaging, effectively enabling the smart contracts to invoke dispatchable functions within the oracle pallet installed on other parachains, as well as allowing the pallet to invoke functions available within the controller smart contracts.
 
 ### Project Details
 
@@ -58,7 +58,7 @@ This smart contract is responsible for the creation and funding of data feeds by
 This functionality will need to be ported to a native Substrate pallet, so that an oracle consumer parachain can create and fund feeds as well as pay reporters locally using its own token. A reporter will earn local staking rewards based on their percentage of the overall parachain stake locked in the Oracle contract.
 
 **Consumer (Using Tellor) Contract**
-The Using Tellor contract is incorporated into consumer smart contracts to access reported oracle data.The functionality and APIs exposed here will need to be ported to a native Substrate pallet, so that a parachain can make use of available oracle data stored within its own chain state.
+The Using Tellor contract is incorporated into consumer smart contracts to access reported oracle data. The functionality and APIs exposed here will need to be ported to a native Substrate pallet, so that a parachain can make use of available oracle data stored within its own chain state.
 
 **Parachain Integration Contract**
 A new lightweight smart contract to handle parachain registration and ease parachain integration from the Oracle and Governance contracts. Registration provides parachain-specific configuration and ensures that sensitive functionality can only be called by the corresponding consumer parachain ‘owner’ accounts. Helper functions will abstract the necessary call encodings for remote execution, keeping cross-chain messaging functionality separate from oracle and governance logic.
@@ -201,8 +201,8 @@ Details:  A new Substrate pallet will be required which includes the core oracle
 | **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. |
 | **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. |
 | 1 | Substrate Oracle pallet design and integration | We will provide the Substrate oracle pallet |
-| 2 | Tests and a guide for testing functionallity of the the pallet with integration of a mock project on selected parachains| We will provide tests and a guide to test cross functionality of the system for interactions between the EVM chain and consumer chain and oracle pallet (meaning test the functinallity between milestone 1 and 2 delivarable 1 -  solidity contracts, pallet, XCM)|
-| 3 | Documentation/ Usage Examples| We will provide documenatation and usage examples for the system.                                                                                               |
+| 2 | Tests and a guide for testing functionality of the pallet with integration of a mock project on selected parachains| We will provide tests and a guide to test cross functionality of the system for interactions between the EVM chain and consumer chain and oracle pallet (meaning test the functionality between milestone 1 and 2 deliverable 1 -  solidity contracts, pallet, XCM)|
+| 3 | Documentation/ Usage Examples| We will provide documentation and usage examples for the system.                                                                                               |
 
 
 
@@ -225,4 +225,4 @@ You can find more information about the program [here](../README.md#moneybag-ref
 
 **How did you hear about the Grants Program?** 
 
-We talked to Rohan at a few events about building on Polkadot and he recommended we apply!  We’ve been in touch with Robin Ejsmond-Frey, Frank Bell, and Guatam from Parity who have done significant work with us in developing the specifications and design for the build. 
+We talked to Rohan at a few events about building on Polkadot and he recommended we apply!  We’ve been in touch with Robin Ejsmond-Frey, Frank Bell, and Guatam from Parity who have done significant work with us in developing the specifications and design for the build. 

applications/chainviz.md

@@ -29,7 +29,7 @@ Application in its current alpha version provides the following features:
 
 **This application is to fund the building of the first major version of Chainviz**, with the following features/visualizations:
 
-- Complete rebuild of the the existing functionality with improved UI/UX and WebGL models and animations
+- Complete rebuild of the existing functionality with improved UI/UX and WebGL models and animations
 - Additional support for Polkadot
 - New visualizations
   - Parachains
@@ -290,7 +290,7 @@ We have successfully [delivered](https://github.com/w3f/Grant-Milestone-Delivery
 
 **Awards Received**
 
-Some of the recent design awards that the design team have received:
+Some of the recent design awards that the design team has received:
 
 1. CSS Design awards ([link](https://www.cssdesignawards.com/sites/klad-syndicate/41871/))
 2. Awwwards ([link](https://www.awwwards.com/Klad/))

applications/helixstreet.md

@@ -10,7 +10,7 @@
 
 ### Overview
 
-helixstreet is a project to extend the use of Blockchain technology to genomics. helixstreet chose substrate as technology to implement a pallet to store a Merkle tree hash of genomic raw sequencing data. Relationsships ( ancestry ) can be documented in the blockchain based on relationships between genomic data. Currently we are planning to implement helixstreet as parathread.
+helixstreet is a project to extend the use of Blockchain technology to genomics. helixstreet chose substrate as technology to implement a pallet to store a Merkle tree hash of genomic raw sequencing data. Relationships ( ancestry ) can be documented in the blockchain based on relationships between genomic data. Currently we are planning to implement helixstreet as parathread.
 
 Ancestry data and personal genomic relationships are today stored centralized. helixstreet's approach allows the representation of ancestry data in a decentralized manner.
 
@@ -21,7 +21,7 @@ The project is in this stage just a pallet.
 
 ### Ecosystem Fit
 
-The project extends the use of Polkadot ( or Kusama ) to a whole new use case. helixstreet would be an application specific parathread. It solves the problem of ownership of genomic data and the the human desire to conduct genealogical research without a central authority.
+The project extends the use of Polkadot ( or Kusama ) to a whole new use case. helixstreet would be an application specific parathread. It solves the problem of ownership of genomic data and the human desire to conduct genealogical research without a central authority.
 
 ## Team :busts_in_silhouette:
 
@@ -82,7 +82,7 @@ N/A
 | 0d. | Docker | We will provide a Dockerfile that can be used to test all the functionality delivered with this milestone. The docker image will not include sequencing data. |
 | 0e. | Article | We will publish an **article**/workshop that explains what was achieved as part of the grant. |
 | 1. | Substrate module: genomics | We will create a Substrate module that will store the merkle hash of genomic sequencing raw data. | 
-| 2. | Program to generate Hashtree | We will creates a hash tree for all reads of the DNA probe. The script should calculate for every Read of every Chromosome a hash and create a Merkle tree to reduce storage. Furthermore the script should store a vector ( or the main root ) of the root hashes automatically in the Blockchain assigned to the private key. A flag is needed to distinguish between entries made by a machine ( e.g. Sequel II ) or by the identified owner of the DNA raw data ( the private key of the human being represented by the sequencing data ). The program will be realized in rust. | 
+| 2. | Program to generate Hashtree | We will create a hash tree for all reads of the DNA probe. The script should calculate for every Read of every Chromosome a hash and create a Merkle tree to reduce storage. Furthermore the script should store a vector ( or the main root ) of the root hashes automatically in the Blockchain assigned to the private key. A flag is needed to distinguish between entries made by a machine ( e.g. Sequel II ) or by the identified owner of the DNA raw data ( the private key of the human being represented by the sequencing data ). The program will be realized in rust. | 
 
 
 

applications/maintenance/Substratesnap_Maintenance.md

@@ -21,11 +21,11 @@
 
 
 - The SubstrateSnap (plugin) enables support for the Polkadot and Kusama network inside of Metamask and by doing so enables Polkadot dApps easy integration with Metamask.
-- ChainSafe believes that Snaps are vital to fostering increased adoption of web3 systems and as such consider the maitainance of the ChainSafe SubstrateSnap a strategic priority.     
+- ChainSafe believes that Snaps are vital to fostering increased adoption of web3 systems and as such consider the maintenance of the ChainSafe SubstrateSnap a strategic priority.     
 
 ### Project Details
 
-This is a maitainance proposal for a project that has already been developed. The initial development was originally funded through a [W3F grant](https://github.com/w3f/General-Grants-Program/pull/244). The project is open-source and its repository and Wiki page can be located using the following links:
+This is a maintenance proposal for a project that has already been developed. The initial development was originally funded through a [W3F grant](https://github.com/w3f/General-Grants-Program/pull/244). The project is open-source and its repository and Wiki page can be located using the following links:
 
 https://github.com/ChainSafe/metamask-snap-polkadot
 https://github.com/ChainSafe/metamask-snap-polkadot/wiki 
@@ -174,4 +174,4 @@ We are owners of the SubstrateSnap repository. Further, the maintainers of Polka
 **How did you hear about the Grants Program?** 
  ChainSafe is a long-standing friend of The Web3 Foundation and has collaborated on several projects over the past few years. It was through this relationship that ChainSafe was made aware of the Maintenance Grant program.  It is also worth noting that ChainSafe has been awarded W3F grant funding for other projects in the past, one such being Gossamer.
 
-
+

applications/maintenance/wasm-opt-for-rust.md

@@ -116,7 +116,7 @@ Our responsibilities:
 - Submit PRs to upgrade `wasm-opt` in `cargo-contract` and `wasm-builder`
   when new versions are published.
 - Fix reported bugs if possible and within budget.
-- Implement minor feature requests if disirable and within budget.
+- Implement minor feature requests if desirable and within budget.
 
 Issues we want to fix:
 
@@ -149,7 +149,7 @@ The monthly budget is calculated based on the following:
 
 - 10 hours to upgrade Binaryen
 - 300 USD / hour
-- x2 for unforseen obstacles
+- x2 for unforeseen obstacles
 
 This implies that a particularly difficult upgrade could exceed the monthly budget.
 In such a case the work would spill over across multiple months,