diff options
Diffstat (limited to 'manual')
| -rw-r--r-- | manual/job.texi | 4 | ||||
| -rw-r--r-- | manual/process.texi | 2 | ||||
| -rw-r--r-- | manual/signal.texi | 10 |
3 files changed, 8 insertions, 8 deletions
diff --git a/manual/job.texi b/manual/job.texi index d19a8d4cc6..fbc7ace2c2 100644 --- a/manual/job.texi +++ b/manual/job.texi @@ -675,8 +675,8 @@ stop together. The foreground job may have left the terminal in a strange state, so the shell should restore its own saved terminal modes before continuing. In -case the job is merely been stopped, the shell should first save the -current terminal modes so that it can restore them later if the job is +case the job is merely stopped, the shell should first save the current +terminal modes so that it can restore them later if the job is continued. The functions for dealing with terminal modes are @code{tcgetattr} and @code{tcsetattr}; these are described in @ref{Terminal Modes}. diff --git a/manual/process.texi b/manual/process.texi index 14421b592f..08c880bc0e 100644 --- a/manual/process.texi +++ b/manual/process.texi @@ -63,7 +63,7 @@ possible to create the shell process, and otherwise is the status of the shell process. @xref{Process Completion}, for details on how this status code can be interpreted. -If the @var{command} argument is a null pointer a non-zero return value +If the @var{command} argument is a null pointer, a non-zero return value indicates that a command processor is available and this function can be used at all. diff --git a/manual/signal.texi b/manual/signal.texi index 08ee785c8c..4340ee7cbd 100644 --- a/manual/signal.texi +++ b/manual/signal.texi @@ -543,7 +543,7 @@ In fact, if @code{SIGKILL} fails to terminate a process, that by itself constitutes an operating system bug which you should report. The system will generate @code{SIGKILL} for a process itself under some -unusual conditions where the program cannot possible continue to run +unusual conditions where the program cannot possibly continue to run (even to run a signal handler). @end deftypevr @cindex kill signal @@ -1856,7 +1856,7 @@ blocks signals around each use, then you are safe. There are a large number of library functions that return values in a fixed object, always reusing the same object in this fashion, and all of -them cause the same problem. Function descriptions in this manual +them cause the same problem. Function descriptions in this manual always mention this behavior. @item @@ -2031,8 +2031,8 @@ atomically. In practice, you can assume that @code{int} and other integer types no longer than @code{int} are atomic. You can also assume that pointer -types are atomic; that is very convenient. Both of these assumptions -are true on all of the machines that the GNU C library supports and on +types are atomic; that is very convenient. Both of these assumptions +are true on all of the machines that the GNU C library supports and on all POSIX systems we know of. @c ??? This might fail on a 386 that uses 64-bit pointers. @@ -3011,7 +3011,7 @@ to terminate the process or invoke a signal handling function. In other words, the program is effectively suspended until one of the signals that is not a member of @var{set} arrives. -If the process is woken up by deliver of a signal that invokes a handler +If the process is woken up by delivery of a signal that invokes a handler function, and the handler function returns, then @code{sigsuspend} also returns. |