Removed trailing white space at end of lines

man2/fanotify_mark.2

@@ -283,7 +283,7 @@ flag was not specified when the fanotify file descriptor was created with
 .TP
 .B ENOSYS
 This kernel does not implement
-.BR fanotify_mark (). 
+.BR fanotify_mark ().
 The fanotify API is available only if the kernel was configured with
 .BR CONFIG_FANOTIFY .
 .TP

man2/read.2

@@ -221,7 +221,7 @@ This problem was fixed in Linux 3.14.
 .\" commit 9c225f2655e36a470c4f58dbbc99244c5fc7f2d4
 .\"    Author: Linus Torvalds <torvalds@linux-foundation.org>
 .\"    Date:   Mon Mar 3 09:36:58 2014 -0800
-.\"    
+.\"
 .\"        vfs: atomic f_pos accesses as per POSIX
 .SH SEE ALSO
 .BR close (2),

man2/rename.2

@@ -373,7 +373,7 @@ contains
 and
 .I newpath
 already exists.
-.TP 
+.TP
 .B EINVAL
 An invalid flag was specified in
 .IR flags ,

man2/write.2

@@ -245,7 +245,7 @@ This problem was fixed in Linux 3.14.
 .\" commit 9c225f2655e36a470c4f58dbbc99244c5fc7f2d4
 .\"    Author: Linus Torvalds <torvalds@linux-foundation.org>
 .\"    Date:   Mon Mar 3 09:36:58 2014 -0800
-.\"    
+.\"
 .\"        vfs: atomic f_pos accesses as per POSIX
 .SH SEE ALSO
 .BR close (2),

man7/fanotify.7

@@ -70,7 +70,7 @@ Having these two types of masks permits a mount point or directory to be
 marked for receiving events, while at the same time ignoring events for
 specific objects under that mount point or directory.
 .PP
-The 
+The
 .BR fanotify_mark (2)
 system call adds a file, directory, or mount to a notification group
 and specifies which events