Fix typos

Author: hugovk

docs/monthly-meeting/2022-04.md

@@ -114,7 +114,7 @@ Discussion outside the meeting should be on the issues :)
 
 ### Bringing in new people
 
-- When “herding cats”, play into people's exixting strengths/interests
+- When “herding cats”, play into people's existing strengths/interests
 - Give people smaller, manageable tasks.
   - [ ] **Petr**: think about how to generate manageable tasks
 

docs/monthly-meeting/2023-06.md

@@ -36,7 +36,7 @@ Regrets:
 ## Reports and celebrations
 
 * [CAM and Erlend's PyCon US talk is now up](https://youtu.be/nMekFX2CDVk)
-    * CAM also pressented a derived version at his local Huntsville Python Users Group (HSV.py)
+    * CAM also presented a derived version at his local Huntsville Python Users Group (HSV.py)
 
 * PEPs site updated for better readability and performance: [python/peps#3132](https://github.com/python/peps/pull/3132)
 

docs/monthly-meeting/2023-08.md

@@ -51,7 +51,7 @@ Please take a second to read through it!
 - [Hugo] Dark theme deploy: 3.11 RM Pablo said fine to deploy. To deploy, need to merge [python/docsbuild-scripts#161](https://github.com/python/docsbuild-scripts/pull/161) and/or pin in `requirements.txt`
 
 - [CAM] Update on structured deprecation work
-    - Originaly prompted by [a recent Discourse thread on soft deprecations](https://discuss.python.org/t/formalize-the-concept-of-soft-deprecation-dont-schedule-removal-in-pep-387-backwards-compatibility-policy/27957/73)
+    - Originally prompted by [a recent Discourse thread on soft deprecations](https://discuss.python.org/t/formalize-the-concept-of-soft-deprecation-dont-schedule-removal-in-pep-387-backwards-compatibility-policy/27957/73)
     - Went through many iterations of design and testing on examples
     - Wrote up a [detailed design doc](https://hackmd.io/@CAM-Gerlach/BJuLFRLj2) with:
         - Rationale and benefits

docs/monthly-meeting/2023-09.md

@@ -74,7 +74,7 @@ Please take a second to read through it!
   - Next steps: CAM to write to Deb from the PSF with a summary of this discussion
 
 - [Maciej] Translations platform – trying to initiate discussion ([Discourse thread](https://discuss.python.org/t/docs-translation-platform/29940))
-  - Transifex has cut off shared memory (between projects) for open source tier, Rafael from Brazilian Portugese team implemented a workaround
+  - Transifex has cut off shared memory (between projects) for open source tier, Rafael from Brazilian Portuguese team implemented a workaround
   - Weblate – based on Django, open license, used by PyPI
   - The POC of Python docs translations/Weblate integration is functional, I'm working on improving it
   - Python docs don't fit into free open source tier on Weblate – the initial proposition is 1500€/year (50% discount)

docs/monthly-meeting/2024-02.md

@@ -75,7 +75,7 @@ Please take a second to read through it!
 - [Carol] Improving clarity around HOWTO docs: https://github.com/python/cpython/issues/114976
 
   [CAM] Could you explain what the older-style howtos were?
-  [Carol] It goes back to Linux in the early days, when docs were scarce. Howtos were architecture discussions of how sonething was implemented, more like background on a topic -- explanations in Diátaxis terms
+  [Carol] It goes back to Linux in the early days, when docs were scarce. Howtos were architecture discussions of how something was implemented, more like background on a topic -- explanations in Diátaxis terms
   [Ned] Maybe the section could be called "longer writings"
   [Daniele] I always call them *howto guides*: `HOWTO` sounds like an old-school passcode
   [Carol] Could we use local ToC trees to split up the section?

docs/monthly-meeting/2024-03.md

@@ -90,10 +90,10 @@ Please take a second to read through it!
   - Hugo: I think it's good.
   - Erlend: One aspect is that this simplifies writing the description. It's more normalized so there isn't so much space for discussion.
   - Petr: Maybe we could get a graphic designer comment on the theme.
-    - Hugo: Tania Allard has offered to help with an accessibilty audit which could help
+    - Hugo: Tania Allard has offered to help with an accessibility audit which could help
   - Ned: There are disparate styles: `str` is monospace, *code object* is italic
   - CAM: We had a big discussion about how to style `None`; decision was to use monospace but not link it. There are differences in the markup too.
-  - Ned: Should we link `str` and `dict`? We could just use monospace. Sometimes, the docs canbe over-linked.
+  - Ned: Should we link `str` and `dict`? We could just use monospace. Sometimes, the docs can be over-linked.
   - CAM: it's important to distinguish names that exist in Python.
   - Carol: Let's ask a UI expert.
   - (...)