6 files changed, 29 insertions, 29 deletions
diff --git a/man7/credentials.7 b/man7/credentials.7
index d65c18de2d..ae5c12b06e 100644
--- a/man7/credentials.7
+++ b/man7/credentials.7
@@ -30,7 +30,7 @@ that is assigned when the process is created using
 A process can obtain its PID using
 .BR getpid (2).
 A PID is represented using the type
-.IR pid_t 
+.IR pid_t
 (defined in
 .IR <sys/types.h> ).
 
@@ -72,7 +72,7 @@ A process's PPID is preserved across an
 Each process has a session ID and a process group ID,
 both represented using the type
 .IR pid_t .
-A process can obtain its session ID using 
+A process can obtain its session ID using
 .BR getsid(2),
 and its process group ID using
 .BR getpgrp (2).
@@ -85,7 +85,7 @@ A process's session ID and process group ID are preserved across an
 
 Sessions and process groups are abstractions devised to support shell
 job control.
-A process group (sometimes called a "job") is a collection of 
+A process group (sometimes called a "job") is a collection of
 processes that share the same process group ID;
 the shell creates a new process group for the process(es) used
 to execute single command or pipeline (e.g., the two processes
@@ -195,7 +195,7 @@ A child process created by
 inherits copies of its parent's user and groups IDs.
 During an
 .BR execve (2),
-a process's real user and group ID and supplementary 
+a process's real user and group ID and supplementary
 group IDs are preserved;
 the effective and saved set IDs may be changed, as described in
 .BR execve (2).
@@ -207,7 +207,7 @@ when determining the permissions for sending signals \(em see
 .BR kill (2);
 .IP *
 when determining the permissions for setting
-process-scheduling parameters (nice value, real time 
+process-scheduling parameters (nice value, real time
 scheduling policy and priority, CPU affinity, I/O priority) using
 .BR setpriority (2),
 .BR sched_setaffinity (2),
diff --git a/man7/epoll.7 b/man7/epoll.7
index 6931d910a3..005dc8ff4f 100644
--- a/man7/epoll.7
+++ b/man7/epoll.7
@@ -84,7 +84,7 @@ interface using the
 .B EPOLLET
 flag, the call to
 .BR epoll_wait (2)
-done in step 
+done in step
 .B 5
 will probably hang despite the available data still present in the file
 input buffer;
@@ -291,7 +291,7 @@ calls, are they combined or reported separately?
 They will be combined.
 .TP
 .B Q8
-Does an operation on a file descriptor affect the 
+Does an operation on a file descriptor affect the
 already collected but not yet reported events?
 .TP
 .B A8
diff --git a/man7/inotify.7 b/man7/inotify.7
index 2e28047f28..ed253f029c 100644
--- a/man7/inotify.7
+++ b/man7/inotify.7
@@ -127,9 +127,9 @@ the length of each
 structure is thus
 .IR "sizeof(inotify_event)+len" .
 
-The behavior when the buffer given to 
+The behavior when the buffer given to
 .BR read (2)
-is too small to return information about the next event depends 
+is too small to return information about the next event depends
 on the kernel version: in kernels before 2.6.21,
 .BR read (2)
 returns 0; since kernel 2.6.21,
diff --git a/man7/man-pages.7 b/man7/man-pages.7
index 2316698eab..152dd0434b 100644
--- a/man7/man-pages.7
+++ b/man7/man-pages.7
@@ -21,8 +21,8 @@
 .\"
 .\" Formatted or processed versions of this manual, if unaccompanied by
 .\" the source, must acknowledge the copyright and authors of this work.
-.\" 
-.\" 2007-05-30 created by mtk, using text from old man.7 plus 
+.\"
+.\" 2007-05-30 created by mtk, using text from old man.7 plus
 .\" rewrites and additional text.
 .\"
 .TH MAN-PAGES 7 2007-05-30 "Linux" "Linux Programmer's Manual"
@@ -86,10 +86,10 @@ New manual pages should be marked up using the
 .B groff tmac.an
 package described in
 .BR man (7).
-This choice is mainly for consistency: the vast majority of 
+This choice is mainly for consistency: the vast majority of
 existing Linux manual pages are marked up using these macros.
 .SS Conventions for source file layout
-Please limit source code line length to no more than about 75 characters 
+Please limit source code line length to no more than about 75 characters
 wherever possible.
 This helps avoid line-wrapping in some mail clients when patches are
 submitted inline.
@@ -137,7 +137,7 @@ However, this was never done consistently, and so was
 probably worse than including no version number.
 Henceforth, avoid including a version number.)
 .sp
-For library calls that are part of glibc or one of the 
+For library calls that are part of glibc or one of the
 other common GNU libraries, just use
 .IR "GNU C Library" ", " GNU ,
 or an empty string.
@@ -149,13 +149,13 @@ In cases of doubt, just write
 .IR Linux ", or " GNU .
 .TP
 .I manual
-The title of the manual (e.g., for Section 2 and 3 pages in 
+The title of the manual (e.g., for Section 2 and 3 pages in
 the \fIman-pages\fP package, use
 .IR "Linux Programmer's Manual" ).
 .RE
 .SS Sections within a manual page
 The list below shows conventional or suggested sections.
-Most manual pages should include at least the 
+Most manual pages should include at least the
 .B highlighted
 sections.
 Arrange a new manual page so that sections
@@ -173,8 +173,8 @@ RETURN VALUE       [Normally only in Sections 2, 3]
 .\" ERROR HANDLING,
 ERRORS             [Typically only in Sections 2, 3]
 .\" May 07: Almost no current man pages have a USAGE section,,,
-.\" USAGE, 
-..\" DIAGNOSTICS, 
+.\" USAGE,
+..\" DIAGNOSTICS,
 .\" May 07: Almost no current man pages have a SECURITY section,,,
 .\" SECURITY,
 ENVIRONMENT
@@ -192,19 +192,19 @@ EXAMPLE
 .in
 .IR "Where a traditional heading would apply" ", " "please use it" ;
 this kind of consistency can make the information easier to understand.
-If you must, you can create your own 
+If you must, you can create your own
 headings if they make things easier to understand (this can
 be especially useful for pages in Sections 4 and 5).
 However, before doing this, consider whether you could use the
 traditional headings, with some subsections (\fI.SS\fP) within
 those sections.
 
-The following list elaborates on the contents of each of 
+The following list elaborates on the contents of each of
 the above sections.
 .TP 14
 .B NAME
 The name of this manual page.
-See 
+See
 .BR man (7)
 for important details of the line(s) that should follow the
 \fB.SH NAME\fI command.
@@ -239,7 +239,7 @@ section.
 .\" section).
 .TP
 .B OPTIONS
-describes the command-line options accepted by a 
+describes the command-line options accepted by a
 program and how they change its behavior.
 This section should only appear for Section 1 and 8 manual pages.
 .\" .TP
@@ -324,8 +324,8 @@ but isn't in the current version of POSIX.1.)
 (See
 .BR standards (7).)
 
-If the call is not governed by any standards but commonly 
-exists on other systems, note them. 
+If the call is not governed by any standards but commonly
+exists on other systems, note them.
 If the call is Linux specific, note this.
 .TP
 .B NOTES
@@ -354,7 +354,7 @@ If you are the author a device driver and what to include
 an address for reporting bugs, place this under the BUGS section.
 .TP
 .B SEE ALSO
-lists related man pages, ordered by section number and 
+lists related man pages, ordered by section number and
 alphabetically by name, possibly followed by
 other related pages or documents.
 .SS Font conventions
@@ -384,7 +384,7 @@ macro).
 Any reference to the subject of the current manual page
 should be written with the name in bold.
 If the subject is a function (i.e., this is a Section 2 or 3 page),
-then the name should be followed by a pair of parentheses 
+then the name should be followed by a pair of parentheses
 in Roman (normal) font.
 For example, in the
 .BR fcntl (2)
@@ -420,7 +420,7 @@ Starting with release 2.59,
 follows American spelling conventions;
 please write all new pages and patches according to these conventions.
 .SS Example Programs
-Manual pages can include example programs demonstrating how to 
+Manual pages can include example programs demonstrating how to
 use a system call or library function.
 However, note the following:
 .TP 3
diff --git a/man7/man.7 b/man7/man.7
index c81f01b78c..0de8734a07 100644
--- a/man7/man.7
+++ b/man7/man.7
@@ -74,7 +74,7 @@ For conventions that should be employed when writing man pages
 for the Linux \fIman-pages\fP package, see
 .BR man-pages (7).
 .SS Title line
-The first command in a man page (after comment lines, 
+The first command in a man page (after comment lines,
 that is, lines that start with \fB.\\"\fP) should be
 .RS
 .sp
diff --git a/man7/unix.7 b/man7/unix.7
index 5f972acaa5..e6cf55d34d 100644
--- a/man7/unix.7
+++ b/man7/unix.7
@@ -291,7 +291,7 @@ call.
 
 Unix domain stream sockets do not support the notion of out-of-band data.
 .SH EXAMPLE
-See 
+See
 .BR bind (2).
 .SH "SEE ALSO"
 .BR recvmsg (2),