aboutsummaryrefslogtreecommitdiff
path: root/manual
diff options
context:
space:
mode:
Diffstat (limited to 'manual')
-rw-r--r--manual/arith.texi12
-rw-r--r--manual/creature.texi10
-rw-r--r--manual/errno.texi2
-rw-r--r--manual/filesys.texi6
-rw-r--r--manual/intro.texi2
-rw-r--r--manual/job.texi50
-rw-r--r--manual/libc.texinfo2
-rw-r--r--manual/locale.texi2
-rw-r--r--manual/math.texi2
-rw-r--r--manual/nss.texi6
-rw-r--r--manual/pattern.texi22
-rw-r--r--manual/signal.texi12
-rw-r--r--manual/startup.texi2
-rw-r--r--manual/stdio.texi4
-rw-r--r--manual/terminal.texi16
-rw-r--r--manual/users.texi18
16 files changed, 84 insertions, 84 deletions
diff --git a/manual/arith.texi b/manual/arith.texi
index e60216ed11..59ddbd626f 100644
--- a/manual/arith.texi
+++ b/manual/arith.texi
@@ -11,7 +11,7 @@ fractional parts. These functions are declared in the header file
* Predicates on Floats:: Testing for infinity and for NaNs.
* Absolute Value:: Absolute value functions.
* Normalization Functions:: Hacks for radix-2 representations.
-* Rounding and Remainders:: Determinining the integer and
+* Rounding and Remainders:: Determining the integer and
fractional parts of a float.
* Integer Division:: Functions for performing integer
division.
@@ -495,8 +495,8 @@ to @code{ERANGE} to indicate there was overflow.
Because the value @code{0l} is a correct result for @code{strtol} the
user who is interested in handling errors should set the global variable
-@code{errno} to @code{0} before calling this function. So it can be
-tested whether an error occured or not.
+@code{errno} to @code{0} before calling this function, so that the program
+can later test whether an error occurred.
There is an example at the end of this section.
@end deftypefun
@@ -699,7 +699,7 @@ call since all failures set @code{errno} to a non-zero value.
@deftypefun float strtof (const char *@var{string}, char **@var{tailptr})
This function is similar to the @code{strtod} function but it returns a
@code{float} value instead of a @code{double} value. If the precision
-of a @code{float} value is sufficent this function should be used since
+of a @code{float} value is sufficient this function should be used since
it is much faster than @code{strtod} on some architectures. The reasons
are obvious: @w{IEEE 754} defines @code{float} to have a mantissa of 23
bits while @code{double} has 53 bits and every additional bit of
@@ -718,9 +718,9 @@ This function is a GNU extension.
@deftypefun {long double} strtold (const char *@var{string}, char **@var{tailptr})
This function is similar to the @code{strtod} function but it returns a
@code{long double} value instead of a @code{double} value. It should be
-used when high presision is used. On systems which define a @code{long
+used when high precision is needed. On systems which define a @code{long
double} type (i.e., on which it is not the same as @code{double})
-running this function might take significently more time since more bits
+running this function might take significantly more time since more bits
of precision are required.
If the string has valid syntax for a floating-point number but the value
diff --git a/manual/creature.texi b/manual/creature.texi
index d5dfb6aa19..5eb665d2ef 100644
--- a/manual/creature.texi
+++ b/manual/creature.texi
@@ -73,13 +73,13 @@ included as well as the @w{ISO C}, POSIX.1, POSIX.2, and X/Open material.
@comment (none)
@comment XOPEN
@defvr Macro _XOPEN_SOURCE
-If you define these macro, functionality described in the X/Open
-Portability Guide is included. This is an superset of the POSIX.1 and
+If you define this macro, functionality described in the X/Open
+Portability Guide is included. This is a superset of the POSIX.1 and
POSIX.2 functionality and in fact @code{_POSIX_SOURCE} and
-@code{_POSIX_C_SOURCE} get automatically be defined.
+@code{_POSIX_C_SOURCE} are automatically defined.
-But as the great unifiction of all Unices there is also functionality
-only available in BSD and SVID is included.
+As the unification of all Unices, functionality only available in
+BSD and SVID is also included.
If the macro @code{_XOPEN_SOURCE_EXTENDED} is also defined, even more
functionality is available. The extra functions will make all functions
diff --git a/manual/errno.texi b/manual/errno.texi
index 47d9857dde..e346dd5f1f 100644
--- a/manual/errno.texi
+++ b/manual/errno.texi
@@ -144,7 +144,7 @@ No process matches the specified process ID.
@comment POSIX.1: Interrupted system call
@deftypevr Macro int EINTR
@comment errno 4 @c DO NOT REMOVE
-Interrupted function call; an asynchronous signal occured and prevented
+Interrupted function call; an asynchronous signal occurred and prevented
completion of the call. When this happens, you should try the call
again.
diff --git a/manual/filesys.texi b/manual/filesys.texi
index 39d4082b7f..54ea99cfd4 100644
--- a/manual/filesys.texi
+++ b/manual/filesys.texi
@@ -338,15 +338,15 @@ value. Use @code{readdir_r} when this is critical.
@deftypefun int readdir_r (DIR *@var{dirstream}, struct *@var{entry}, struct **@var{result})
This function is the reentrant version of @code{reentrant}. Like
@code{readdir} it returns the next entry from the directory. But to
-prevent conflicts for simultanously running threads the result is not
+prevent conflicts for simultaneously running threads the result is not
stored in some internal memory. Instead the argument @var{entry} has to
point to a place where the result is stored.
The return value is @code{0} in case the next entry was read
successfully. In this case a pointer to the result is returned in
*@var{result}. It is not required that *@var{result} is the same as
-@var{entry}. If somethings goes wrong while exeucting @code{readdir_r}
-the function return @code{-1}. The @code{errno} variable is set like
+@var{entry}. If something goes wrong while executing @code{readdir_r}
+the function returns @code{-1}. The @code{errno} variable is set like
described for @code{readdir}.
@strong{Portability Note:} On some systems, @code{readdir_r} may not
diff --git a/manual/intro.texi b/manual/intro.texi
index b4cb344915..e0447b6d92 100644
--- a/manual/intro.texi
+++ b/manual/intro.texi
@@ -92,7 +92,7 @@ standards each function or symbol comes from.
The GNU C library is compatible with the C standard adopted by the
American National Standards Institute (ANSI):
@cite{American National Standard X3.159-1989---``ANSI C''} and later
-by the International Standardization Organizaion (ISO):
+by the International Standardization Organization (ISO):
@cite{ISO/IEC 9899:1990, ``Programming languages---C''}.
We here refer to the standard as @w{ISO C} since this is the more
general standard in respect of ratification.
diff --git a/manual/job.texi b/manual/job.texi
index 1ac15fffc4..f97aceb61c 100644
--- a/manual/job.texi
+++ b/manual/job.texi
@@ -54,7 +54,7 @@ terminate all the processes in the foreground process group.
@cindex session
A @dfn{session} is a larger group of processes. Normally all the
-proccesses that stem from a single login belong to the same session.
+processes that stem from a single login belong to the same session.
Every process belongs to a process group. When a process is created, it
becomes a member of the same process group and session as its parent
@@ -154,7 +154,7 @@ calls @code{setsid} to become the leader of a new session.
@cindex controlling terminal, access to
Processes in the foreground job of a controlling terminal have
-unrestricted access to that terminal; background proesses do not. This
+unrestricted access to that terminal; background processes do not. This
section describes in more detail what happens when a process in a
background job tries to access its controlling terminal.
@@ -213,7 +213,7 @@ involved.
@iftex
@itemize @bullet
-@item
+@item
@ref{Data Structures}, introduces the example and presents
its primary data structures.
@@ -310,7 +310,7 @@ job *
find_job (pid_t pgid)
@{
job *j;
-
+
for (j = first_job; j; j = j->next)
if (j->pgid == pgid)
return j;
@@ -324,7 +324,7 @@ int
job_is_stopped (job *j)
@{
process *p;
-
+
for (p = j->first_process; p; p = p->next)
if (!p->completed && !p->stopped)
return 0;
@@ -338,7 +338,7 @@ int
job_is_completed (job *j)
@{
process *p;
-
+
for (p = j->first_process; p; p = p->next)
if (!p->completed)
return 0;
@@ -355,7 +355,7 @@ job_is_completed (job *j)
When a shell program that normally performs job control is started, it
has to be careful in case it has been invoked from another shell that is
-already doing its own job control.
+already doing its own job control.
A subshell that runs interactively has to ensure that it has been placed
in the foreground by its parent shell before it can enable job control
@@ -413,7 +413,7 @@ int shell_is_interactive;
void
init_shell ()
@{
-
+
/* @r{See if we are running interactively.} */
shell_terminal = STDIN_FILENO;
shell_is_interactive = isatty (shell_terminal);
@@ -512,7 +512,7 @@ send a @code{SIGTSTP} signal to the process group of the process, not
just to the process itself. @xref{Signaling Another Process}.
Finally, each child process should call @code{exec} in the normal way.
-This is also the point at which redirection of the standard input and
+This is also the point at which redirection of the standard input and
output channels should be handled. @xref{Duplicating Descriptors},
for an explanation of how to do this.
@@ -564,9 +564,9 @@ launch_process (process *p, pid_t pgid,
@{
dup2 (errfile, STDERR_FILENO);
close (errfile);
- @}
-
- /* @r{Exec the new process. Make sure we exit.} */
+ @}
+
+ /* @r{Exec the new process. Make sure we exit.} */
execvp (p->argv[0], p->argv);
perror ("execvp");
exit (1);
@@ -590,7 +590,7 @@ launch_job (job *j, int foreground)
process *p;
pid_t pid;
int mypipe[2], infile, outfile;
-
+
infile = j->stdin;
for (p = j->first_process; p; p = p->next)
@{
@@ -638,7 +638,7 @@ launch_job (job *j, int foreground)
close (outfile);
infile = mypipe[0];
@}
-
+
format_job_info (j, "launched");
if (!shell_is_interactive)
@@ -704,13 +704,13 @@ put_job_in_foreground (job *j, int cont)
perror ("kill (SIGCONT)");
@}
@end group
-
+
/* @r{Wait for it to report.} */
wait_for_job (j);
-
+
/* @r{Put the shell back in the foreground.} */
tcsetpgrp (shell_terminal, shell_pgid);
-
+
@group
/* @r{Restore the shell's terminal modes.} */
tcgetattr (shell_terminal, &j->tmodes);
@@ -722,7 +722,7 @@ put_job_in_foreground (job *j, int cont)
@cindex background job, launching
If the process group is launched as a background job, the shell should
remain in the foreground itself and continue to read commands from
-the terminal.
+the terminal.
In the sample shell, there is not much that needs to be done to put
a job into the background. Here is the function it uses:
@@ -833,7 +833,7 @@ update_status (void)
@{
int status;
pid_t pid;
-
+
do
pid = waitpid (WAIT_ANY, &status, WUNTRACED|WNOHANG);
while (!mark_process_status (pid, status));
@@ -849,11 +849,11 @@ wait_for_job (job *j)
@{
int status;
pid_t pid;
-
+
do
pid = waitpid (WAIT_ANY, &status, WUNTRACED);
- while (!mark_process_status (pid, status)
- && !job_is_stopped (j)
+ while (!mark_process_status (pid, status)
+ && !job_is_stopped (j)
&& !job_is_completed (j));
@}
@end group
@@ -880,7 +880,7 @@ do_job_notification (void)
/* @r{Update status information for child processes.} */
update_status ();
-
+
jlast = NULL;
for (j = first_job; j; j = jnext)
@{
@@ -976,7 +976,7 @@ allocated and initialized.
Most real shells provide a complex user interface that has support for
a command language; variables; abbreviations, substitutions, and pattern
matching on file names; and the like. All of this is far too complicated
-to explain here! Instead, we have concentrated on showing how to
+to explain here! Instead, we have concentrated on showing how to
implement the core process creation and job control functions that can
be called from such a shell.
@@ -1058,7 +1058,7 @@ represents the size of a string large enough to hold the file name
returned by @code{ctermid}.
@end deftypevr
-See also the @code{isatty} and @code{ttyname} functions, in
+See also the @code{isatty} and @code{ttyname} functions, in
@ref{Is It a Terminal}.
diff --git a/manual/libc.texinfo b/manual/libc.texinfo
index fa3f3e443d..f2b688400e 100644
--- a/manual/libc.texinfo
+++ b/manual/libc.texinfo
@@ -616,7 +616,7 @@ Pseudo-Random Numbers
Low-Level Arithmetic Functions
* Normalization Functions:: Hacks for radix-2 representations.
-* Rounding and Remainders:: Determinining the integer and
+* Rounding and Remainders:: Determining the integer and
fractional parts of a float.
* Integer Division:: Functions for performing integer division.
* Parsing of Numbers:: Functions for ``reading'' numbers from strings.
diff --git a/manual/locale.texi b/manual/locale.texi
index cfe6b7e94b..1866c66fb7 100644
--- a/manual/locale.texi
+++ b/manual/locale.texi
@@ -505,7 +505,7 @@ precede the amount.
We can only guess which of these (if either) matches the usual
conventions for printing international currency symbols. Our guess is
-that they should always preceed the amount. If we find out a reliable
+that they should always precede the amount. If we find out a reliable
answer, we will put it here.
@item char p_sep_by_space
diff --git a/manual/math.texi b/manual/math.texi
index 870edd54bf..61455ef8a8 100644
--- a/manual/math.texi
+++ b/manual/math.texi
@@ -165,7 +165,7 @@ either positive or negative @code{HUGE_VAL}.
@node Inverse Trig Functions
@section Inverse Trigonometric Functions
-@cindex inverse trigonmetric functions
+@cindex inverse trigonometric functions
These are the usual arc sine, arc cosine and arc tangent functions,
which are the inverses of the sine, cosine and tangent functions,
diff --git a/manual/nss.texi b/manual/nss.texi
index e6c8649ddc..f24d7dd34c 100644
--- a/manual/nss.texi
+++ b/manual/nss.texi
@@ -5,7 +5,7 @@
@cindex Name Service Switch
@cindex NSS
-@cindex databses
+@cindex databases
Various functions in the C Library need to be configured to work
correctly in the local environment. Traditionally, this was done by
using files (e.g., @file{/etc/passwd}), but other nameservices (line the
@@ -128,7 +128,7 @@ the reaction on lookup result line @code{[NOTFOUND=return]}.
@menu
* Services in the NSS configuration:: Service names in the NSS configuration.
-* Actions in the NSS configuration:: React approprite on the lookup result.
+* Actions in the NSS configuration:: React appropriately to the lookup result.
* Notes on NSS Configuration File:: Things to take care about while
configuring NSS.
@end menu
@@ -181,7 +181,7 @@ service. They mean
@ftable @samp
@item success
-No error occured an the wanted entry is returned. The default action
+No error occurred and the wanted entry is returned. The default action
for this is @code{return}.
@item notfound
diff --git a/manual/pattern.texi b/manual/pattern.texi
index 903aa48073..b1e7206b58 100644
--- a/manual/pattern.texi
+++ b/manual/pattern.texi
@@ -178,7 +178,7 @@ To return this vector, @code{glob} stores both its address and its
length (number of elements, not counting the terminating null pointer)
into @code{*@var{vector-ptr}}.
-Normally, @code{glob} sorts the file names alphabetically before
+Normally, @code{glob} sorts the file names alphabetically before
returning them. You can turn this off with the flag @code{GLOB_NOSORT}
if you want to get the information as fast as possible. Usually it's
a good idea to let @code{glob} sort them---if you process the files in
@@ -224,7 +224,7 @@ In the event of an error, @code{glob} stores information in
@node Flags for Globbing
@subsection Flags for Globbing
-This section describes the flags that you can specify in the
+This section describes the flags that you can specify in the
@var{flags} argument to @code{glob}. Choose the flags you want,
and combine them with the C bitwise OR operator @code{|}.
@@ -483,7 +483,7 @@ One of the endpoints in a range expression was invalid.
These are the bit flags that you can use in the @var{cflags} operand when
compiling a regular expression with @code{regcomp}.
-
+
@table @code
@comment regex.h
@comment POSIX.2
@@ -530,7 +530,7 @@ This function tries to match the compiled regular expression
@code{regexec} returns @code{0} if the regular expression matches;
otherwise, it returns a nonzero value. See the table below for
what nonzero values mean. You can use @code{regerror} to produce an
-error message string describing the reason for a nonzero value;
+error message string describing the reason for a nonzero value;
see @ref{Regexp Cleanup}.
The argument @var{eflags} is a word of bit flags that enable various
@@ -538,7 +538,7 @@ options.
If you want to get information about what part of @var{string} actually
matched the regular expression or its subexpressions, use the arguments
-@var{matchptr} and @var{nmatch}. Otherwise, pass @code{0} for
+@var{matchptr} and @var{nmatch}. Otherwise, pass @code{0} for
@var{nmatch}, and @code{NULL} for @var{matchptr}. @xref{Regexp
Subexpressions}.
@end deftypefun
@@ -549,7 +549,7 @@ locales that were in effect when you compiled the regular expression.
The function @code{regexec} accepts the following flags in the
@var{eflags} argument:
-@table @code
+@table @code
@comment regex.h
@comment POSIX.2
@item REG_NOTBOL
@@ -594,7 +594,7 @@ subexpression.
@comment POSIX.2
@deftp {Data Type} regmatch_t
This is the data type of the @var{matcharray} array that you pass to
-@code{regexec}. It containes two structure fields, as follows:
+@code{regexec}. It contains two structure fields, as follows:
@table @code
@item rm_so
@@ -661,7 +661,7 @@ appears within another, then the results reported for the inner
subexpression reflect whatever happened on the last match of the outer
subexpression. For an example, consider @samp{\(ba\(na\)*s \)*} matching
the string @samp{bananas bas }. The last time the inner expression
-actually matches is near the end of the first word. But it is
+actually matches is near the end of the first word. But it is
@emph{considered} again in the second word, and fails to match there.
@code{regexec} reports nonuse of the ``na'' subexpression.
@@ -738,7 +738,7 @@ char *get_regerror (int errcode, regex_t *compiled)
@cindex word expansion
@cindex expansion of shell words
-@dfn{Word expansion} means the process of splitting a string into
+@dfn{Word expansion} means the process of splitting a string into
@dfn{words} and substituting for variables, commands, and wildcards
just as the shell does.
@@ -936,7 +936,7 @@ data it points to.
@node Flags for Wordexp
@subsection Flags for Word Expansion
-This section describes the flags that you can specify in the
+This section describes the flags that you can specify in the
@var{flags} argument to @code{wordexp}. Choose the flags you want,
and combine them with the C operator @code{|}.
@@ -1139,7 +1139,7 @@ characters in the value of @var{variable}. @samp{$@{#foo@}} stands for
@end table
These variants of variable substitution let you remove part of the
-variable's value before substituting it. The @var{prefix} and
+variable's value before substituting it. The @var{prefix} and
@var{suffix} are not mere strings; they are wildcard patterns, just
like the patterns that you use to match multiple file names. But
in this context, they match against parts of the variable value
diff --git a/manual/signal.texi b/manual/signal.texi
index 088c35d02f..1a4f866876 100644
--- a/manual/signal.texi
+++ b/manual/signal.texi
@@ -135,7 +135,7 @@ process that receives them. These signals arrive at unpredictable times
during execution. External events generate signals asynchronously, and
so do explicit requests that apply to some other process.
-A given type of signal is either typically synchrous or typically
+A given type of signal is either typically synchronous or typically
asynchronous. For example, signals for errors are typically synchronous
because errors generate signals synchronously. But any type of signal
can be generated synchronously or asynchronously with an explicit
@@ -608,7 +608,7 @@ code profiling facilities, hence the name of this signal.
The signals listed in this section are used in conjunction with
asynchronous I/O facilities. You have to take explicit action by
-calling @code{fcntl} to enable a particular file descriptior to generate
+calling @code{fcntl} to enable a particular file descriptor to generate
these signals (@pxref{Interrupt Input}). The default action for these
signals is to ignore them.
@@ -2310,7 +2310,7 @@ signals to any random process. These are intended to prevent antisocial
behavior such as arbitrarily killing off processes belonging to another
user. In typical use, @code{kill} is used to pass signals between
parent, child, and sibling processes, and in these situations you
-normally do have permission to send signals. The only common execption
+normally do have permission to send signals. The only common exception
is when you run a setuid program in a child process; if the program
changes its real UID as well as its effective UID, you may not have
permission to send a signal. The @code{su} program does this.
@@ -2692,7 +2692,7 @@ install_handler (void)
@end smallexample
This is more reliable than blocking the other signals explicitly in the
-code for the handler. If you block signals explicity in the handler,
+code for the handler. If you block signals explicitly in the handler,
you can't avoid at least a short interval at the beginning of the
handler where they are not yet blocked.
@@ -2837,7 +2837,7 @@ these things in the other order, like this,
@noindent<