mlock.2: Minor tweaks to Sebastian Andrzej Siewior's patch

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man2/mlock.2 b/man2/mlock.2
index 27f80f6664efc3a5527ff3bb2d29ed6c86ab445f..08387b0bbebb8f0426a608a9bc21b314a4b2ca50 100644 (file)
--- a/man2/mlock.2
+++ b/man2/mlock.2
@@ -352,17 +352,17 @@ and are cleared during an
 
 Note that
 .BR fork (2)
-will prepare the address space for a copy-on-write operation. The consequence
-is that any write access that follows will cause a page fault which in turn may
-cause high latencies for a real-time process. Therefore it is crucial not to
-invoke
+will prepare the address space for a copy-on-write operation.
+The consequence is that any write access that follows will cause
+a page fault that in turn may cause high latencies for a real-time process.
+Therefore, it is crucial not to invoke
 .BR fork (2)
-after the
+after an
 .BR mlockall ()
 or
 .BR mlock ()
-operation not even from thread which runs at a low priority within a process
-which also has a thread running at elevated priority.
+operation\(emnot even from a thread which runs at a low priority within
+a process which also has a thread running at elevated priority.
 
 The memory lock on an address range is automatically removed
 if the address range is unmapped via