access.2, delete_module.2, eventfd.2, fallocate.2, fcntl.2, getrandom.2, init_module.2, open.2, seccomp.2, timerfd_create.2, openpty.3, pthread_spin_lock.3, shm_open.3, tempnam.3, fifo.7, keyrings.7, pid_namespaces.7, sched.7, thread-keyring.7: wfix (will fail --> fail/fails)

Reported-by: Pedro Alves <palves@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/access.2

@@ -319,7 +319,7 @@ directories in the path prefix of
 grant search (i.e., execute) access.
 If any directory is inaccessible, then the
 .BR access ()
-call will fail, regardless of the permissions on the file itself.
+call fails, regardless of the permissions on the file itself.
 .PP
 Only access bits are checked, not the file type or contents.
 Therefore, if a directory is found to be writable,

man2/delete_module.2

@@ -106,7 +106,7 @@ By default, if a module has an
 .I init
 function but no
 .I exit
-function, then an attempt to remove the module will fail.
+function, then an attempt to remove the module fails.
 However, if
 .BR O_TRUNC
 was specified, this requirement is bypassed.

man2/eventfd.2

@@ -80,7 +80,7 @@ Each successful
 returns an 8-byte integer.
 A
 .BR read (2)
-will fail with the error
+fails with the error
 .B EINVAL
 if the size of the supplied buffer is less than 8 bytes.
 .IP
@@ -141,7 +141,7 @@ if the file descriptor has been made nonblocking.
 .IP
 A
 .BR write (2)
-will fail with the error
+fails with the error
 .B EINVAL
 if the size of the supplied buffer is less than 8 bytes,
 or if an attempt is made to write the value 0xffffffffffffffff.

man2/fallocate.2

@@ -165,7 +165,7 @@ must be a multiple of the filesystem logical block size,
 which varies according to the filesystem type and configuration.
 If a filesystem has such a requirement,
 .BR fallocate ()
-will fail with the error
+fails with the error
 .BR EINVAL
 if this requirement is violated.
 .PP
@@ -267,7 +267,7 @@ This mode has the same limitations as
 regarding the granularity of the operation.
 If the granularity requirements are not met,
 .BR fallocate ()
-will fail with the error
+fails with the error
 .BR EINVAL.
 If the
 .I offset

man2/fcntl.2

@@ -1417,7 +1417,7 @@ If this seal is set, any further call to
 .BR fcntl ()
 with
 .B F_ADD_SEALS
-will fail with
+fails with the error
 .BR EPERM .
 Therefore, this seal prevents any modifications to the set of seals itself.
 If the initial set of seals of a file includes

man2/getrandom.2

@@ -246,7 +246,7 @@ source is interrupted by a signal handler
 depends on the initialization state of the entropy buffer
 and on the request size,
 .IR buflen .
-If the entropy is not yet initialized, then the call will fail with the
+If the entropy is not yet initialized, then the call fails with the
 .B EINTR
 error.
 If the entropy pool has been initialized

man2/init_module.2

@@ -148,7 +148,7 @@ flag indicates that the "vermagic" string is to be ignored, and the
 flag indicates that the symbol version hashes are to be ignored.
 If the kernel is built to permit forced loading (i.e., configured with
 .BR CONFIG_MODULE_FORCE_LOAD ),
-then loading will continue, otherwise it will fail with
+then loading continues, otherwise it fails with the error
 .B ENOEXEC
 as expected for malformed modules.
 .SH RETURN VALUE

man2/open.2

@@ -429,7 +429,8 @@ and
 .I pathname
 already exists, then
 .BR open ()
-will fail.
+fails with the error
+.BR EEXIST .
 .IP
 When these two flags are specified, symbolic links are not followed:
 .\" POSIX.1-2001 explicitly requires this behavior.

man2/seccomp.2

@@ -148,7 +148,7 @@ the thread must make the following call:
 .IP
 Otherwise, the
 .BR SECCOMP_SET_MODE_FILTER
-operation will fail and return
+operation fails and returns
 .BR EACCES
 in
 .IR errno .

man2/timerfd_create.2

@@ -297,7 +297,7 @@ flag).
 .IP
 A
 .BR read (2)
