From: Rich Bowen
Date: Tue, 16 Mar 2010 12:48:31 +0000 (+0000)
Subject: In as much as we can be said to have consensus on anything at all, we
X-Git-Tag: 2.3.6~337
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0c0ac0138507e9081bec7a1ec6a776b190911b84;p=thirdparty%2Fapache%2Fhttpd.git
In as much as we can be said to have consensus on anything at all, we
appear to have consensus that we will refer to the product (in the
documentation) as Apache HTTPD, or HTTPD for short, and to the server
binary executable as httpd. Here's a few changes to that
effect.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@923712 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/bind.html.en b/docs/manual/bind.html.en
index 1adf4b60077..96c48450016 100644
--- a/docs/manual/bind.html.en
+++ b/docs/manual/bind.html.en
@@ -26,7 +26,7 @@
tr
-
Configuring Apache HTTP Server (httpd) to listen on specific addresses and ports.
+
Configuring Apache HTTPD to listen on specific addresses and ports.
The Apache HTTP Server is configured by placing directives in plain text
+
Apache HTTPD is configured by placing directives in plain text
configuration files. The main configuration file is usually called
httpd.conf. The location of this file is set at
compile-time, but may be overridden with the -f
diff --git a/docs/manual/configuring.xml b/docs/manual/configuring.xml
index d7b0f0f1692..2a59a993888 100644
--- a/docs/manual/configuring.xml
+++ b/docs/manual/configuring.xml
@@ -25,7 +25,7 @@
Configuration Files
-
This document describes the files used to configure the Apache HTTP server (httpd).
+
This document describes the files used to configure Apache HTTPD.
@@ -41,7 +41,7 @@
-
The Apache HTTP Server is configured by placing Apache HTTPD is configured by placing directives in plain text
configuration files. The main configuration file is usually called
httpd.conf. The location of this file is set at
diff --git a/docs/manual/content-negotiation.html.en b/docs/manual/content-negotiation.html.en
index fd7d98a8941..5acde5ad219 100644
--- a/docs/manual/content-negotiation.html.en
+++ b/docs/manual/content-negotiation.html.en
@@ -25,7 +25,7 @@
-
The Apache HTTP Server (httpd) supports content negotiation as described in
+
Apache HTTPD supports content negotiation as described in
the HTTP/1.1 specification. It can choose the best
representation of a resource based on the browser-supplied
preferences for media type, languages, character set and
diff --git a/docs/manual/content-negotiation.xml b/docs/manual/content-negotiation.xml
index 0d89fe4894f..306b9b7f9df 100644
--- a/docs/manual/content-negotiation.xml
+++ b/docs/manual/content-negotiation.xml
@@ -26,7 +26,7 @@
-
The Apache HTTP Server (httpd) supports content negotiation as described in
+
Apache HTTPD supports content negotiation as described in
the HTTP/1.1 specification. It can choose the best
representation of a resource based on the browser-supplied
preferences for media type, languages, character set and
diff --git a/docs/manual/custom-error.html.en b/docs/manual/custom-error.html.en
index cfb0263730c..43d9ae196e7 100644
--- a/docs/manual/custom-error.html.en
+++ b/docs/manual/custom-error.html.en
@@ -29,7 +29,7 @@
Although the Apache HTTP Server provides generic error responses
in the event of 4xx or 5xx HTTP status codes, these responses are
- rather stark, uninformative, and can be indimidating to site users.
+ rather stark, uninformative, and can be intimidating to site users.
You may wish to provide custom error responses which are either
friendlier, or in some language other than English, or perhaps which
are styled more in line with your site layout.
Custom error documents are configured using the ErrorDocument directive.
- ErrorDocument, which may be used in global,
+
Custom error documents are configured using the ErrorDocument directive,
+ which may be used in global,
virtualhost, or directory context. It may be used in .htaccess files
if AllowOverride is set to
FileInfo.
ErrorDocument <3-digit-code> <action>
@@ -197,7 +197,7 @@
provide more useful information to users about your site, and what
they can expect to find there.
This page could be summarized with the statement: don't
- configure Apache HTTPD in such a way that it relies on DNS resolution
+ configure Apache HTTP Server in such a way that it relies on DNS resolution
for parsing of the configuration files. If HTTPD requires DNS
resolution to parse the configuration files then your server
may be subject to reliability problems (ie. it might not boot),
diff --git a/docs/manual/dns-caveats.xml b/docs/manual/dns-caveats.xml
index 7250ba10d44..e47c0b32eda 100644
--- a/docs/manual/dns-caveats.xml
+++ b/docs/manual/dns-caveats.xml
@@ -22,11 +22,11 @@
- Issues Regarding DNS and Apache HTTPD
+ Issues Regarding DNS and Apache HTTP Server
This page could be summarized with the statement: don't
- configure Apache HTTPD in such a way that it relies on DNS resolution
+ configure Apache HTTP Server in such a way that it relies on DNS resolution
for parsing of the configuration files. If HTTPD requires DNS
resolution to parse the configuration files then your server
may be subject to reliability problems (ie. it might not boot),
diff --git a/docs/manual/dns-caveats.xml.ja b/docs/manual/dns-caveats.xml.ja
index c8f80dfd8e1..84976e3d61c 100644
--- a/docs/manual/dns-caveats.xml.ja
+++ b/docs/manual/dns-caveats.xml.ja
@@ -1,7 +1,7 @@
-
+
+
+
-
Stopping and Restarting - Apache HTTP Server
+Stopping and Restarting Apache HTTPD - Apache HTTP Server
@@ -16,7 +16,7 @@