Fix: typos

creators/collection-guidelines.md

@@ -5,7 +5,7 @@ coverY: 0
 
 # Collection Guidelines
 
-Since NFTs are so new, there’s little guidance on what makes a great NFT. We’re still incredibly early, and the full potential of NFTs have yet to be realized.
+Since NFTs are so new, there’s little guidance on what makes a great NFT. We’re still incredibly early, and the full potential of NFTs has yet to be realized.
 
 Although NFTs are a new medium, there are a few criteria that will make collections more straightforward to launch on Stargaze.
 
@@ -14,7 +14,7 @@ Here’s some guidelines. These aren’t rules that are set in stone. Rather, so
 1. Do some market analysis to determine the optimal price and size of your collection. The Cosmos community isn't as large as Ethereum, so a 1,000 NFT collection may perform better than a 10,000 NFT collection. Strive for quality over quantity.
 2. Stick to digital-only. NFTs are inherently digital-native. The media is often created digitally and uploaded to IPFS. NFT collectors are often only represented by a Stargaze address and may not even be a physical entity. Physical items are problematic because there might not be a physical address associated with a collector. There are also complications with transferability. For example, what happens when the physical version is sold? Does the NFT have an independent value from the physical item? Until these issues are resolved, it’s simplest to stick to digital-only NFTs.
 3. Refrain from using text in your art. NFT art is ideally designed to be universal and timeless. You are storing it on an immutable ledger after all. For example, English sentences in NFTs won’t be localized to other languages. So it’s best to avoid written language and stick to art. Save written text for metadata.
-4. Make liberal use of metadata. Computers can’t read art, but they can read metadata. Metadata traits enables formulating rarity scores for your NFT. Traders use these attributes to compare NFT valuations.
+4. Make liberal use of metadata. Computers can’t read art, but they can read metadata. Metadata traits enable formulating rarity scores for your NFT. Traders use these attributes to compare NFT valuations.
 5. Create the highest resolution version of the art that you can. 
 
 {% hint style="info" %}

creators/create-stargaze-multisig.md

@@ -154,7 +154,7 @@ Often you want to do more than just send tokens! Here are some other transaction
 
 ### Staking
 
-You'll want to stake you multisig assets to earn staking rewards. Figure out which validator you want to delegate to from the [list of validators](https://app.stargaze.zone/stake) and use their address where it says `<validator-address>`. For example, `starsvaloper1jxv0u20scum4trha72c7ltfgfqef6nscdghxyx`.
+You'll want to stake your multisig assets to earn staking rewards. Figure out which validator you want to delegate to from the [list of validators](https://app.stargaze.zone/stake) and use their address where it says `<validator-address>`. For example, `starsvaloper1jxv0u20scum4trha72c7ltfgfqef6nscdghxyx`.
 
 ```
 starsd tx staking delegate <validator-address> 500000000000ustars --from $(starsd keys multisig -a) --generate only > tx.json

developers/cosmwasm-smart-contracts.md

@@ -16,7 +16,7 @@ Without going through governance, it would be easy to upload a malicious contrac
 ### How do I write a contract that works with Stargaze?
 
 1. Write your contract, deploy it on [testnet](https://testnet.publicawesome.dev/marketplace), and make sure it works as intended.
-2. If the contract charges any fees, be sure to take advantage of Stargaze’s Developer Royalties. Developer Royalties enables developers to earn 50% of all fees that go through their custom contracts.
+2. If the contract charges any fees, be sure to take advantage of Stargaze’s Developer Royalties. Developer Royalties enable developers to earn 50% of all fees that go through their custom contracts.
 3. Submit a [Commonwealth](https://gov.stargaze.zone) post, explaining what your contract does, with a link to the source code. Smart contracts on Stargaze are required to be open source. Non-contract code such as frontend and backend may be private.
 4. Contact the Core Team for a review and audit of your code.
 5. After validating the project with the community and team, submit a governance proposal with the contract code. See the following command to submit your proposal: `starsd tx gov submit-proposal wasm-store -h`.

governance/marketplace.md

@@ -5,7 +5,7 @@ coverY: 0
 
 # Marketplace
 
-Marketplace is a community-owned contract that allows Stargaze stakeholders to decide on how it is goverened. They can vote to change any of the parameters below.
+Marketplace is a community-owned contract that allows Stargaze stakeholders to decide on how it is governed. They can vote to change any of the parameters below.
 
 #### Listing Fee