docs: fix typos

LIPs/lip-0.md

@@ -9,7 +9,7 @@ created: 2023-05-24
 
 ## Motivation
 
-We want Lens to be a community ran project with standards shaped by everyone, as more builders use Lens we want them to have a voice and be able to promote ideas easily and in a way which would get eyes on it. LIPs is a great way to do this and we should start using it. Inspiration from [EIP](https://eips.ethereum.org/) was taken.
+We want Lens to be a community run project with standards shaped by everyone, as more builders use Lens we want them to have a voice and be able to promote ideas easily and in a way which would get eyes on it. LIPs is a great way to do this and we should start using it. Inspiration from [EIP](https://eips.ethereum.org/) was taken.
 
 ## Specification
 

LIPs/lip-2.md

@@ -13,7 +13,7 @@ Metadata was growing and growing, and with that, we had a flat structure which w
 
 ## Motivation
 
-We want Lens to be a community ran project with standards shaped by everyone, with the way metadata was set out before this was hard to co-write and also with no JSON schema very hard to validate. It should be easy to know the standards but also grow them without affecting other standards.
+We want Lens to be a community run project with standards shaped by everyone, with the way metadata was set out before this was hard to co-write and also with no JSON schema very hard to validate. It should be easy to know the standards but also grow them without affecting other standards.
 
 ## Specification
 

LIPs/lip-3.md

@@ -57,7 +57,7 @@ An example:
 }
 ```
 
-The `:handle` and `:id` tokens represent placeholder for where the app expect Profile handles and Publication Ids. The specification could be extended to support Profile Ids if need to.
+The `:handle` and `:id` tokens represent placeholder for where the app expects Profile handles and Publication Ids. The specification could be extended to support Profile Ids if need to.
 
 The app manifest should be submitted as PRs to the registry repository and there should be a process in place to validate and approve new apps. See proposed [schema](../supported-standards/lens-share/app-manifest-schema.json).
 

LIPs/lip-4.md

@@ -57,7 +57,7 @@ The user can enable the Profile Guardian back by executing `enableTokenGuardian`
 
 ### 3. Profile Guardian does not apply to non-EOA addresses
 
-Non-EOA addresses are not affected by this safety layer in order to avoid issues with smart contracts (e.g. NFT protocols or smart wallets) that expect the default plain ERC-721 behaviour. Non-EOA adresses have a higher safety assumption as significant amount of the non-EOAs are multisigs, DAOs or protocols that have a higher threshold of observation from the users and are assumed to remain less affected.
+Non-EOA addresses are not affected by this safety layer in order to avoid issues with smart contracts (e.g. NFT protocols or smart wallets) that expect the default plain ERC-721 behaviour. Non-EOA addresses have a higher safety assumption as significant amount of the non-EOAs are multisigs, DAOs or protocols that have a higher threshold of observation from the users and are assumed to remain less affected.
 
 ### 4. Lens ecosystem support
 

LIPs/lip-5.md

@@ -17,7 +17,7 @@ Earlier this week, a conversation on Farcaster made strides on Lens, which comme
 
 ## Specification and Rationale
 
-While it is time for Lens to open, it should be in a healthy progression towards decentralization. The Lens core team should look to do this by putting in safety measures for when it goes permissionless to combat the risk of spam. Front ends should have their own measures to mitigate risks associated with a large influx of users. As for the opening, @defispartan suggested anyone who can pay the gas to mint a profile should have the right to do so to make Lens as permissionsless as possible. Also, I suggest that there also should be a small nominal fee for a specific handle. Handles are optional as the profile is what holds all of the user’s social graph; however, purchasing handles could be the initial funding mechanism to sponsor transactions on Momoka. Additionally, as @defispartan suggested profiles should be included into the subsidized fees program based on well intentioned engagement, an example of how this would work would be using a floating/community based threshold of the reputation score from Big Query for subsidized posting. Furthermore, Lens should have an unbiased - permissionless way to open up the protocol, with reasonable measures in place, and a strategic plan for subsidizing fees for profiles.
+While it is time for Lens to open, it should be in a healthy progression towards decentralization. The Lens core team should look to do this by putting in safety measures for when it goes permissionless to combat the risk of spam. Front ends should have their own measures to mitigate risks associated with a large influx of users. As for the opening, @defispartan suggested anyone who can pay the gas to mint a profile should have the right to do so to make Lens as permissionless as possible. Also, I suggest that there also should be a small nominal fee for a specific handle. Handles are optional as the profile is what holds all of the user’s social graph; however, purchasing handles could be the initial funding mechanism to sponsor transactions on Momoka. Additionally, as @defispartan suggested profiles should be included into the subsidized fees program based on well intentioned engagement, an example of how this would work would be using a floating/community based threshold of the reputation score from Big Query for subsidized posting. Furthermore, Lens should have an unbiased - permissionless way to open up the protocol, with reasonable measures in place, and a strategic plan for subsidizing fees for profiles.
 
 ## Copyright
 

README.md

@@ -17,8 +17,8 @@ We have different types of proposals which currently are:
 - Lens Metadata Standard
 - Lens Open Algorithm Standard
 
-All of these can go through an LIP process. Lens Open Algorithm Standards are the only ones that are not required to go through the LIP process as has its own flow. That said if you want to improve that standards an LIP can be opened for it.
+All of these can go through an LIP process. Lens Open Algorithm Standards are the only ones that are not required to go through the LIP process as has its own flow. That said if you want to improve the standards an LIP can be opened for it.
 
 ## Supported standards
 
-You can see all the supported standards which that are supported and shaped by LIPs [here](./supported-standards/README.md).
+You can see all the supported standards that are supported and shaped by LIPs [here](./supported-standards/README.md).