Re: [PATCH] manual: Document the fexecve function

[Florian Weimer <fw@deneb.enyo.de>]

* Michael Kerrisk:

>> +@deftypefun int fexecve (int @var{fd},  char *const @var{argv}@t{[]}, char *const @var{env}@t{[]})
>> +@standards{POSIX.1, unistd.h}
>> +@safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
>> +This is similar to @code{execve}, but instead identifying the progam
>
> s/instead/instead of/
> s/progam/program/

Thanks.  Here's what I'm going to push.

8<------------------------------------------------------------------8<
Subject: manual: Fix typos in the fexecve description

Reported by Michael Kerrisk.

-----
 manual/process.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/manual/process.texi b/manual/process.texi
index b20ad26cbf..54e65f76c6 100644
--- a/manual/process.texi
+++ b/manual/process.texi
@@ -408,7 +408,7 @@ variable; see @ref{Environment Access}.
 @deftypefun int fexecve (int @var{fd},  char *const @var{argv}@t{[]}, char *const @var{env}@t{[]})
 @standards{POSIX.1, unistd.h}
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-This is similar to @code{execve}, but instead identifying the progam
+This is similar to @code{execve}, but instead of identifying the program
 executable by its pathname, the file descriptor @var{fd} is used.  The
 descriptor must have been opened with the @code{O_RDONLY} flag or (on
 Linux) the @code{O_PATH} flag.