vfork.2: Minor wording fixes

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2012-03-13 03:50:13 +13:00
parent f23cc1df32
commit 7a5b06940e
1 changed files with 3 additions and 3 deletions

View File

@ -183,9 +183,9 @@ as it will, in that case, be made synonymous to
" "
However, even though modern memory management hardware However, even though modern memory management hardware
has decreased the performance difference between has decreased the performance difference between
.BR fork () .BR fork (2)
and and
.BR vfork (2), .BR vfork (),
there are various reasons why Linux and other systems have retained there are various reasons why Linux and other systems have retained
.BR vfork (): .BR vfork ():
.IP * 3 .IP * 3
@ -193,7 +193,7 @@ Some performance-critical applications require the small performance
advantage conferred by advantage conferred by
.BR vfork (). .BR vfork ().
.IP * .IP *
.BR vfork (2) .BR vfork ()
can be implemented on systems that lack a memory-management unit (MMU), but can be implemented on systems that lack a memory-management unit (MMU), but
.BR fork (2) .BR fork (2)
can't be implemented on such systems. can't be implemented on such systems.