trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1213417 - in /trafficserver/site/branches/ats-cms/content/docs/trunk/admin: configuration-files/records.config.en.mdtext reverse-proxy-http-redirects/index.en.mdtext
Date Mon, 12 Dec 2011 20:24:09 GMT
Author: igalic
Date: Mon Dec 12 20:24:08 2011
New Revision: 1213417

Tune a bit of wording, fix a typo.


Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
Mon Dec 12 20:24:08 2011
@@ -890,7 +890,7 @@ the `records.config` file.
 *`proxy.config.srv_enabled`* {#proxy.config.srv_enabled}
 :   `INT`
 :   Default: `0`
-:   Indicates whether to utilize SRV records for orgin server lookup.
+:   Indicates whether to use SRV records for orgin server lookup.
 # HostDB # {#HostDB}
@@ -898,7 +898,7 @@ the `records.config` file.
 *`proxy.config.hostdb.serve_stale_for`* {#proxy.config.hostdb.serve_stale_for}
 :  `INT`
 :  Default: `0`
-:  The number of seconds for which to utilize a stale NS record whileinitiating a background
fetch for the new data.
+:  The number of seconds for which to use a stale NS record while initiating a background
fetch for the new data.
 *`proxy.config.hostdb.storage_size`* {#proxy.config.hostdb.storage_size}
 :  `INT`

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext
Mon Dec 12 20:24:08 2011
@@ -71,7 +71,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. 

View raw message