svn commit: r788042 [3/3] - /websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/

[bu...@apache.org]

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/storage.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/storage.config.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/storage.config.en.html Wed Apr  6 13:48:33 2011
@@ -46,7 +46,7 @@ you modify the <code>storage.config</cod
 Server.</p>
 <h2 id="Format">Format</h2>
 <p>The format of the <code>storage.config</code> file is:</p>
-<p><em><code>pathname size</code></em></p>
+<p id="pathname_size"><em><code>pathname size</code></em></p>
 <p>where <em><code>pathname</code></em> is the name of a partition, directory or
 file, and <em><code>size</code></em> is the size of the named partition,
 directory or file (in bytes). You must specify a size for

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/update.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/update.config.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/update.config.en.html Wed Apr  6 13:48:33 2011
@@ -90,28 +90,22 @@ URL sets, such as those used by Internet
 
 <p>The following list describes each field.</p>
 <dl>
-<dt><em><code>URL</code></em></dt>
+<dt id="URL"><em><code>URL</code></em></dt>
 <dd>HTTP-based URLs.</dd>
-<dt><em><code>request_headers</code></em></dt>
-<dd>Optional. A list of headers, separated by semicolons, passed in</dd>
+<dt id="request_headers"><em><code>request_headers</code></em></dt>
+<dd>Optional. A list of headers, separated by semicolons, passed in
+each <code>GET</code> request. You can define any request header that conforms
+to the HTTP specification; the default is no request header.</dd>
+<dt id="offset_hour"><em><code>offset_hour</code></em></dt>
+<dd>The base hour used to derive the update periods. The range is 00-23
+hours.</dd>
+<dt id="interval"><em><code>interval</code></em></dt>
+<dd>The interval (in seconds) at which updates should occur, starting
+at the offset hour.</dd>
+<dt id="recursion_depth"><em><code>recursion_depth</code></em></dt>
+<dd>The depth to which referenced URLs are recursively updated,
+starting at the given URL. This field applies only to HTTP.</dd>
 </dl>
-<p>each <code>GET</code> request. You can define any request header that conforms
-   to the HTTP specification; the default is no request header.</p>
-<dl>
-<dt><em><code>offset_hour</code></em></dt>
-<dd>The base hour used to derive the update periods. The range is 00-23</dd>
-</dl>
-<p>hours.</p>
-<dl>
-<dt><em><code>interval</code></em></dt>
-<dd>The interval (in seconds) at which updates should occur, starting</dd>
-</dl>
-<p>at the offset hour.</p>
-<dl>
-<dt><em><code>recursion_depth</code></em></dt>
-<dd>The depth to which referenced URLs are recursively updated,</dd>
-</dl>
-<p>starting at the given URL. This field applies only to HTTP.</p>
 <h2 id="Examples">Examples</h2>
 <p>An example HTTP scheduled update is provided below:</p>
 <div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">www</span><span class="o">.</span><span class="n">company</span><span class="o">.</span><span class="n">com</span><span class="o">\</span><span class="n">User</span><span class="o">-</span><span class="n">Agent:</span> <span class="n">noname</span> <span class="n">user</span> <span class="n">agent</span><span class="o">\</span><span class="mi">13</span><span class="o">\</span><span class="mi">3600</span><span class="o">\</span><span class="mi">5</span><span class="o">\</span>