5 files changed, 8 insertions, 8 deletions
diff --git a/man7/fifo.7 b/man7/fifo.7
index d7dde7ca58..aa73f9dd69 100644
--- a/man7/fifo.7
+++ b/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.
diff --git a/man7/keyrings.7 b/man7/keyrings.7
index 3c72054b6d..e893838655 100644
--- a/man7/keyrings.7
+++ b/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
diff --git a/man7/pid_namespaces.7 b/man7/pid_namespaces.7
index 7618f2db8f..d762df2031 100644
--- a/man7/pid_namespaces.7
+++ b/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
diff --git a/man7/sched.7 b/man7/sched.7
index 94789e565b..c8073467a4 100644
--- a/man7/sched.7
+++ b/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
diff --git a/man7/thread-keyring.7 b/man7/thread-keyring.7
index 14ac958958..67c6aa87be 100644
--- a/man7/thread-keyring.7
+++ b/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