From: Igor Galić Date: Wed, 11 Apr 2012 11:00:16 +0000 (+0000) Subject: Be consistent with *s' usage. Thank you, the oatmeal. X-Git-Tag: 2.5.0-alpha~7207 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d163262e2d39976aa2729074da6d59a32966d99e;p=apache Be consistent with *s' usage. Thank you, the oatmeal. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1324697 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/perf-tuning.xml b/docs/manual/misc/perf-tuning.xml index c9630446cf..6e8977343b 100644 --- a/docs/manual/misc/perf-tuning.xml +++ b/docs/manual/misc/perf-tuning.xml @@ -904,7 +904,7 @@

The -l option tells truss to log the ID of the - LWP (lightweight process--Solaris's form of kernel-level thread) + LWP (lightweight process--Solaris' form of kernel-level thread) that invokes each system call.

Other systems may have different system call tracing utilities @@ -974,7 +974,7 @@

Next, the worker thread puts the connection to the client (file descriptor 9) in non-blocking mode. The setsockopt(2) and getsockopt(2) calls are a side-effect of how - Solaris's libc handles fcntl(2) on sockets.

+ Solaris' libc handles fcntl(2) on sockets.

/65:    read(9, " G E T   / 1 0 k . h t m".., 8000)     = 97
diff --git a/docs/manual/mod/mod_lbmethod_byrequests.xml b/docs/manual/mod/mod_lbmethod_byrequests.xml index a9a718153b..41be7d0e7a 100644 --- a/docs/manual/mod/mod_lbmethod_byrequests.xml +++ b/docs/manual/mod/mod_lbmethod_byrequests.xml @@ -46,7 +46,7 @@ provides the byrequests load balancing method..

of the number of requests. It works as follows:

lbfactor is how much we expect this worker - to work, or the workers's work quota. This is + to work, or the workers' work quota. This is a normalized value representing their "share" of the amount of work to be done.

diff --git a/docs/manual/mod/mpmt_os2.xml b/docs/manual/mod/mpmt_os2.xml index 63a41290ef..e4f70e8890 100644 --- a/docs/manual/mod/mpmt_os2.xml +++ b/docs/manual/mod/mpmt_os2.xml @@ -32,7 +32,7 @@

The Server consists of a main, parent process and a small, static number of child processes.

-

The parent process's job is to manage the child processes. This +

The parent process' job is to manage the child processes. This involves spawning children as required to ensure there are always StartServers processes accepting connections.