aboutsummaryrefslogtreecommitdiffstats
path: root/man7/pthreads.7
diff options
context:
space:
mode:
authorSamanta Navarro <ferivoz@riseup.net>2021-11-24 11:58:58 +0000
committerAlejandro Colomar <alx.manpages@gmail.com>2021-12-18 19:32:51 +0100
commit1f08fc80e4573f8b6356296e511164477b935678 (patch)
treeca414163a142e6675b64dc3a1a208b017ff48904 /man7/pthreads.7
parent79c9fe57dd2164c1c58496034851fc499cc91958 (diff)
downloadman-pages-1f08fc80e4573f8b6356296e511164477b935678.tar.gz
pthread_cancel.3, pthread_cleanup_push_defer_np.3, pthread_setcancelstate.3, pthread_testcancel.3, pthreads.7: tfix
Changed cancellation to cancelation. Signed-off-by: Samanta Navarro <ferivoz@riseup.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Diffstat (limited to 'man7/pthreads.7')
-rw-r--r--man7/pthreads.728
1 files changed, 14 insertions, 14 deletions
diff --git a/man7/pthreads.7 b/man7/pthreads.7
index 6f4f6e763c..380aeb2175 100644
--- a/man7/pthreads.7
+++ b/man7/pthreads.7
@@ -257,17 +257,17 @@ pthread_setcanceltype()
.in
.SS Cancellation points
POSIX.1 specifies that certain functions must,
-and certain other functions may, be cancellation points.
+and certain other functions may, be cancelation points.
If a thread is cancelable, its cancelability type is deferred,
-and a cancellation request is pending for the thread,
+and a cancelation request is pending for the thread,
then the thread is canceled when it calls a function
-that is a cancellation point.
+that is a cancelation point.
.PP
-The following functions are required to be cancellation points by
+The following functions are required to be cancelation points by
POSIX.1-2001 and/or POSIX.1-2008:
.PP
.\" FIXME
-.\" Document the list of all functions that are cancellation points in glibc
+.\" Document the list of all functions that are cancelation points in glibc
.in +4n
.EX
accept()
@@ -331,7 +331,7 @@ writev()
.EE
.in
.PP
-The following functions may be cancellation points according to
+The following functions may be cancelation points according to
POSIX.1-2001 and/or POSIX.1-2008:
.PP
.in +4n
@@ -567,23 +567,23 @@ wscanf()
.in
.PP
An implementation may also mark other functions
-not specified in the standard as cancellation points.
+not specified in the standard as cancelation points.
In particular, an implementation is likely to mark
-any nonstandard function that may block as a cancellation point.
+any nonstandard function that may block as a cancelation point.
(This includes most functions that can touch files.)
.PP
It should be noted that even if an application is not using
-asynchronous cancellation, that calling a function from the above list
+asynchronous cancelation, that calling a function from the above list
from an asynchronous signal handler may cause the equivalent of
-asynchronous cancellation.
+asynchronous cancelation.
The underlying user code may not expect
-asynchronous cancellation and the state of the user data may become
+asynchronous cancelation and the state of the user data may become
inconsistent.
Therefore signals should be used with caution when
-entering a region of deferred cancellation.
-.\" So, scanning "cancellation point" comments in the glibc 2.8 header
+entering a region of deferred cancelation.
+.\" So, scanning "cancelation point" comments in the glibc 2.8 header
.\" files, it looks as though at least the following nonstandard
-.\" functions are cancellation points:
+.\" functions are cancelation points:
.\" endnetgrent
.\" endspent
.\" epoll_pwait