Merge in APR[-util] macros from branches/trunk-buildconf-noapr

[apache] / docs / manual / mod / mod_usertrack.xml

diff --git a/docs/manual/mod/mod_usertrack.xml b/docs/manual/mod/mod_usertrack.xml
index 734b866b989bd63d62c6134e76cf0028409c0dc4..c85294c838fee703710c956f1f317ad462a53231 100644 (file)
--- a/docs/manual/mod/mod_usertrack.xml
+++ b/docs/manual/mod/mod_usertrack.xml
@@ -41,10 +41,10 @@
     <p><module>mod_usertrack</module> sets a cookie which can be logged
     via <module>mod_log_config</module> configurable logging formats:</p>
 
-    <example>
-    LogFormat "%{Apache}n %r %t" usertrack<br />
-    CustomLog logs/clickstream.log usertrack
-    </example>
+    <highlight language="config">
+LogFormat "%{Apache}n %r %t" usertrack
+CustomLog "logs/clickstream.log" usertrack
+    </highlight>
 
 </section>
 
@@ -68,24 +68,24 @@
 
     <p>The domain string <strong>must</strong> begin with a dot, and
     <strong>must</strong> include at least one embedded dot. That is,
-    <code>.example.com</code> is legal, but <code>www.example.com</code> and 
+    <code>.example.com</code> is legal, but <code>www.example.com</code> and
     <code>.com</code> are not.</p>
 
     <note>Most browsers in use today will not allow cookies to be set
-    for a two-part top level domain, such as <code>.co.uk</code>, 
+    for a two-part top level domain, such as <code>.co.uk</code>,
     although such a domain ostensibly fulfills the requirements
-    above.<br /> 
-    
+    above.<br />
+
     These domains are equivalent to top level domains such as
     <code>.com</code>, and allowing such cookies may be a security
     risk. Thus, if you are under a two-part top level domain, you
     should still use your actual domain, as you would with any other top
     level domain (for example <code>.example.co.uk</code>).
-    </note> 
+    </note>
 
-    <example>
+    <highlight language="config">
     CookieDomain .example.com
-    </example>
+    </highlight>
 </usage>
 </directivesynopsis>
 
@@ -114,9 +114,9 @@
     <p>If this directive is not used, cookies last only for the
     current browser session.</p>
 
-    <example>
+    <highlight language="config">
     CookieExpires "3 weeks"
-    </example>
+    </highlight>
 </usage>
 </directivesynopsis>
 
@@ -142,9 +142,9 @@
     unpredictable if you use a name containing unusual characters.
     Valid characters include A-Z, a-z, 0-9, "_", and "-".</p>
 
-    <example>
+    <highlight language="config">
     CookieName clicktrack
-    </example>
+    </highlight>
 </usage>
 
 </directivesynopsis>
@@ -185,9 +185,9 @@
     three of these formats, with <code>Cookie2</code> being the
     preferred format.</p>
 
-    <example>
+    <highlight language="config">
     CookieStyle Cookie2
-    </example>
+    </highlight>
 </usage>
 </directivesynopsis>
 
@@ -212,12 +212,12 @@
     user-tracking cookie for all new requests. This directive can
     be used to turn this behavior on or off on a per-server or
     per-directory basis. By default, enabling
-    <module>mod_usertrack</module> will <strong>not</strong> 
+    <module>mod_usertrack</module> will <strong>not</strong>
     activate cookies. </p>
 
-    <example>
+    <highlight language="config">
     CookieTracking on
-    </example>
+    </highlight>
 
 </usage>
 </directivesynopsis>