acct.2, chmod.2, fcntl.2, mmap.2, mprotect.2, rmdir.2, times.2: tfix

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

man2/acct.2

@@ -125,7 +125,7 @@ is not in fact a directory.
 .TP
 .B EPERM
 The calling process has insufficient privilege to enable process accounting.
-On Linux the
+On Linux, the
 .B CAP_SYS_PACCT
 capability is required.
 .TP

man2/chmod.2

@@ -165,7 +165,7 @@ but this will not cause an error to be returned.
 As a security measure, depending on the filesystem,
 the set-user-ID and set-group-ID execution bits
 may be turned off if a file is written.
-(On Linux this occurs if the writing process does not have the
+(On Linux, this occurs if the writing process does not have the
 .B CAP_FSETID
 capability.)
 On some filesystems, only the superuser can set the sticky bit,

man2/fcntl.2

@@ -207,7 +207,7 @@ and file creation flags
 in
 .I arg
 are ignored.
-On Linux this command can change only the
+On Linux, this command can change only the
 .BR O_APPEND ,
 .BR O_ASYNC ,
 .BR O_DIRECT ,

man2/mmap.2

@@ -680,7 +680,7 @@ wrapper function invokes
 with a suitably adjusted value for
 .IR offset .
 .SH BUGS
-On Linux there are no guarantees like those suggested above under
+On Linux, there are no guarantees like those suggested above under
 .BR MAP_NORESERVE .
 By default, any process can be killed
 at any moment when the system runs out of memory.

man2/mprotect.2

@@ -131,7 +131,7 @@ is unspecified if it is applied to a region of memory that
 was not obtained via
 .BR mmap (2).
 .SH NOTES
-On Linux it is always permissible to call
+On Linux, it is always permissible to call
 .BR mprotect ()
 on any address in a process's address space (except for the
 kernel vsyscall area).

man2/rmdir.2

@@ -57,7 +57,7 @@ did not allow search permission.
 .I pathname
 is currently in use by the system or some process that prevents its
 removal.
-On Linux this means
+On Linux, this means
 .I pathname
 is currently used as a mount point
 or is the root directory of the calling process.

man2/times.2

@@ -166,7 +166,7 @@ not the clock ticks used by
 On Linux, the "arbitrary point in the past" from which the return value of
 .BR times ()
 is measured has varied across kernel versions.
-On Linux 2.4 and earlier this point is the moment the system was booted.
+On Linux 2.4 and earlier, this point is the moment the system was booted.
 Since Linux 2.6, this point is \fI(2^32/HZ) \- 300\fP
 seconds before system boot time.
 This variability across kernel versions (and across UNIX implementations),