svn commit: r800176 - in /websites/staging/trafficserver/trunk/content/docs/trunk/admin: configuration-files/records.config.en.html reverse-proxy-http-redirects/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Mon Dec 12 20:24:29 2011
New Revision: 800176

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html Mon Dec 12 20:24:29 2011
@@ -1038,7 +1038,7 @@ would listed to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
-<p>Indicates whether to utilize SRV records for orgin server lookup.</p>
+<p>Indicates whether to use SRV records for orgin server lookup.</p>
 </dd>
 </dl>
 <h1 id="HostDB">HostDB</h1>
@@ -1046,7 +1046,7 @@ would listed to ports <code>6060</code>,
 <dt id="proxy.config.hostdb.serve_stale_for"><em><code>proxy.config.hostdb.serve_stale_for</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
-<dd>The number of seconds for which to utilize a stale NS record whileinitiating a background fetch for the new data.</dd>
+<dd>The number of seconds for which to use a stale NS record while initiating a background fetch for the new data.</dd>
 <dt id="proxy.config.hostdb.storage_size"><em><code>proxy.config.hostdb.storage_size</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>33554432</code></dd>

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.html Mon Dec 12 20:24:29 2011
@@ -25,7 +25,7 @@
       </div>
       <div class="eightcol last" style="margin-top: 15px;">
         
-        <div id="header-main">Apache Traffic Server</div>
+        <div id="header-main">Adminstrator&#39;s Guide</div>
         
         <div id="header-sub">Reverse Proxy and HTTP Redirects </div>
       </div>
@@ -124,7 +124,7 @@ data. For example, Traffic Server can be
 of a trans-Atlantic link to serve users without having to fetch the request 
 and content across expensive international connections. Unlike replication, 
 for which hardware must be configured to replicate all data and to handle peak 
-capacity, Traffic Server dynamically adjusts to best utilize the serving and 
+capacity, Traffic Server dynamically adjusts to optimally use the serving and 
 storing capacity of the hardware. Traffic Server is also designed to keep content 
 fresh automatically, thereby eliminating the complexity of updating remote 
 origin servers. </p>