Fix some typos (#1007)

Author: jdufresne

getting-started/setup-building.rst

@@ -98,7 +98,7 @@ You will only need to execute these steps once per machine:
       upstream
 
 For more information about these commands see
-:ref:`Git Bootcamp and Cheat Sheat <git-boot-camp>`.
+:ref:`Git Bootcamp and Cheat Sheet <git-boot-camp>`.
 
 If you did everything correctly, you should now have a copy of the code
 in the ``cpython`` directory and two remotes that refer to your own GitHub fork
@@ -300,7 +300,7 @@ from the dropdown menus in the toolbar.
    If you need to change the build configuration or platform,
    build once with the ``build.bat`` script set to those options first
    before building with them in VS to ensure all files are rebuilt properly,
-   or you may encouter errors when loading modules that were not rebuilt.
+   or you may encounter errors when loading modules that were not rebuilt.
 
    Avoid selecting the ``PGInstrument`` and ``PGUpdate`` configurations,
    as these are intended for PGO builds and not for normal development.

triage/triage-team.rst

@@ -90,7 +90,7 @@ transition into becoming a Python triager. They can request this to any core
 developer, either confidentially via a DM in Discourse, or
 publicly by opening an `issue in the core-workflow repository
 <https://github.com/python/core-workflow/issues/new?template=triage_membership.md>`_.
-If the core devloper decides you are ready to gain the extra privileges on the
+If the core developer decides you are ready to gain the extra privileges on the
 tracker, they will ask a :ref:`Python organization admin <current owners>`
 to invite you to the Python organisation, and then  act as a mentor to you until
 you are ready to do things entirely on your own.