aboutsummaryrefslogtreecommitdiffstats
path: root/man3/pthread_setcancelstate.3
diff options
context:
space:
mode:
Diffstat (limited to 'man3/pthread_setcancelstate.3')
-rw-r--r--man3/pthread_setcancelstate.32
1 files changed, 1 insertions, 1 deletions
diff --git a/man3/pthread_setcancelstate.3 b/man3/pthread_setcancelstate.3
index 85af0309ec..1c0de7e3e9 100644
--- a/man3/pthread_setcancelstate.3
+++ b/man3/pthread_setcancelstate.3
@@ -128,7 +128,7 @@ Since the thread could be canceled at
time, it cannot safely reserve resources (e.g., allocating memory with
.BR malloc (3)),
acquire mutexes, semaphores, or locks, and so on.
-Reserving resources is unafe because the application has no way of
+Reserving resources is unsafe because the application has no way of
knowing what the state of these resources is when the thread is canceled;
that is, did cancellation occur before the resources were reserved,
while they were reserved, or after they were released?