seccomp_unotify.2: Minor fixes

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man2/seccomp_unotify.2 b/man2/seccomp_unotify.2
index bded82f8b18a94482f22f61c5349b6e1ca12f352..1cc9d8ea2906196bd791d1d235926ba685efe5c5 100644 (file)
--- a/man2/seccomp_unotify.2
+++ b/man2/seccomp_unotify.2
@@ -226,7 +226,7 @@ a value that will be assigned to the
 variable of the target.
 .IP
 The response is sent using the
-.B SECCOMP_IOCTL_NOTIF_RECV
+.B SECCOMP_IOCTL_NOTIF_SEND
 .BR ioctl (2)
 operation, which is used to transmit a
 .I seccomp_notif_resp
@@ -342,7 +342,7 @@ structure that was passed to the call contained nonzero fields.
 .B ENOENT
 The target thread was killed by a signal as the notification information
 was being generated,
-or the target's system call was interrupted by a signal handler.
+or the target's (blocked) system call was interrupted by a signal handler.
 .RE
 .\" FIXME
 .\" From my experiments,
@@ -395,7 +395,7 @@ The returned
 .I seccomp_notif
 contains the TID of the target thread (in the
 .I pid
-filed of the structure).
+field of the structure).
 .IP 2.
 The target terminates.
 .IP 3.
@@ -407,7 +407,7 @@ The supervisor
 the
 .IR /proc/[tid]/mem
 file for the TID obtained in step 1, with the intention of (say)
-inspecting the memory location(s) that containiing the argument(s) of
+inspecting the memory location(s) that containing the argument(s) of
 the system call that triggered the notification in step 1.
 .RE
 .IP
@@ -477,7 +477,7 @@ This is the value that will be used as the error number
 for a spoofed error return for the target's system call; see below.
 .TP
 .I flags
-This is a bit mask that includes zero or more of the following flags
+This is a bit mask that includes zero or more of the following flags:
 .RS
 .TP
 .BR SECCOMP_USER_NOTIF_FLAG_CONTINUE " (since Linux 5.5)"