diff --git a/man2/futex.2 b/man2/futex.2
index 6c70df113..62f56abe1 100644
--- a/man2/futex.2
+++ b/man2/futex.2
@@ -778,7 +778,7 @@ have their priorities raised to be the same as the high-priority task.
 From a user-space perspective,
 what makes a futex PI-aware is a policy agreement (described below)
 between user space and the kernel about the value of the futex word,
-coupled with the use of the PI futex operations described below
+coupled with the use of the PI-futex operations described below
 (in particular,
 .BR FUTEX_LOCK_PI ,
 .BR FUTEX_TRYLOCK_PI ,
@@ -794,9 +794,9 @@ and
 
 .\"       mtk: The following text is drawn from the Hart/Guniguntala paper
 .\"       (listed in SEE ALSO), but I have reworded some pieces
-.\"       significantly.
+.\"       significntly.
 .\"
-The PI futex operations described below differ from the other
+The PI-futex operations described below differ from the other
 futex operations in that they impose policy on the use of the value of the
 futex word:
 .IP * 3
@@ -865,7 +865,7 @@ It is important to note
 that the kernel will update the futex word's value prior
 to returning to user space.
 Unlike the other futex operations described above,
-the PI futex operations are designed
+the PI-futex operations are designed
 for the implementation of very specific IPC mechanisms.
 .\"
 .\" FIXME XXX In discussing errors for FUTEX_CMP_REQUEUE_PI, Darren Hart
@@ -1472,7 +1472,7 @@ nor
 .BR FUTEX_CMP_REQUEUE_PI ,
 .BR FUTEX_WAIT_REQUEUE_PI )
 A run-time check determined that the operation is not available.
-The PI futex operations are not implemented on all architectures and
+The PI-futex operations are not implemented on all architectures and
 are not supported on some CPU variants.
 .TP
 .BR EPERM