From 1268e49b7cba3b2e1d4425a0b7c19ef377a5f186 Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Fri, 12 Dec 2025 00:13:44 +0200 Subject: [PATCH] Fix typos --- developer-workflow/c-api.rst | 2 +- developer-workflow/extension-modules.rst | 2 +- documentation/devguide.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/developer-workflow/c-api.rst b/developer-workflow/c-api.rst index c65e88ce1..b68a891b0 100644 --- a/developer-workflow/c-api.rst +++ b/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 diff --git a/developer-workflow/extension-modules.rst b/developer-workflow/extension-modules.rst index fa4c11868..4d8c0ffca 100644 --- a/developer-workflow/extension-modules.rst +++ b/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 diff --git a/documentation/devguide.rst b/documentation/devguide.rst index 9f2ada23c..fc12c369f 100644 --- a/documentation/devguide.rst +++ b/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 `__, which may also be used by redistributors.