On 02/27/2015 01:26 AM, saulery@xxxxxxx wrote: > From: Stéphane Aulery <saulery@xxxxxxx> Thanks, Stéphane. Applied. Cheers, Michael > Signed-off-by: Stéphane Aulery <saulery@xxxxxxx> > --- > man2/intro.2 | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/man2/intro.2 b/man2/intro.2 > index b65bdfc..d0d18dc 100644 > --- a/man2/intro.2 > +++ b/man2/intro.2 > @@ -46,7 +46,7 @@ copying arguments and the unique system call number to the > registers where the kernel expects them; > .IP * > trapping to kernel mode, > -at which point the kernel does the real work of the system call; and > +at which point the kernel does the real work of the system call; > .IP * > setting > .I errno > @@ -55,7 +55,7 @@ CPU to user mode. > .LP > However, in a few cases, a wrapper function may do rather more than this, > for example, performing some preprocessing > -of the arguments of arguments before trapping to kernel mode, > +of the arguments before trapping to kernel mode, > or postprocessing of values returned by the system call. > Where this is the case, the manual pages in Section 2 generally > try to note the details of both the (usually GNU) C library API > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
