aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/pies.texi14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/pies.texi b/doc/pies.texi
index c72ac3e..15c37e1 100644
--- a/doc/pies.texi
+++ b/doc/pies.texi
@@ -774,7 +774,7 @@ entered.
The process will be executed when the specified @dfn{ondemand}
runlevel is called (@samp{a}, @samp{b} and @samp{c}). No real
runlevel change will occur (@pxref{Ondemand runlevels}).
-The process will remain running accross any eventual runlevel changes
+The process will remain running across any eventual runlevel changes
and will be restarted whenever it terminates, similarly to
@code{respawn} components.
@@ -877,7 +877,7 @@ names, instead of IP addresses.
@kwindex siggroup
@item siggroup
-This flag affects the befavior of @command{pies} when a stopped
+This flag affects the behavior of @command{pies} when a stopped
process fails to terminate within a predefined timeout
(@pxref{shutdown-timeout}. Normally @command{pies} would send the
@samp{SIGKILL} signal to such a process. If this flag is set,
@@ -1324,7 +1324,7 @@ only for TCP sockets.
@end deffn
@deffn {Config: component} max-ip-connections @var{number}
-Miximum number of connections that can be opened simultaneously from a
+Maximum number of connections that can be opened simultaneously from a
single IP address.
@end deffn
@@ -2562,7 +2562,7 @@ built-in service (@pxref{qotd}).
@end table
The following statements allow to redefine state file names.
-Use them only if the defaults do not suit your needs, and niether
+Use them only if the defaults do not suit your needs, and neither
the @code{state-directory} statement nor the @option{--instance}
option can help:
@@ -2945,7 +2945,7 @@ Read configuration from @var{file} instead of the default
@item -d
@itemx --dump
-Dump obained responses verbatim. This is useful mainly for debugging
+Dump obtained responses verbatim. This is useful mainly for debugging
purposes.
@item -i @var{inst}
@@ -3182,7 +3182,7 @@ Multiuser with X11.
@anchor{Ondemand runlevels}
Additionally, three special runlevels @samp{a}, @samp{b} and @samp{c}
can be used to start @dfn{on-demand} components without actually
-changing the runlevel. Once started, on-demain components persist
+changing the runlevel. Once started, on-demand components persist
through eventual runlevel changes.
@node Init Process Configuration
@@ -3266,7 +3266,7 @@ on the console keyboard.
The process will be executed when the specified @dfn{ondemand}
runlevel is called (@samp{a}, @samp{b} and @samp{c}). No real
runlevel change will occur (@pxref{Ondemand runlevels}).
-The process will remain running accross any eventual runlevel changes
+The process will remain running across any eventual runlevel changes
and will be restarted whenever it terminates, similarly to
@code{respawn} components.

Return to:

Send suggestions and report system problems to the System administrator.