From a0c49d5d8e1d0fc3db9ded628b1bddb6fedd89da Mon Sep 17 00:00:00 2001 From: Marco Casaroli Date: Wed, 14 Oct 2026 15:26:23 +0200 Subject: [PATCH] Documentation/cancellation_points: Fix two codespell errors. codespell reports "Cancelation" and "cancelability" in cancellation_points.rst. The check job runs codespell on every file that a commit in its range touches, so every pull request whose range includes the last change of this file fails. Use "Cancellation" in the title and "re-enable cancellation" in the note. Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Marco Casaroli --- Documentation/os/scheduling/cancellation_points.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/os/scheduling/cancellation_points.rst b/Documentation/os/scheduling/cancellation_points.rst index 8ddd258ff824a..5f32b8ebbd5d4 100644 --- a/Documentation/os/scheduling/cancellation_points.rst +++ b/Documentation/os/scheduling/cancellation_points.rst @@ -27,8 +27,8 @@ of interface functions. Those interface functions are listed here: http://OpenGroup.org. -Enter and Leave Cancelation Point -================================= +Enter and Leave Cancellation Point +================================== In NuttX, each of these functions ``CONFIG_CANCELLATION_POINTS=y`` will enable a special call to ``enter_cancellation_point()`` at the beginning @@ -65,7 +65,7 @@ kill the thread immediately. .. note:: For pthreads, the cancelable state is controlled by the interface ``pthread_setcancelstate().`` This allows the pthread to disable or - re-enable cancelability. If the thread is not cancelable when + re-enable cancellation. If the thread is not cancelable when ``pthread_cancel()`` is called, it will never do more than just mark the cancellation as pending. When the cancelable state is re-enabled, then any pending cancellation will take effect.