docs: various pages: Use "system call" not "syscall"

A minor wording fix...

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

5 files changed, 9 insertions, 8 deletions

diff --git a/misc-utils/kill.1 b/misc-utils/kill.1
index d638ead6c0..e7e2b6ba50 100644
--- a/misc-utils/kill.1
+++ b/misc-utils/kill.1
@@ -112,7 +112,7 @@ then it can obtain this data via the si_sigval field of the siginfo_t structure.
 It is not possible to send a signal to an explicitly selected thread in a
 multithreaded process using the
 .BR kill (2)
-syscall.  If
+system call.  If
 .BR kill (2)
 is used to send a signal to a thread group, then the kernel selects an arbitrary
 member of the thread group that has not blocked the signal.  For more details
@@ -122,7 +122,7 @@ the CLONE_THREAD description.
 .PP
 The command
 .BR kill (1)
-as well as syscall
+as well as system call
 .BR kill (2)
 accept a TID (thread ID, see
 .BR gettid (2))
diff --git a/sys-utils/mount.8 b/sys-utils/mount.8
index beef62233a..9f7dbde837 100644
--- a/sys-utils/mount.8
+++ b/sys-utils/mount.8
@@ -358,7 +358,8 @@ For example:
 .RE
 
 This feature is not supported by the Linux kernel; it is implemented in userspace
-by an additional \fBmount\fR(2) remounting syscall.  This solution is not atomic.
+by an additional \fBmount\fR(2) remounting system call.
+This solution is not atomic.
 
 The alternative (classic) way to create a read-only bind mount is to use the remount
 operation, for example:
@@ -452,11 +453,11 @@ specified on the command line.
 Note that the Linux kernel does not allow to change multiple propagation flags
 with a single
 .BR mount (2)
-syscall, and the flags cannot be mixed with other mount options.
+system call, and the flags cannot be mixed with other mount options.
 
 Since util-linux 2.23 the \fBmount\fR command allows to use several propagation flags
 together and also together with other mount operations.  This feature is EXPERIMENTAL.
-The propagation flags are applied by additional \fBmount\fR(2) syscalls when the
+The propagation flags are applied by additional \fBmount\fR(2) system calls when the
 preceding mount operations were successful.  Note that this use case is not
 atomic.  It is possible to specify the propagation flags in
 .BR fstab (5)
diff --git a/sys-utils/setpriv.1 b/sys-utils/setpriv.1
index 11c28d40f7..383efec376 100644
--- a/sys-utils/setpriv.1
+++ b/sys-utils/setpriv.1
@@ -13,7 +13,7 @@ Sets or queries various Linux privilege settings that are inherited across
 The difference between the commands setpriv and su (or runuser) is that setpriv does
 not use open PAM session and does not ask for password. It's simple non-suid wrapper around
 .B execve
-syscall.
+system call.
 .SH OPTION
 .TP
 .B \-\-clear\-groups
diff --git a/sys-utils/umount.8 b/sys-utils/umount.8
index 1c99b90662..8abfc1b676 100644
--- a/sys-utils/umount.8
+++ b/sys-utils/umount.8
@@ -102,7 +102,7 @@ Force an unmount (in case of an unreachable NFS system).  (Requires kernel
 
 Note that this option does not guarantee that umount command does not hang.
 It's strongly recommended to use absolute paths without symlinks to avoid
-unwanted readlink and stat syscalls on unreachable NFS in umount.
+unwanted readlink and stat system calls on unreachable NFS in umount.
 .TP
 .BR \-i , " \-\-internal\-only"
 Do not call the \fB/sbin/umount.\fIfilesystem\fR helper even if it exists.
diff --git a/sys-utils/unshare.1 b/sys-utils/unshare.1
index dc99944eb7..9479f597c9 100644
--- a/sys-utils/unshare.1
+++ b/sys-utils/unshare.1
@@ -161,7 +161,7 @@ namespace (\fB\-\-mount\fP) is not requested.
 .BR "\-\-setgroups allow" | deny
 Allow or deny the
 .BR setgroups (2)
-syscall in a user namespace.
+system call in a user namespace.
 .sp
 To be able to call
 .BR setgroups (2),