-will fail with the error
+fails with the error
 .B EINVAL
 if the size of the supplied buffer is less than 8 bytes.
 .IP
@@ -313,7 +313,7 @@ was specified when calling
 .BR timerfd_settime (),
 then
 .BR read (2)
-will fail with the error
+fails with the error
 .BR ECANCELED
 if the real-time clock undergoes a discontinuous change.
 (This allows the reading application to discover

man3/openpty.3

@@ -130,20 +130,20 @@ return 0, and the parent process of
 returns the process ID of the child process.
 .SH ERRORS
 .BR openpty ()
-will fail if:
+fails if:
 .TP
 .B ENOENT
 There are no available terminals.
 .PP
 .BR login_tty ()
-will fail if
+fails if
 .BR ioctl (2)
 fails to set
 .I fd
 to the controlling terminal of the calling process.
 .PP
 .BR forkpty ()
-will fail if either
+fails if either
 .BR openpty ()
 or
 .BR fork (2)

man3/pthread_spin_lock.3

@@ -100,7 +100,7 @@ may fail with the following errors:
 The system detected a deadlock condition.
 .PP
 .BR pthread_spin_trylock ()
-will fail with the following errors:
+fails with the following errors:
 .TP
 .B EBUSY
 The spin lock is currently locked by another thread.

man3/shm_open.3

@@ -165,7 +165,7 @@ attempts to
 .BR shm_open ()
 an object with the same
 .I name
-will fail (unless
+fail (unless
 .B O_CREAT
 was specified, in which case a new, distinct object is created).
 .SH RETURN VALUE

man3/tempnam.3

@@ -174,7 +174,7 @@ uses at most the first five bytes from
 .PP
 The glibc implementation of
 .BR tempnam ()
-will fail with the error
+fails with the error
 .B EEXIST
 upon failure to find a unique name.
 .SH BUGS

man7/fifo.7

@@ -34,9 +34,9 @@ until the other end is opened also.
 .PP
 A process can open a FIFO in nonblocking mode.
 In this
-case, opening for read-only will succeed even if no-one has
-opened on the write side yet and opening for write-only will
-fail with
+case, opening for read-only succeeds even if no-one has
+opened on the write side yet and opening for write-only
+fails with
 .B ENXIO
 (no such device or address) unless the other
 end has already been opened.

man7/keyrings.7

@@ -91,7 +91,7 @@ the key is marked as being expired and accesses to it fail with the error
 If not deleted, updated, or replaced, then, after a set amount of time,
 an expired key is automatically removed (garbage collected)
 along with all links to it,
-and attempts to access the key will fail with the error
+and attempts to access the key fail with the error
 .BR ENOKEY .
 .TP
 Reference count

man7/pid_namespaces.7

@@ -81,7 +81,7 @@ This behavior reflects the fact that the "init" process
 is essential for the correct operation of a PID namespace.
 In this case, a subsequent
 .BR fork (2)
-into this PID namespace will fail with the error
+into this PID namespace fail with the error
 .BR ENOMEM ;
 it is not possible to create a new processes in a PID namespace whose "init"
 process has terminated.
@@ -97,7 +97,7 @@ if the first child subsequently created by a
 .BR fork (2)
 terminates, then subsequent calls to
 .BR fork (2)
-will fail with
+fail with
 .BR ENOMEM .
 .PP
 Only signals for which the "init" process has established a signal handler

man7/sched.7

@@ -356,7 +356,7 @@ A call to
 .BR fork (2)
 by a thread scheduled under the
 .B SCHED_DEADLINE
-policy will fail with the error
+policy fails with the error
 .BR EAGAIN ,
 unless the thread has its reset-on-fork flag set (see below).
 .PP

man7/thread-keyring.7

@@ -41,7 +41,7 @@ A thread keyring is destroyed when the thread that refers to it terminates.
 Initially, a thread does not have a thread keyring.
 If a thread doesn't have a thread keyring when it is accessed,
 then it will be created if it is to be modified;
-otherwise the operation will fail with the error
+otherwise the operation fails with the error
 .BR ENOKEY .
 .SH SEE ALSO
 .ad l