This is an automated email from the ASF dual-hosted git repository.
xiaoxiang781216 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/nuttx.git
The following commit(s) were added to refs/heads/master by this push:
new 0121eddcc48 Documentation/cancellation_points: Fix two codespell
errors.
0121eddcc48 is described below
commit 0121eddcc484c2656c8a4d159fa336b4da91fd46
Author: Marco Casaroli <[email protected]>
AuthorDate: Wed Oct 14 15:26:23 2026 +0200
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 <[email protected]>
---
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 8ddd258ff82..5f32b8ebbd5 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.
