From 7a5b06940eee5561724ca63a9515ba866d9f075b Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Tue, 13 Mar 2012 03:50:13 +1300 Subject: [PATCH] vfork.2: Minor wording fixes Signed-off-by: Michael Kerrisk --- man2/vfork.2 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/man2/vfork.2 b/man2/vfork.2 index 1201afb94..94d25f83e 100644 --- a/man2/vfork.2 +++ b/man2/vfork.2 @@ -183,9 +183,9 @@ as it will, in that case, be made synonymous to " However, even though modern memory management hardware has decreased the performance difference between -.BR fork () +.BR fork (2) and -.BR vfork (2), +.BR vfork (), there are various reasons why Linux and other systems have retained .BR vfork (): .IP * 3 @@ -193,7 +193,7 @@ Some performance-critical applications require the small performance advantage conferred by .BR vfork (). .IP * -.BR vfork (2) +.BR vfork () can be implemented on systems that lack a memory-management unit (MMU), but .BR fork (2) can't be implemented on such systems.