Fix typos

developer-workflow/c-api.rst

@@ -104,7 +104,7 @@ This helps us ensure *newly added* API is consistent and maintainable.
 
 Also check with the C API WG before requiring a C feature not present in C99.
 While the *public* docs only promise compatibility with C11, in practice
-we only intruduce C11 features individually as needed.
+we only introduce C11 features individually as needed.
 
 .. _decisions repo: https://github.com/capi-workgroup/decisions/issues
 

developer-workflow/extension-modules.rst

@@ -574,7 +574,7 @@ Now that the configuration is in place, it remains to compile the project:
   :mod:`!_foo` discoverable and importable via ``import _foo``.
 
 * The final ``make`` step is generally not needed since the previous ``make``
-  invokations may completely rebuild the project, but it could be needed in
+  invocations may completely rebuild the project, but it could be needed in
   some specific cases.
 
 Troubleshooting

documentation/devguide.rst

@@ -22,7 +22,7 @@ lives in a `separate repository`_ and bug reports should be submitted to the
 Changes to the Developer's Guide are published when pull requests are merged.
 
 Changes to the Python documentation are published regularly,
-ususally within 48 hours of the change being committed.
+usually within 48 hours of the change being committed.
 The documentation is also `published for each release <https://docs.python.org/release/>`__,
 which may also be used by redistributors.