Fix typos (#75)

* Fix typos

* Fix stale link

* Bump GitHub Actions

Author: hugovk

.github/workflows/test-build.yaml

@@ -9,10 +9,10 @@ jobs:
 
     steps:
       - name: Check out repository
-        uses: actions/checkout@v2
+        uses: actions/checkout@v3
 
       - name: Set up Python 3
-        uses: actions/setup-python@v2
+        uses: actions/setup-python@v4
         with:
           python-version: '3.x'
           cache: "pip"

docs/monthly-meeting/2022-02.md

@@ -41,7 +41,7 @@ This is a place to make announcements (without a need for discussion). This is a
 >
 >> editor's note: it doesn't work outside HackMD, and has been replaced by [name] in this document
 
-> I've been making a decent amount of progress on the Sphinx theme, and spent some time reading the implemention of https://github.com/python/docsbuild-scripts [Pradyun]
+> I've been making a decent amount of progress on the Sphinx theme, and spent some time reading the implementation of https://github.com/python/docsbuild-scripts [Pradyun]
 
 > Thanks @encukou for kicking this off. :tada: [willingc]
 
@@ -58,7 +58,7 @@ A "guidance document is at the end of the document"
 
 [Carol] We started the group to provide editorial guidance that included non-core devs as well as core devs that lets people contribute.
 
-[Petr] If we come up with guidance, the Docs-WG should probably ratify it. The PSF / SC might need to ratify this. Will have community input, but Docs-WG is teh final arbiters.
+[Petr] If we come up with guidance, the Docs-WG should probably ratify it. The PSF / SC might need to ratify this. Will have community input, but Docs-WG is the final arbiter.
 
 [Julien] Every one of us can review PRs; if 6 of us say this is good, it'll be very hard for people to say "this is my kingdom, don't touch it".
 
@@ -81,7 +81,7 @@ Guidance, like dividing docs into 4 quadrants, would help.
 
 [Carol] Another thing to keep in mind: we can create new docs. e.g. print returns None might be a completely new set of docs. A user could find it with search, but doesn't need to edit the *reference* docs.
 
-[James] Optimising for the audience is indeed relevant. An expereinced dev knows print returns None, but a beginner would miss the information burried in the middle of a paragraph. Targeting for different audiences can make it more optimised for it.
+[James] Optimising for the audience is indeed relevant. An experienced dev knows print returns None, but a beginner would miss the information buried in the middle of a paragraph. Targeting for different audiences can make it more optimised for it.
 
 > Audience is a good point on consumers of documentation.
 
@@ -95,7 +95,7 @@ Guidance, like dividing docs into 4 quadrants, would help.
 
 [Petr] Good to have folks with different experience here.
 
-[CAM] Indeed! It's super valuable in working on documentation to have multiple expereince levels.
+[CAM] Indeed! It's super valuable in working on documentation to have multiple experience levels.
 
 [Petr] Autogeneration is related to the skimming-prose aspects we just discussed -- let's defer that for later.
 
@@ -117,7 +117,7 @@ Even if Docs WG is the place where people submit ideas and others implement them
 
 [Mariatta] Do we need CLA for documentation?
 
-[Julien] We don't have one for the French translation -- just have a nore that all contributions are CC0.
+[Julien] We don't have one for the French translation -- just have a note that all contributions are CC0.
 
 [Petr] That's a question for VanL.
 

docs/monthly-meeting/2022-03.md

@@ -50,7 +50,7 @@ Please take a second to read through it!
 
 ### Python Language Summit @ PyCon US
 
-- If there's any updates/issues that would be relavant to the Python core developers, this would be a good place for presenting that for discussion!
+- If there's any updates/issues that would be relevant to the Python core developers, this would be a good place for presenting that for discussion!
 - Still in planning stage, but worth it to start thinking about it now, if you want to bring up something for discussion.
 - Petr gave a summary of what the event will look like.
   - In-person event, at PyCon US 2022.

docs/monthly-meeting/2022-08.md

@@ -71,7 +71,7 @@ Please take a second to read through it!
     -  Pradyun: PEP is our tool for consensus building.
     -  Hugo: With [PEP 676](https://peps.python.org/pep-0676/): work was done ahead before the PEP, and we didn't really know who was going to make the decision of it, and after the PEP there was more clarity of who makes the decision. 
     -  CAM: a PEP can be design docs or detailed plan, but can also be a rationale. 
-    -  Pradyun: We don't want to put in process that makes it more diffcult for people to contribute.
+    -  Pradyun: We don't want to put in process that makes it more difficult for people to contribute.
 
 ## Next meeting
 

docs/monthly-meeting/2022-11.md

@@ -33,7 +33,7 @@ Please take a second to read through it!
 - Ezio: devguide, [CSV with status of Python branches](https://github.com/python/devguide/pull/884), [OpenGraph metadata for devguide et al.](https://github.com/python/devguide/pull/953), catching up after a busy month
 - Erlend: getting help from Cam on two huge PRs on SQLite docs
 - Hugo: OpenGraph extension on DevGuide, created PR on Sphinx extension to improve SEO, now does `meta description` in addition to `meta og:...`, plus bug fix in `dirhtml` used to generate the pages.
-- Cam: attended core dev sprint, helped a lot of people get things done. Will work on whats new. New Sphinx roles for linking Python source code & GitHub. automate checking if things added in new version is documented, docstrings updated, deprecation tracking.
+- Cam: attended core dev sprint, helped a lot of people get things done. Will work on what's new. New Sphinx roles for linking Python source code & GitHub. automate checking if things added in new version is documented, docstrings updated, deprecation tracking.
 
 ## Agenda items
 

docs/monthly-meeting/2022-12.md

@@ -62,8 +62,8 @@ Please take a second to read through it!
     * e.g.: is it documented outside the PEP? Add a note?
    * @CAM-Gerlach will open an issue to discuss adding checklists for new, Approved/Rejected and Final PEPs (opened as [python/peps#2937](https://github.com/python/peps/issues/2937))
 * Status for PEP 659?
-  * @CAM-Gerlach will open issue proposing a list of obselete PEPs to the SC to be formally rejected
-  * We may need an obselete status?
+  * @CAM-Gerlach will open issue proposing a list of obsolete PEPs to the SC to be formally rejected
+  * We may need an obsolete status?
 
 ### Improve SEO for CPython docs