Typo.

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

diff --git a/docs/manual/dns-caveats.html.en b/docs/manual/dns-caveats.html.en
index 226a5ecabf7c1d13ab960b3303134b42facfda4b..c826a0aa182e3653bbd925360dfe2e9020fc699a 100644 (file)
--- a/docs/manual/dns-caveats.html.en
+++ b/docs/manual/dns-caveats.html.en
@@ -92,18 +92,18 @@
     <p>Suppose that you've assigned 10.0.0.1 to
     <code>www.abc.dom</code> and 10.0.0.2 to
     <code>www.def.dom</code>. Furthermore, suppose that
-    <code>def.com</code> has control of their own DNS. With this
-    config you have put <code>def.com</code> into a position where
-    they can steal all traffic destined to <code>abc.com</code>. To
+    <code>def.dom</code> has control of their own DNS. With this
+    config you have put <code>def.dom</code> into a position where
+    they can steal all traffic destined to <code>abc.dom</code>. To
     do so, all they have to do is set <code>www.def.dom</code> to
     10.0.0.1. Since they control their own DNS you can't stop them
-    from pointing the <code>www.def.com</code> record wherever they
+    from pointing the <code>www.def.dom</code> record wherever they
     wish.</p>
     
     <p>Requests coming in to 10.0.0.1 (including all those where
     users typed in URLs of the form
     <code>http://www.abc.dom/whatever</code>) will all be served by
-    the <code>def.com</code> virtual host. To better understand why
+    the <code>def.dom</code> virtual host. To better understand why
     this happens requires a more in-depth discussion of how Apache
     matches up incoming requests with the virtual host that will
     serve it. A rough document describing this <a href="vhosts/details.html">is available</a>.</p>

diff --git a/docs/manual/dns-caveats.xml b/docs/manual/dns-caveats.xml
index eb0f8f3a3a44668f53f3c738aea68ab9edbcafdf..157b66d45dddd61d53f931d94537f13cd66f822e 100644 (file)
--- a/docs/manual/dns-caveats.xml
+++ b/docs/manual/dns-caveats.xml
@@ -99,18 +99,18 @@
     <p>Suppose that you've assigned 10.0.0.1 to
     <code>www.abc.dom</code> and 10.0.0.2 to
     <code>www.def.dom</code>. Furthermore, suppose that
-    <code>def.com</code> has control of their own DNS. With this
-    config you have put <code>def.com</code> into a position where
-    they can steal all traffic destined to <code>abc.com</code>. To
+    <code>def.dom</code> has control of their own DNS. With this
+    config you have put <code>def.dom</code> into a position where
+    they can steal all traffic destined to <code>abc.dom</code>. To
     do so, all they have to do is set <code>www.def.dom</code> to
     10.0.0.1. Since they control their own DNS you can't stop them
-    from pointing the <code>www.def.com</code> record wherever they
+    from pointing the <code>www.def.dom</code> record wherever they
     wish.</p>
     
     <p>Requests coming in to 10.0.0.1 (including all those where
     users typed in URLs of the form
     <code>http://www.abc.dom/whatever</code>) will all be served by
-    the <code>def.com</code> virtual host. To better understand why
+    the <code>def.dom</code> virtual host. To better understand why
     this happens requires a more in-depth discussion of how Apache
     matches up incoming requests with the virtual host that will
     serve it. A rough document describing this <a
@@ -206,4 +206,4 @@
     been deployed widely enough to be put into use on critical
     webservers.</p>
   </section>
-</manualpage>
\ No newline at end of file
+</manualpage>