sp

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@84787 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 12 insertions, 12 deletions

diff --git a/docs/conf/httpd-std.conf b/docs/conf/httpd-std.conf
index 6f45132efd..aaa3d1eb97 100644
--- a/docs/conf/httpd-std.conf
+++ b/docs/conf/httpd-std.conf
@@ -634,12 +634,12 @@ AddEncoding x-gzip gz tgz
 # a document. You can then use content negotiation to give a browser a 
 # file in a language the user can understand.
 #
-# Specify a default langyage. This means that all data
-# going out without a specific language tag (See below) will 
-# be marked with this one. You propably do NOT want to set
+# Specify a default language. This means that all data
+# going out without a specific language tag (see below) will 
+# be marked with this one. You probably do NOT want to set
 # this unless you are sure it is correct for all cases.
 #
-# * It is generally better to not mark a pages as in
+# * It is generally better to not mark a page as 
 # * being a certain language than marking it with the wrong
 # * language!
 #
@@ -650,13 +650,13 @@ AddEncoding x-gzip gz tgz
 # language code is pl) may wish to use "AddLanguage pl .po" to
 # avoid the ambiguity with the common suffix for perl scripts.
 #
-# Note 2: The example entries below illustrate that in quite
-# some cases the two character 'Language' abbriviation is not
+# Note 2: The example entries below illustrate that in 
+# some cases the two character 'Language' abbreviation is not
 # identical to the two character 'Country' code for its country,
 # E.g. 'Danmark/dk' versus 'Danish/da'.
 #
 # Note 3: In the case of 'ltz' we violate the RFC by using a three char
-# specifier. But there is 'work in progress' to fix this and get
+# specifier. There is 'work in progress' to fix this and get
 # the reference data for rfc1766 cleaned up.
 #
 # Danish (da) - Dutch (nl) - English (en) - Estonian (et)
@@ -698,16 +698,16 @@ LanguagePriority en da nl et fr de el it ja kr no pl pt pt-br ltz ca es sv
 # Specify a default charset for all pages sent out. This is
 # always a good idea and opens the door for future internationalisation
 # of your web site, should you ever want it. Specifying it as
-# a default does little harm; as the standart dictates that a page
-# is in iso-8859-1 (latin1) unless specified otherwise. I.e. you
+# a default does little harm; as the standard dictates that a page
+# is in iso-8859-1 (latin1) unless specified otherwise i.e. you
 # are merely stating the obvious. There are also some security
 # reasons in browsers, related to javascript and URL parsing
-# which encourage to always set a default char set.
+# which encourage you to always set a default char set.
 #
 AddDefaultCharset	ISO-8859-1
 
 #
-# Commonly used filename extensions to character sets. You propably
+# Commonly used filename extensions to character sets. You probably
 # want to avoid clashes with the language extensions, unless you
 # are good at carefully testing your setup after each change.
 #
@@ -725,7 +725,7 @@ AddCharset ISO-2022-KR .iso2022-kr .kis
 AddCharset ISO-2022-CN .iso2022-cn .cis
 
 # The set below does not map to a specific (iso) standard
-# but works on a fairly wide range of browser. Note that
+# but works on a fairly wide range of browsers. Note that
 # capitalization actually matters (it should not, but it
 # does for some browsers).
 #