s/since kernel x.y.z/since Linux s.y.z/

man2/epoll_ctl.2

@@ -74,7 +74,7 @@ The associated file is available for
 .BR write (2)
 operations.
 .TP
-.BR EPOLLRDHUP " (since kernel 2.6.17)"
+.BR EPOLLRDHUP " (since Linux 2.6.17)"
 Stream socket peer closed connection,
 or shut down writing half of connection.
 (This flag is especially useful for writing simple code to detect
@@ -107,7 +107,7 @@ See
 for more detailed information about Edge and Level Triggered event
 distribution architectures.
 .TP
-.BR EPOLLONESHOT " (since kernel 2.6.2)"
+.BR EPOLLONESHOT " (since Linux 2.6.2)"
 Sets the one-shot behavior for the associated file descriptor.
 This means that after an event is pulled out with
 .BR epoll_wait (2)
@@ -229,7 +229,7 @@ In kernel versions before 2.6.9, the
 operation required a non-NULL pointer in
 .IR event ,
 even though this argument is ignored.
-Since kernel 2.6.9,
+Since Linux 2.6.9,
 .I event
 can be specified as NULL
 when using

man2/getitimer.2

@@ -132,7 +132,7 @@ is not one of
 .BR ITIMER_VIRTUAL ,
 or
 .BR ITIMER_PROF ;
-or (since kernel 2.6.22) one of the
+or (since Linux 2.6.22) one of the
 .I tv_usec
 fields contains a value outside the range 0 to 999999.
 .SH "CONFORMING TO"
@@ -162,7 +162,7 @@ representation exceeds
 (defined in
 .IR include/linux/jiffies.h ),
 then the timer is silently truncated to this ceiling value.
-On Linux/i386 (where, since kernel 2.6.13,
+On Linux/i386 (where, since Linux 2.6.13,
 the default jiffy is 0.004 seconds),
 this means that the ceiling value for a timer is
 approximately 99.42 days.

man2/getpriority.2

@@ -224,4 +224,4 @@ defined in
 .BR renice (8)
 .sp
 .I Documentation/scheduler/sched-nice-design.txt
-in the kernel source tree (since kernel 2.6.23).
+in the kernel source tree (since Linux 2.6.23).

man2/getrlimit.2

@@ -255,7 +255,7 @@ The first addend in the formula, which includes
 create an unlimited number of zero-length messages (such messages
 nevertheless each consume some system memory for bookkeeping overhead).
 .TP
-.BR RLIMIT_NICE " (since kernel 2.6.12, but see BUGS below)"
+.BR RLIMIT_NICE " (since Linux 2.6.12, but see BUGS below)"
 Specifies a ceiling to which the process's nice value can be raised using
 .BR setpriority (2)
 or
@@ -402,7 +402,7 @@ In 2.6.x kernels before 2.6.17, a
 .B RLIMIT_CPU
 limit of 0 is wrongly treated as "no limit" (like
 .BR RLIM_INFINITY ).
-Since kernel 2.6.17, setting a limit of 0 does have an effect,
+Since Linux 2.6.17, setting a limit of 0 does have an effect,
 but is actually treated as a limit of 1 second.
 .\" see http://marc.theaimsgroup.com/?l=linux-kernel&m=114008066530167&w=2
 

man7/unix.7

@@ -41,7 +41,7 @@ for a stream-oriented socket and
 for a datagram-oriented socket that preserves message boundaries
 (as on most Unix implementations, Unix domain datagram
 sockets are always reliable and don't reorder datagrams);
-and (since kernel 2.6.4)
+and (since Linux 2.6.4)
 .BR SOCK_SEQPACKET ,
 for a connection-oriented socket that preserves message boundaries
 and delivers messages in the order that they were sent.