You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by tr...@apache.org on 2012/08/20 21:23:21 UTC
svn commit: r1375173 - in /httpd/httpd/branches/2.2.x/docs/manual:
developer/modules.xml mod/mod_ssl.xml
Author: trawick
Date: Mon Aug 20 19:23:21 2012
New Revision: 1375173
URL: http://svn.apache.org/viewvc?rev=1375173&view=rev
Log:
s/it's/its/ and fix another minor error
Modified:
httpd/httpd/branches/2.2.x/docs/manual/developer/modules.xml
httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml
Modified: httpd/httpd/branches/2.2.x/docs/manual/developer/modules.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/developer/modules.xml?rev=1375173&r1=1375172&r2=1375173&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/developer/modules.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/developer/modules.xml Mon Aug 20 19:23:21 2012
@@ -120,7 +120,7 @@ static void register_hooks(void)
<p>In the <code>mod_mmap_static</code> case I didn't care about the
<code>post_config</code> stage, but the <code>mmap_static_xlat</code>
- <strong>must</strong> be called after the core module had done it's name
+ <strong>must</strong> be called after the core module had done its name
translation, hence the use of the aszPre to define a modifier to the
position <code>HOOK_LAST</code>.</p>
</section>
Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml?rev=1375173&r1=1375172&r2=1375173&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml Mon Aug 20 19:23:21 2012
@@ -310,7 +310,7 @@ in the global server context because the
The following <em>source</em> variants are available:</p>
<ul>
<li><code>builtin</code>
- <p> This is the always available builtin seeding source. It's usage
+ <p> This is the always available builtin seeding source. Its usage
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
@@ -345,9 +345,9 @@ The following <em>source</em> variants a
On some platforms like FreeBSD one can even control how the entropy is
actually generated, i.e. by which system interrupts. More details one can
find under <em>rndcontrol(8)</em> on those platforms. Alternatively, when
- your system lacks such a random device, you can use tool
+ your system lacks such a random device, you can use a tool
like <a href="http://www.lothar.com/tech/crypto/">EGD</a>
- (Entropy Gathering Daemon) and run it's client program with the
+ (Entropy Gathering Daemon) and run its client program with the
<code>exec:/path/to/program/</code> variant (see below) or use
<code>egd:/path/to/egd-socket</code> (see below).</p></li>
@@ -550,7 +550,7 @@ The available (case-insensitive) <em>pro
<li><code>SSLv2</code>
<p>
This is the Secure Sockets Layer (SSL) protocol, version 2.0. It is the
- original SSL protocol as designed by Netscape Corporation. Though it's
+ original SSL protocol as designed by Netscape Corporation. Though its
use has been deprecated, because of weaknesses in the security of the protocol.</p></li>
<li><code>SSLv3</code>