--- a/xml/en/docs/http/converting_rewrite_rules.xml
+++ b/xml/en/docs/http/converting_rewrite_rules.xml
@@ -39,7 +39,7 @@ server {
 
 <para>
 This is a wrong, cumbersome, and ineffective way.
-The right way is to define a separate server for <url>example.org</url>:
+The right way is to define a separate server for <literal>example.org</literal>:
 
 <programlisting>
 server {
@@ -72,7 +72,7 @@ On versions prior to 0.9.1, redirects ca
 <para>
 Another example.
 Instead of the &ldquo;upside-down&rdquo; logic &ldquo;all that is not
-<url>example.com</url> and is not <url>www.example.com</url>&rdquo;:
+<literal>example.com</literal> and is not <literal>www.example.com</literal>&rdquo;:
 
 <programlisting>
 RewriteCond  %{HTTP_HOST}  !example.com
@@ -80,7 +80,7 @@ RewriteCond  %{HTTP_HOST}  !www.example.
 RewriteRule  (.*)          http://www.example.com$1
 </programlisting>
 
-one should simply define <url>example.com</url>, <url>www.example.com</url>,
+one should simply define <literal>example.com</literal>, <literal>www.example.com</literal>,
 and &ldquo;everything else&rdquo;:
 
 <programlisting>