diff --git a/man2/sigaction.2 b/man2/sigaction.2
index 18404dde1..5262b81c9 100644
--- a/man2/sigaction.2
+++ b/man2/sigaction.2
@@ -266,13 +266,13 @@ This flag is meaningful only when establishing a signal handler.
 Used to dynamically probe for flag bit support.
 .IP
 If an attempt to register a handler succeeds with this flag set in
-.I act->sa_flags
+.I act\->sa_flags
 alongside other flags that are potentially unsupported by the kernel,
 and an immediately subsequent
 .BR sigaction ()
-call specifying the same signal number n and with non-NULL
+call specifying the same signal number and with a non-NULL
 .I oldact
-yields
+argument yields
 .B SA_UNSUPPORTED
 .I clear
 in
@@ -888,16 +888,16 @@ filter rule.
 The
 .BR sigaction ()
 call on Linux accepts unknown bits set in
-.I act->sa_flags
+.I act\->sa_flags
 without error.
 The behavior of the kernel starting with Linux 5.11 is that a second
 .BR sigaction ()
 will clear unknown bits from
-.IR oldact->sa_flags .
+.IR oldact\->sa_flags .
 However, historically, a second
 .BR sigaction ()
 call would typically leave those bits set in
-.IR oldact->sa_flags .
+.IR oldact\->sa_flags .
 .PP
 This means that support for new flags cannot be detected
 simply by testing for a flag in
@@ -919,7 +919,7 @@ in the signal handler itself.
 In kernels that do not support a specific flag,
 the kernel's behavior is as if the flag was not set,
 even if the flag was set in
-.IR act->sa_flags .
+.IR act\->sa_flags .
 .PP
 The flags
 .BR SA_NOCLDSTOP ,