[deployment-guide/comm-rel: 654/727] Corrected a handful of typing errors.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 13:20:41 UTC 2010
commit dc67492af72be09e8be97382baf13ee27846336d
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Tue Sep 14 16:10:18 2010 +0200
Corrected a handful of typing errors.
en-US/The_Apache_HTTP_Server.xml | 18 +++++++++---------
1 files changed, 9 insertions(+), 9 deletions(-)
---
diff --git a/en-US/The_Apache_HTTP_Server.xml b/en-US/The_Apache_HTTP_Server.xml
index d6c016b..02fbd3d 100644
--- a/en-US/The_Apache_HTTP_Server.xml
+++ b/en-US/The_Apache_HTTP_Server.xml
@@ -269,7 +269,7 @@ Syntax OK</screen>
The <replaceable>directory</replaceable> can be either a full path to an existing directory in the local file system, or a wildcard expression.
</para>
<para>
- This directive can be used to configure additional <literal>cgi-bin</literal> directories for server-side scripts located outside the directory that is specified by <option>ScriptAlias</option>. In this case, the <option>ExecCGI</option> and <option>AddHandler</option> directives must be supplied, and the permissons on the target directory must be set correctly (that is, <literal>0755</literal>).
+ This directive can be used to configure additional <literal>cgi-bin</literal> directories for server-side scripts located outside the directory that is specified by <option>ScriptAlias</option>. In this case, the <option>ExecCGI</option> and <option>AddHandler</option> directives must be supplied, and the permissions on the target directory must be set correctly (that is, <literal>0755</literal>).
</para>
<example id="example-apache-httpdconf-directory">
<title>Using the <option><Directory></option> directive</title>
@@ -615,7 +615,7 @@ Syntax OK</screen>
</para>
<screen>AddLanguage <replaceable>language</replaceable> <replaceable>extension</replaceable>…</screen>
<para>
- The <replaceable>language</replaceable> has to be a valide MIME language such as <literal>cs</literal>, <literal>en</literal>, or <literal>fr</literal>. The <replaceable>extension</replaceable> is a case sensitive file extension, and is conventionally written with a leading dot (for example, <literal>.cs</literal>).
+ The <replaceable>language</replaceable> has to be a valid MIME language such as <literal>cs</literal>, <literal>en</literal>, or <literal>fr</literal>. The <replaceable>extension</replaceable> is a case sensitive file extension, and is conventionally written with a leading dot (for example, <literal>.cs</literal>).
</para>
<para>
This directive is especially useful for web servers that serve content in multiple languages based on the client's language settings.
@@ -1144,7 +1144,7 @@ ErrorDocument 404 /404-not_found.html</screen>
<option>On</option>
</entry>
<entry>
- Enabes generating the detailed server status.
+ Enables generating the detailed server status.
</entry>
</row>
<row>
@@ -1853,7 +1853,7 @@ ErrorDocument 404 /404-not_found.html</screen>
</para>
<screen>MaxKeepAliveRequests <replaceable>number</replaceable></screen>
<para>
- A high <replaceable>number</replaceable> can improve the performence of the server. Note that using <literal>0</literal> allows unlimited number of requests. The default option is <option>100</option>.
+ A high <replaceable>number</replaceable> can improve the performance of the server. Note that using <literal>0</literal> allows unlimited number of requests. The default option is <option>100</option>.
</para>
<example id="example-apache-httpdconf-maxkeepaliverequests">
<title>Using the <option>MaxKeepAliveRequests</option> option</title>
@@ -2253,7 +2253,7 @@ ErrorDocument 404 /404-not_found.html</screen>
</para>
<screen>ServerName <replaceable>hostname</replaceable><optional>:<replaceable>port</replaceable></optional></screen>
<para>
- The <replaceable>hostname</replaceable> has to be a <firstterm>fully qualified domain name</firstterm> (FQDN) of the server. The <replaceable>port</replaceable> is optional, but when supplied, it has to match the number specified by the <option>Listen</option> directive.
+ The <replaceable>hostname</replaceable> has to be a <firstterm>fully qualified domain name</firstterm> (<acronym>FQDN</acronym>) of the server. The <replaceable>port</replaceable> is optional, but when supplied, it has to match the number specified by the <option>Listen</option> directive.
</para>
<para>
When using this directive, make sure that the IP address and server name pair are included in the <filename>/etc/hosts</filename> file.
@@ -2610,7 +2610,7 @@ ErrorDocument 404 /404-not_found.html</screen>
<screen>~]# <command>chmod a+x /home/<replaceable>username</replaceable>/</command>
~]# <command>chmod a+rx /home/<replaceable>username</replaceable>/public_html/</command></screen>
<para>
- All files in this directory must be set acordingly.
+ All files in this directory must be set accordingly.
</para>
</note>
<example id="example-apache-httpdconf-userdir">
@@ -2624,7 +2624,7 @@ ErrorDocument 404 /404-not_found.html</screen>
<section id="s2-apache-sslconf-common">
<title>Common <filename>ssl.conf</filename> Directives</title>
<para>
- The <firstterm>Secure Sockets Layer</firstterm> (<acronym>SSL</acronym>) directives allow you to customize the behavior of the Apache HTTP Secure Server, and in most cases, they are configured appropriately during the installation. Be careful when changing these settings, as incorrect configuration can lead to security vulnurabilities.
+ The <firstterm>Secure Sockets Layer</firstterm> (<acronym>SSL</acronym>) directives allow you to customize the behavior of the Apache HTTP Secure Server, and in most cases, they are configured appropriately during the installation. Be careful when changing these settings, as incorrect configuration can lead to security vulnerabilities.
</para>
<para>
The following directive is commonly used in <filename>/etc/httpd/conf.d/ssl.conf</filename>:
@@ -2952,7 +2952,7 @@ ErrorDocument 404 /404-not_found.html</screen>
When a web browser establishes a new SSL connection, it checks the certificate provided by the web server. If the certificate does not have a signature from a trusted CA, or if the hostname listed in the certificate does not match the hostname used to establish the connection, it refuses to communicate with the server and usually presents a user with an appropriate error message.
</para>
<para>
- By default, most web browsers are configured to trust a set of widely used certificate authorities. Because of this, an appropriate CA should be chosen when setting up a secure server, so that target users can trust the connection, otherwise they will be presented with an error messge, and will have to accept the certificate manually. Since encouraging users to override certificate errors can allow an attacker to intercept the connection, you should use a trusted CA whenever possible. For more information on this, see <xref linkend="table-apache-mod_ssl-certificates-authorities" />.
+ By default, most web browsers are configured to trust a set of widely used certificate authorities. Because of this, an appropriate CA should be chosen when setting up a secure server, so that target users can trust the connection, otherwise they will be presented with an error message, and will have to accept the certificate manually. Since encouraging users to override certificate errors can allow an attacker to intercept the connection, you should use a trusted CA whenever possible. For more information on this, see <xref linkend="table-apache-mod_ssl-certificates-authorities" />.
</para>
<table id="table-apache-mod_ssl-certificates-authorities">
<title>CA lists for most common web browsers</title>
@@ -2998,7 +2998,7 @@ ErrorDocument 404 /404-not_found.html</screen>
</tgroup>
</table>
<para>
- When setting up an SSL server, you need to generate a certificate request and a private key, and then send the certificate request, proof of the company's identity, and payment to a certificate authority. Once the CA verifies the certificate request and your identity, it will send you a signed certificate you can use with your server. Alternatively, you can create a self-signed certificate that does not contain a CA signuture, and thus should be used for testing purposes only.
+ When setting up an SSL server, you need to generate a certificate request and a private key, and then send the certificate request, proof of the company's identity, and payment to a certificate authority. Once the CA verifies the certificate request and your identity, it will send you a signed certificate you can use with your server. Alternatively, you can create a self-signed certificate that does not contain a CA signature, and thus should be used for testing purposes only.
</para>
</section>
<section id="s2-apache-mod_ssl-enabling">
More information about the docs-commits
mailing list