diff --git a/man2/seccomp.2 b/man2/seccomp.2
index ec1df0c9e..8b2543715 100644
--- a/man2/seccomp.2
+++ b/man2/seccomp.2
@@ -385,13 +385,15 @@ the handler will be ignored in this case and the process always terminates.
 .\" See these commits:
 .\" seccomp: dump core when using SECCOMP_RET_KILL (b25e67161c295c98acda92123b2dd1e7d8642901)
 .\" seccomp: Only dump core when single-threaded (d7276e321ff8a53106a59c85ca46d03e34288893)
-Before Linux 4.11, any process terminated this way would not trigger a coredump
+Before Linux 4.11,
+any process terminated this way would not trigger a coredump
 (even though
 .B SIGSYS
 is documented in
 .BR signal (7)
-as having a default core action).
-Since Linux 4.11, single threaded processes follow standard coredump behavior,
+as having a default action of termination with a core dump).
+Since Linux 4.11,
+single threaded processes follow standard core dump behavior,
 but multithreaded processes still do not.
 There is no workaround currently for multithreaded processes.
 .TP