More documentation consistency cleanup for 1.3.2.

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

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/manual/content-negotiation.html b/docs/manual/content-negotiation.html
index b4f035e880..73e534e6f9 100644
--- a/docs/manual/content-negotiation.html
+++ b/docs/manual/content-negotiation.html
@@ -85,7 +85,7 @@ information about each of the variants. This is done in one of two
 ways:
 
 <UL>
-  <LI> Using a type map (i.e., a <CODE>*.var</CODE> file) which
+  <LI> Using a type map (<EM>i.e.</EM>, a <CODE>*.var</CODE> file) which
        names the files containing the variants explicitly
   <LI> Or using a 'MultiViews' search, where the server does an implicit
        filename pattern match, and chooses from among the results.
@@ -167,8 +167,8 @@ The full list of headers recognized is:
        <CODE>text/html;&nbsp;level=3</CODE>.
   <DT> <CODE>Content-language:</CODE>
   <DD> The languages of the variant, specified as an Internet standard
-       language code (e.g., <CODE>en</CODE> for English,
-       <CODE>kr</CODE> for Korean, etc.).
+       language code (<EM>e.g.</EM>, <CODE>en</CODE> for English,
+       <CODE>kr</CODE> for Korean, <EM>etc.</EM>).
   <DT> <CODE>Content-encoding:</CODE>
   <DD> If the file is compressed, or otherwise encoded, rather than
        containing the actual raw data, this says how that was done.
@@ -491,12 +491,12 @@ hyperlinks:
 Looking at the table above you will notice that it is always possible to
 use the name without any extensions  in an hyperlink (<EM>e.g.</EM>, <SAMP>foo</SAMP>).
 The advantage is that you can hide the actual type of a
-document rsp. file and can change it later, e.g. from <SAMP>html</SAMP>
+document rsp. file and can change it later, <EM>e.g.</EM>, from <SAMP>html</SAMP>
 to <SAMP>shtml</SAMP> or <SAMP>cgi</SAMP> without changing any
 hyperlink references.
 
 <P>
-If you want to continue to use a MIME-type in your hyperlinks (e.g.
+If you want to continue to use a MIME-type in your hyperlinks (<EM>e.g.</EM>
 <SAMP>foo.html</SAMP>) the language extension (including an encoding extension
 if there is one) must be on the right hand side of the MIME-type extension
 (<EM>e.g.</EM>, <SAMP>foo.html.en</SAMP>).