some more typo fixes

<compatibility>Available in Apache 2.0.31 and later</compatibility>

<usage>

    <p>This directive allows a user to specifiy a timeout on proxy requests.

    <p>This directive allows a user to specify a timeout on proxy requests.

    This is useful when you have a slow/buggy appserver which hangs, and you

    would rather just return a timeout and fail gracefully instead of waiting

    however long it takes the server to return.</p>

slash or protocol name) substitution encounters the end of a rule set.  

See the <directive module="mod_rewrite">RewriteBase</directive> 

directive for more information regarding what prefix will be added back to 

relative substitions.</li>

relative substitutions.</li>

<li> If you wish to match against the full URL-path in a per-directory 

(htaccess) RewriteRule, use the <code>%{REQUEST_URI}</code> variable in

    consumes minimum CPU cycles under runtime and hence can be always used

    without drawbacks. The source used for seeding the PRNG contains of the

    current time, the current process id and (when applicable) a randomly

    choosen 1KB extract of the inter-process scoreboard structure of Apache.

    chosen 1KB extract of the inter-process scoreboard structure of Apache.

    The drawback is that this is not really a strong source and at startup

    time (where the scoreboard is still not available) this source just

    produces a few bytes of entropy. So you should always, at least for the

used both in per-server and per-directory context. In per-server context it

applies to the client authentication process used in the standard SSL

handshake when a connection is established. In per-directory context it forces

a SSL renegotation with the reconfigured client verification depth after the

a SSL renegotiation with the reconfigured client verification depth after the

HTTP request was read but before the HTTP response is sent.</p>

<p>

The depth actually is the maximum number of intermediate certificate issuers,