doc: clarify child_process.execFile{,Sync} file argument
This may be a bit of a nit, but I thought it was worth fixing for clarity.
The changes to the file
argument of execFile
in #4504 make it appear that execFile
requires an absolute or relative path to the executable file, when in fact it also supports a filename which will be resolved using $PATH
. Although the example clarifies this somewhat, assuming there isn't a node
binary in $CWD
, it's easy to overlook. This commit clarifies that point.
It also updates the argument description for execFileSync
to match, since it was overlooked in #4504 and behaves identically.
Thanks for considering, Kevin