delete_module.2, perf_event_open.2, sched_setscheduler.2, shmctl.2, gai.conf.5, resolv.conf.5, fanotify.7, man-pages.7: wsfix

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

man2/delete_module.2

@@ -54,7 +54,7 @@ If there are other loaded modules that depend on
 then the call fails.
 .IP 2.
 Otherwise, if the reference count for the module
-(i.e., the  number  of processes currently using the module)
+(i.e., the number of processes currently using the module)
 is zero, then the module is immediately unloaded.
 .IP 3.
 If a module has a nonzero reference count,

man2/perf_event_open.2

@@ -749,7 +749,7 @@ Adds the 64-bit
 .I time_running
 field.
 This can be used to calculate estimated totals if
-the PMU is overcommitted and  multiplexing is happening.
+the PMU is overcommitted and multiplexing is happening.
 .TP
 .B PERF_FORMAT_ID
 Adds a 64-bit unique value that corresponds to the event group.
@@ -994,7 +994,7 @@ bitflag.
 only counts
 .B PERF_RECORD_SAMPLE
 record types.
-To  receive a signal for every incoming
+To receive a signal for every incoming
 .B PERF_RECORD
 type set
 .I wakeup_watermark
@@ -1131,7 +1131,7 @@ is specified.
 .SS Reading results
 Once a
 .BR perf_event_open ()
-file descriptor  has been opened, the values
+file descriptor has been opened, the values
 of the events can be read from the file descriptor.
 The values that are there are specified by the
 .I read_format
@@ -1479,7 +1479,7 @@ an event took place (TID, TIME, ID, CPU, STREAM_ID) described in
 below, it will be stashed just after the
 .I perf_event_header
 and the fields already present for the existing
-fields, that  is, at the end of the payload.
+fields, that is, at the end of the payload.
 That way a newer perf.data
 file will be supported by older perf tools, with these new optional
 fields being ignored.

man2/sched_setscheduler.2

@@ -159,7 +159,7 @@ POSIX.1-2001 (but see BUGS below).
 The \fBSCHED_BATCH\fP and \fBSCHED_IDLE\fP policies are Linux-specific.
 .SH NOTES
 Further details of the semantics of all of the above "normal"
-and "real-time" scheduling  policies can be found in
+and "real-time" scheduling policies can be found in
 .BR sched (7).
 
 POSIX systems on which

man2/shmctl.2

@@ -178,7 +178,7 @@ feature test macro is defined:
 .nf
 .in +4n
 
-struct  shminfo {
+struct shminfo {
     unsigned long shmmax; /* Maximum segment size */
     unsigned long shmmin; /* Minimum segment size;
                              always 1 */

man5/gai.conf.5

@@ -50,7 +50,7 @@ Following the keyword,
 the line has to contain a network mask and a label value.
 .TP
 \fBprecedence\fR \fInetmask\fR \fIprecedence\fR
-This  keyword is similar to \fBlabel\fR, but instead the value is added
+This keyword is similar to \fBlabel\fR, but instead the value is added
 to the precedence table as specified in RFC\ 3484.
 Once again, the
 presence of a single \fBprecedence\fR line in the configuration file

man5/resolv.conf.5

@@ -260,7 +260,7 @@ Some hardware mistakenly sends back only one reply.
 When that happens the client system will sit and wait for the second reply.
 Turning this option on changes this behavior
 so that if two requests from the same port are not handled correctly it will
-close the  socket and open a new one before sending the second request.
+close the socket and open a new one before sending the second request.
 .RE
 .LP
 The \fIdomain\fP and \fIsearch\fP keywords are mutually exclusive.

man7/fanotify.7

@@ -459,7 +459,7 @@ events for the monitored directory itself.
 Fanotify monitoring of directories is not recursive:
 to monitor subdirectories under a directory,
 additional marks must be created.
-(But note that the fanotify API provides no way of  detecting when a
+(But note that the fanotify API provides no way of detecting when a
 subdirectory has been created under a marked directory,
 which makes recursive monitoring difficult.)
 Monitoring mounts offers the capability to monitor a whole directory tree.

man7/man-pages.7

@@ -274,7 +274,7 @@ list, in the following form (here, for a new system call flag):
 Description of flag...
 .RE
 .IP
-Including version information is  especially useful to users
+Including version information is especially useful to users
 who are constrained to using older kernel or C library versions
 (which is typical in embedded systems, for example).
 .TP