Fix typos; avoid passive form

Signed-off-by: Shane Curcuru <asf@shanecurcuru.org>

Author: ShaneCurcuru

content/en/contribute/_index.md

@@ -22,7 +22,7 @@ There are a number of ways you can contribute to this project, which we'll cover
 
 The goal of this glossary is to simplify the Open Source Program Office space and thus make it more accessible to people. 
 
-The OSPO Glossary content is stored in [this GitHub repo](https://github.com/todogorup/glossary) 
+The OSPO Glossary content is stored in [this GitHub repo](https://github.com/todogroup/glossary) 
 where you'll find a list of [issues](https://github.com/todogroup/glossary/issues) and pull requests ([PRs](https://github.com/todogroup/glossary/pulls)).
 ## Who can contribute?
 
@@ -32,7 +32,7 @@ Therefore, to contribute new terms, you must be proficient in them.
 
 That know-how is required because explaining complex concepts in simple words is _really_ hard. And while the digestible, user-friendly outcome may seem easy, achieving the desired simplicity results from hard work and collaboration between cloud native experts. 
 
-If you have never directly engaging with Open Source Program Offices or open source initiatives wihtin organizations yet, but still want to contribute, we recommend teaming up with someone who is. 
+If you have never directly engaging with Open Source Program Offices or open source initiatives within organizations yet, but still want to contribute, we recommend teaming up with someone who is. 
 Once the expert is confident that the term accurately describes the concept, you are ready for your first Glossary contribution.
 
 The localization effort is where beginners proficient in another language can make valuable contributions to the Glossary. 
@@ -63,7 +63,7 @@ You can use labels (e.g., English language, help needed, good first issue) to fi
 
 **Note**: you can start working on an issue after the maintainers assigned it to you. 
 You can only claim one term at a time. 
-Workig on multiple terms is sequential, you must complete a term before claiming the next one.
+Working on multiple terms is sequential, you must complete a term before claiming the next one.
 
 ## Propose new terms {#propose-new-terms}
 

content/en/style-guide/_index.md

@@ -16,7 +16,7 @@ The OSPO Glossary follows the following rules:
 3. [Use literal and concrete language](https://guidetogrammar.org/grammar/composition/abstract.htm)
 4. [Omit contractions](https://en.wikipedia.org/wiki/Contraction_(grammar))
 5. [Use passive voice sparingly](https://www.ef.com/ca/english-resources/english-grammar/passive-voice/)
-6. [Aim to phrase statements in a positive form](https://examples.yourdictionary.com/positive-sentence-examples.html) 
+6. [Phrase statements in a positive form](https://examples.yourdictionary.com/positive-sentence-examples.html) 
 7. [No exclamation marks outside of quotations](https://www.grammarly.com/blog/exclamation-mark/)
 8. Do not exaggerate
 9. Avoid repetition
@@ -91,7 +91,7 @@ status: Feedback Appreciated
 
 The **tag** label follows the status label. 
 For the tags to be meaningful and thus helpful to the user, we will use them in a strict sense. 
-Applying too many tags will only delute its meaning. 
+Applying too many tags will only dilute its meaning. 
 With the exception of "fundamental," which simply indicates this term is needed to understand other cloud native concepts, most terms will likely only have one tag.
 
 **Note**: Please do not introduce new tags unless approved by the maintainers. When you add tags to an entry, ensure they are spelled exactly as listed below (singular, no typos).