1 files changed, 21 insertions, 21 deletions
diff --git a/man7/attributes.7 b/man7/attributes.7
index 580ebfe868..fdf91e1c0f 100644
--- a/man7/attributes.7
+++ b/man7/attributes.7
@@ -85,7 +85,7 @@ safe for inlining.
 .\" .I AC-Safe
 .\" .I AC-Safe
 .\" or Async-Cancel-Safe functions are safe to call when
-.\" asynchronous cancellation is enabled.
+.\" asynchronous cancelation is enabled.
 .\" AC in AC-Safe stands for Asynchronous Cancellation.
 .\"
 .\" The POSIX standard defines only three functions to be AC-Safe, namely
@@ -99,10 +99,10 @@ safe for inlining.
 .\" This documentation is provided for use
 .\" by the GNU C Library developers.
 .\"
-.\" Just like signal handlers, cancellation cleanup routines must configure
+.\" Just like signal handlers, cancelation cleanup routines must configure
 .\" the floating point environment they require.
 .\" The routines cannot assume a floating point environment,
-.\" particularly when asynchronous cancellation is enabled.
+.\" particularly when asynchronous cancelation is enabled.
 .\" If the configuration of the floating point
 .\" environment cannot be performed atomically then it is also possible that
 .\" the environment encountered is internally inconsistent.
@@ -174,7 +174,7 @@ Other keywords that appear in safety notes are defined in subsequent sections.
 .\" AS-Unsafe features in this section indicate the functions are never safe
 .\" to call when asynchronous signals are enabled.
 .\" AC-Unsafe features
-.\" indicate they are never safe to call when asynchronous cancellation is
+.\" indicate they are never safe to call when asynchronous cancelation is
 .\" .\" enabled.
 .\" There are no MT-Unsafe marks in this section.
 .\" .TP
@@ -190,7 +190,7 @@ Other keywords that appear in safety notes are defined in subsequent sections.
 .\" .I lock
 .\" as an AC-Unsafe feature may, if canceled asynchronously,
 .\" fail to release a lock that would have been released if their execution
-.\" had not been interrupted by asynchronous thread cancellation.
+.\" had not been interrupted by asynchronous thread cancelation.
 .\" Once a lock is left taken,
 .\" attempts to take that lock will block indefinitely.
 .\" .TP
@@ -319,7 +319,7 @@ Other keywords that appear in safety notes are defined in subsequent sections.
 .\" AS-Unsafe, because calling them in signal handlers may interfere with
 .\" timers set in the interrupted code, and AC-Unsafe,
 .\" because there is no safe way to guarantee an earlier timer
-.\" will be reset in case of asynchronous cancellation.
+.\" will be reset in case of asynchronous cancelation.
 .\"
 .\"
 .SS Conditionally safe features
@@ -366,7 +366,7 @@ the function can then be safely called after other threads are started.
 .\" .I init
 .\" as an AS-Safety or AC-Unsafe feature should ensure
 .\" the initialization is performed
-.\" before configuring signal handlers or enabling cancellation,
+.\" before configuring signal handlers or enabling cancelation,
 .\" so that the AS-Safety and AC-Safety issues related with
 .\" .I libc_once
 .\" do not arise.
@@ -565,16 +565,16 @@ blocking that signal before the call and resetting its
 handler afterwards is recommended.
 .\"
 .\" There is no safe way to guarantee the original signal handler is
-.\" restored in case of asynchronous cancellation,
+.\" restored in case of asynchronous cancelation,
 .\" therefore so-marked functions are also AC-Unsafe.
 .\"
-.\" .\" fixme: at least deferred cancellation should get it right, and would
+.\" .\" fixme: at least deferred cancelation should get it right, and would
 .\" .\" obviate the restoring bit below, and the qualifier above.
 .\"
 .\" Besides the measures recommended to work around the
 .\" MT-Safety and AS-Safety problem,
-.\" in order to avert the cancellation problem,
-.\" disabling asynchronous cancellation
+.\" in order to avert the cancelation problem,
+.\" disabling asynchronous cancelation
 .\" .I and
 .\" installing a cleanup handler to restore the signal to the desired state
 .\" and to release the mutex are recommended.
@@ -616,13 +616,13 @@ even if referenced by different file descriptors.
 .\" restore terminal settings to their original state,
 .\" after temporarily changing them, but they may fail to do so if canceled.
 .\"
-.\" .\" fixme: at least deferred cancellation should get it right, and would
+.\" .\" fixme: at least deferred cancelation should get it right, and would
 .\" .\" obviate the restoring bit below, and the qualifier above.
 .\"
 .\" Besides the measures recommended to work around the
 .\" MT-Safety and AS-Safety problem,
-.\" in order to avert the cancellation problem,
-.\" disabling asynchronous cancellation
+.\" in order to avert the cancelation problem,
+.\" disabling asynchronous cancelation
 .\" .I and
 .\" installing a cleanup handler to
 .\" restore the terminal settings to the original state and to release the
@@ -733,7 +733,7 @@ which makes the former safe.
 .\" Functions annotated with
 .\" .I fd
 .\" as an AC-Safety issue may leak file
-.\" descriptors if asynchronous thread cancellation interrupts their
+.\" descriptors if asynchronous thread cancelation interrupts their
 .\" execution.
 .\"
 .\" Functions that allocate or deallocate file descriptors will generally be
@@ -755,7 +755,7 @@ which makes the former safe.
 .\" reallocated by another thread or signal handler.
 .\"
 .\" Such leaks could be internally avoided, with some performance penalty,
-.\" by temporarily disabling asynchronous thread cancellation.
+.\" by temporarily disabling asynchronous thread cancelation.
 .\" However,
 .\" since callers of allocation or deallocation functions would have to do
 .\" this themselves, to avoid the same sort of leak in their own layer,
@@ -768,26 +768,26 @@ which makes the former safe.
 .\" However, cumulative effects of such leaks may pose a
 .\" problem for some programs.
 .\" If this is the case,
-.\" suspending asynchronous cancellation for the duration of calls
+.\" suspending asynchronous cancelation for the duration of calls
 .\" to such functions is recommended.
 .\" .TP
 .\" .I mem
 .\" Functions annotated with
 .\" .I mem
 .\" as an AC-Safety issue may leak
-.\" memory if asynchronous thread cancellation interrupts their execution.
+.\" memory if asynchronous thread cancelation interrupts their execution.
 .\"
 .\" The problem is similar to that of file descriptors: there is no atomic
 .\" interface to allocate memory and store its address in the argument to a
 .\" cleanup handler,
 .\" or to release it and remove its address from that argument,
-.\" without at least temporarily disabling asynchronous cancellation,
+.\" without at least temporarily disabling asynchronous cancelation,
 .\" which these functions do not do.
 .\"
 .\" This remark does not by itself cause a function to be regarded as
 .\" generally AC-Unsafe.
 .\" However, cumulative effects of such leaks may be
-.\" severe enough for some programs that disabling asynchronous cancellation
+.\" severe enough for some programs that disabling asynchronous cancelation
 .\" for the duration of calls to such functions may be required.
 .TP
 .I cwd
@@ -796,7 +796,7 @@ Functions marked with
 as an MT-Safety issue may temporarily
 change the current working directory during their execution,
 which may cause relative pathnames to be resolved in unexpected ways in
-other threads or within asynchronous signal or cancellation handlers.
+other threads or within asynchronous signal or cancelation handlers.
 .IP
 This is not enough of a reason to mark so-marked functions as MT-Unsafe,
 .\" or AS-Unsafe,