fix: typos (#4439)

CONTRIBUTING.md

@@ -22,7 +22,7 @@ the process works smoothly and your contributions can be merged as quickly and e
 ## Issues
 
 - Issues should be used to open a discussion about something that you want to see changed.
-- Please tag individual maintainers if you would like thier input. If you don't know which maintainer to tag, just tag
+- Please tag individual maintainers if you would like their input. If you don't know which maintainer to tag, just tag
   @UMAprotocol/eng.
 - To make a change, add a feature, or fix a bug, one should start by opening an issue briefly describing what should be
   changed and why.
@@ -41,7 +41,7 @@ the process works smoothly and your contributions can be merged as quickly and e
   auto-select a second.
 - If you make updates and would like another round of reviews, use the cycle icon next to the reviewers names to
   request a follow-up review.
-- PRs should be narrow and focused. Making multiple, unrelated changes in the same PR makes things difficult on reviewers
+- PRs should be narrow and focused. Making multiple, unrelated changes in the same PR makes things difficult for reviewers
   and can often slow PR progress. If this is the case, you may be asked to split the PR up.
 - PRs must get approval from _at least_ one maintainer. However, it is considered best practice to make sure all
   comments are completely resolved before merging.

MAINTAINING.md

@@ -16,9 +16,9 @@ actively triaged for consideration and review. This document outlines the respon
   - If the PR has stalled, determine whose action is needed and tag them in a comment (or re-request a review if it's
     the reviewer). If a 3rd party's PR is ready and passing tests, merge it.
   - DCO is a common problem for many users, please help them by pointing them to the
-    [DCO docs](https://github.com/apps/dco). Note: DCO checks can be overriden for UMA org members because DCO is covered
+    [DCO docs](https://github.com/apps/dco). Note: DCO checks can be overridden for UMA org members because DCO is covered
     by other agreements, but 3rd party developers _must_ sign off on their commits.
   - For the full PR process, see [the contributing guidelines](./CONTRIBUTING.md).
 - For each _new_ issue:
-  - If it's a 3rd party issue, traige by assigning or tagging a relevant UMA team member.
+  - If it's a 3rd party issue, triage by assigning or tagging a relevant UMA team member.
   - If it was posted by an UMA org member, no action is required.

README.md

@@ -116,8 +116,8 @@ yarn lint
 
 ### Packages 📦
 
-Because this repo is a monorepo, it conatains many different npm packages. More will be discussed about these packages in the
-following sections. However, the basic structure is that each pacakge is listed in the `packages/` directory. Each package has
+Because this repo is a monorepo, it contains many different npm packages. More will be discussed about these packages in the
+following sections. However, the basic structure is that each package is listed in the `packages/` directory. Each package has
 its own scripts and dependencies and operates (mostly) independently from the others.
 
 ### Adding dependencies 👩‍👦