changed spelling of "super-user" to "superuser"

man1/ln.1

@@ -110,7 +110,7 @@ Terminate option list.
 .SH "GNU OPTIONS"
 .TP
 .B "\-d, \-F, \-\-directory"
-Allow the super-user to make hard links to directories.
+Allow the superuser to make hard links to directories.
 .TP
 .B "\-f, \-\-force"
 Remove existing destination files.

man2/bind.2

@@ -126,7 +126,7 @@ is set appropriately.
 .SH ERRORS
 .TP
 .B EACCES
-The address is protected, and the user is not the super-user.
+The address is protected, and the user is not the superuser.
 .TP
 .B EBADF
 .I sockfd

man2/chmod.2

@@ -108,7 +108,7 @@ may be turned off if a file is written.
 (On Linux this occurs if the writing process does not have the
 .B CAP_FSETID
 capability.)
-On some file systems, only the super-user can set the sticky bit,
+On some file systems, only the superuser can set the sticky bit,
 which may have a special meaning.
 For the sticky bit, and for set user ID and set group ID bits on
 directories, see

man2/chown.2

@@ -63,7 +63,7 @@ or
 .I group
 is specified as \-1, then that ID is not changed.
 
-When the owner or group of an executable file are changed by a non-super-user,
+When the owner or group of an executable file are changed by a non-superuser,
 the S_ISUID and S_ISGID mode bits are cleared. POSIX does not specify whether
 this also should happen when root does the
 .IR chown ;

man2/chroot.2

@@ -54,7 +54,7 @@ and does nothing else.
 
 This call does not change the current working directory,
 so that after the call `.' can be outside the tree rooted at `/'.
-In particular, the super-user can escape from a `chroot jail'
+In particular, the superuser can escape from a `chroot jail'
 by doing `mkdir foo; chroot foo; cd ..'.
 
 This call does not close open file descriptors, and such file

man2/getpriority.2

@@ -96,7 +96,7 @@ call returns the highest priority (lowest numerical value)
 enjoyed by any of the specified processes.  The
 .B setpriority
 call sets the priorities of all of the specified processes
-to the specified value.  Only the super-user may lower priorities.
+to the specified value.  Only the superuser may lower priorities.
 .SH "RETURN VALUE"
 Since
 .B getpriority
@@ -139,7 +139,7 @@ and (on Linux systems) the caller did not have the
 capability.
 .TP
 .B EACCES
-A non super-user attempted to lower a process priority.
+A non superuser attempted to lower a process priority.
 .SH NOTES
 The details on the condition for EPERM depend on the system.
 The above description is what SUSv3 says, and seems to be followed on

man2/idle.2

@@ -46,7 +46,7 @@ never returns.
 .PP
 Only process 0 may call
 .BR idle .
-Any user process, even a process with super-user permission,
+Any user process, even a process with superuser permission,
 will receive
 .BR EPERM .
 .SH "RETURN VALUE"

man2/reboot.2

@@ -115,7 +115,7 @@ This means that the CAD keystroke will cause a SIGINT signal to be
 sent to init (process 1), whereupon this process may decide upon a
 proper action (maybe: kill all processes, sync, reboot).
 .LP
-Only the super-user may use this function.
+Only the superuser may use this function.
 .LP
 The precise effect of the above actions depends on the architecture.
 For the i386 architecture, the additional argument does not do

man2/setgid.2

@@ -51,7 +51,7 @@ is set appropriately.
 .SH ERRORS
 .TP
 .B EPERM
-The user is not the super-user (does not have the CAP_SETGID capability), and
+The user is not the superuser (does not have the CAP_SETGID capability), and
 .I gid
 does not match the effective group ID or saved set-group-ID of
 the calling process.

man2/setresuid.2

@@ -44,7 +44,7 @@ real, effective and saved user ID nonzero) may change the real,
 effective and saved user ID, each to one of:
 the current uid, the current effective uid or the current saved uid.
 
-The super-user may set real, effective and saved user ID to arbitrary values.
+The superuser may set real, effective and saved user ID to arbitrary values.
 
 If one of the parameters equals \-1, the corresponding value is not changed.
 

man2/setup.2

@@ -49,7 +49,7 @@ configured into the kernel and then mounts the root file system.
 .PP
 No user process may call
 .BR setup .
-Any user process, even a process with super-user permission,
+Any user process, even a process with superuser permission,
 will receive
 .BR EPERM .
 .SH "RETURN VALUE"

man3/rcmd.3

@@ -58,7 +58,7 @@
 The
 .Fn rcmd
 function
-is used by the super-user to execute a command on
+is used by the superuser to execute a command on
 a remote machine using an authentication scheme based
 on reserved port numbers.
 The
@@ -134,7 +134,7 @@ address bound to it.  This socket is suitable for use
 by 
 .Fn rcmd
 and several other functions.  Privileged Internet ports are those
-in the range 0 to 1023.  Only the super-user
+in the range 0 to 1023.  Only the superuser
 is allowed to bind an address of this sort to a socket.
 .Pp
 The
@@ -143,10 +143,10 @@ and
 .Fn ruserok
 functions take a remote host's IP address or name, respectively,
 two user names and a flag indicating whether the local user's
-name is that of the super-user.
+name is that of the superuser.
 Then, if the user is
 .Em NOT
-the super-user, it checks the
+the superuser, it checks the
 .Pa /etc/hosts.equiv
 file.
 If that lookup is not done, or is unsuccessful, the
@@ -155,7 +155,7 @@ in the local user's home directory is checked to see if the request for
 service is allowed.
 .Pp
 If this file does not exist, is not a regular file, is owned by anyone
-other than the user or the super-user, or is writeable by anyone other
+other than the user or the superuser, or is writeable by anyone other
 than the owner, the check automatically fails.
 Zero is returned if the machine name is listed in the
 .Dq Pa hosts.equiv

man8/ldconfig.8

@@ -87,7 +87,7 @@ allowed.  Also see the
 .B -p
 option.
 .B ldconfig
-should normally be run by the super-user as it may require write
+should normally be run by the superuser as it may require write
 permission on some root owned directories and files.
 .SH OPTIONS
 .TP