intro.1, gettimeofday.2, mkdir.2, nice.2, setresuid.2, stime.2, adjtime.3, getttyent.3, proc.5: tfix

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

man1/intro.1

@@ -50,7 +50,7 @@ Linux is a flavor of UNIX, and as a first approximation
 all user commands under UNIX work precisely the same under
 Linux (and FreeBSD and lots of other UNIX-like systems).
 .LP
-Under Linux there are GUIs (graphical user interfaces), where you
+Under Linux, there are GUIs (graphical user interfaces), where you
 can point and click and drag, and hopefully get work done without
 first reading lots of documentation.
 The traditional UNIX environment

man2/gettimeofday.2

@@ -117,7 +117,7 @@ structure is obsolete; the
 argument should normally be specified as NULL.
 (See NOTES below.)
 
-Under Linux there are some peculiar "warp clock" semantics associated
+Under Linux, there are some peculiar "warp clock" semantics associated
 with the
 .BR settimeofday ()
 system call if on the very first call (after booting)

man2/mkdir.2

@@ -209,7 +209,7 @@ SVr4, BSD, POSIX.1-2001, POSIX.1-2008.
 .BR mkdirat ():
 POSIX.1-2008.
 .SH NOTES
-Under Linux apart from the permission bits, only the
+Under Linux, apart from the permission bits, only the
 .B S_ISVTX
 mode bit is honored.
 That is, under Linux the created directory actually gets mode

man2/nice.2

@@ -65,7 +65,7 @@ The calling process attempted to increase its priority by
 supplying a negative
 .I inc
 but has insufficient privileges.
-Under Linux the
+Under Linux, the
 .B CAP_SYS_NICE
 capability is required.
 (But see the discussion of the

man2/setresuid.2

@@ -108,7 +108,7 @@ they also appear on HP-UX and some of the BSDs.
 .SH NOTES
 Under HP-UX and FreeBSD, the prototype is found in
 .IR <unistd.h> .
-Under Linux the prototype is provided by glibc since version 2.3.2.
+Under Linux, the prototype is provided by glibc since version 2.3.2.
 
 The original Linux
 .BR setresuid ()

man2/stime.2

@@ -62,7 +62,7 @@ Error in getting information from user space.
 .TP
 .B EPERM
 The calling process has insufficient privilege.
-Under Linux the
+Under Linux, the
 .B CAP_SYS_TIME
 privilege is required.
 .SH CONFORMING TO

man3/adjtime.3

@@ -99,7 +99,7 @@ is outside the permitted range.
 .TP
 .B EPERM
 The caller does not have sufficient privilege to adjust the time.
-Under Linux the
+Under Linux, the
 .B CAP_SYS_TIME
 capability is required.
 .SH ATTRIBUTES

man3/getttyent.3

@@ -90,7 +90,7 @@ so it is not thread-safe.
 Not in POSIX.1-2001.
 Present on the BSDs, and perhaps other systems.
 .SH NOTES
-Under Linux the file
+Under Linux, the file
 .IR /etc/ttys ,
 and the functions described above, are not used.
 .SH SEE ALSO

man5/proc.5

@@ -266,7 +266,7 @@ are not available if the main thread has already terminated
 (typically by calling
 .BR pthread_exit (3)).
 
-Under Linux 2.0 and earlier
+Under Linux 2.0 and earlier,
 .I /proc/[pid]/exe
 is a pointer to the binary which was executed,
 and appears as a symbolic link.
@@ -671,7 +671,7 @@ short of running it through
 .BR strace (1),
 or similar.
 
-Under Linux 2.0 there is no field giving pathname.
+Under Linux 2.0, there is no field giving pathname.
 .TP
 .I /proc/[pid]/mem
 This file can be used to access the pages of a process's memory through
@@ -3641,7 +3641,7 @@ with
 .B MAP_NORESERVE
 are not checked, and the default check is very weak,
 leading to the risk of getting a process "OOM-killed".
-Under Linux 2.4 any nonzero value implies mode 1.
+Under Linux 2.4, any nonzero value implies mode 1.
 In mode 2 (available since Linux 2.6), the total virtual address space
 on the system is limited to (SS + RAM*(r/100)),
 where SS is the size of the swap space, and RAM