Removed trailing white space at end of lines

man2/futex.2

@@ -712,7 +712,7 @@ This operation is like
 except that
 .I val3
 is used to provide a 32-bit bit mask to the kernel.
-This bit mask, in which at least one bit must be set, 
+This bit mask, in which at least one bit must be set,
 is stored in the kernel-internal state of the waiter.
 See the description of
 .BR FUTEX_WAKE_BITSET
@@ -1093,7 +1093,7 @@ clock.
 .\" From: Thomas Gleixner <tglx@linutronix.de>
 .\" Date: 6 July 2016 at 20:57
 .\" Subject: Re: futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op
-.\" 
+.\"
 .\" On Thu, 23 Jun 2016, Michael Kerrisk (man-pages) wrote:
 .\" > On 06/23/2016 08:28 PM, Darren Hart wrote:
 .\" > > And as a follow-on, what is the reason for FUTEX_LOCK_PI only using
@@ -1101,7 +1101,7 @@ clock.
 .\" > > specific amount of time, regardless of wall time.
 .\" >
 .\" > Yes, that's another weird inconsistency.
-.\" 
+.\"
 .\" The reason is that phtread_mutex_timedlock() uses absolute timeouts based on
 .\" CLOCK_REALTIME. glibc folks asked to make that the default behaviour back
 .\" then when we added LOCK_PI.

man2/ioctl_fideduperange.2

@@ -71,7 +71,7 @@ struct file_dedupe_range {
 Deduplication is atomic with regards to concurrent writes, so no locks need to
 be taken to obtain a consistent deduplicated copy.
 
-The fields 
+The fields
 .IR reserved1 " and " reserved2
 must be zero.
 

man3/strcat.3

@@ -211,7 +211,7 @@ main(int argc, char *argv[])
     int j;
     char p[LIM];
     time_t base;
-     
+
     base = time(NULL);
     p[0] = \(aq\\0\(aq;
 
@@ -222,7 +222,7 @@ main(int argc, char *argv[])
     }
 }
 .fi
-.BR 
+.BR
 .\"
 .SH SEE ALSO
 .BR bcopy (3),