svn commit: r789602 - in /websites/staging/trafficserver/trunk/content/docs/trunk/admin: cluster-howto/index.en.html security-options/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Sun May 15 01:09:23 2011
New Revision: 789602

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html Sun May 15 01:09:23 2011
@@ -115,7 +115,7 @@ in the cluster. You must change the clus
 individually. You may following these instructions:</p>
 <ol>
 <li>
-<p>setup the same cluster name, or proxy name(let us name it MyCluster):</p>
+<p>setup the same cluster name, or proxy name, e.g. MyCluster:</p>
 <div class="codehilite"><pre><span class="n">traffic_line</span> <span class="o">-</span><span class="n">s</span> <span class="n">proxy</span><span class="o">.</span><span class="n">config</span><span class="o">.</span><span class="n">proxy_name</span> <span class="o">-</span><span class="n">v</span> <span class="n">MyCluster</span>
 </pre></div>
 
@@ -127,11 +127,7 @@ individually. You may following these in
 </pre></div>
 
 
-<p><strong>Config Variable Description:</strong>
-    <em>proxy.local.cluster.type</em>
-     1 for full-clustering mode.
-     2 for management-only mode.
-     3 for no clustering.</p>
+<p>Refer to <a href="../configuration-files/records.config#proxy.local.cluster.type"><code>proxy.local.cluster.type</code></a> for a full description.</p>
 </li>
 <li>
 <p>enable:</p>
@@ -141,8 +137,8 @@ individually. You may following these in
 <p>Traffic Server will join into the Cluster in about 10 seconds, you man run
 <code>traffic_line -r proxy.process.cluster.nodes</code> to check the hosts in cluster
 or checkout the cluster.config in config dir.</p>
-<p>after the success join of the cluster, all changes of global config on any
-node, will take effect on this node now.</p>
+<p>After a successful join of the cluster, all changes of global configurations on any
+node, will take effect on <strong>all</strong> node now.</p>
 <h3 id="DeletingNodesFromCluster">Deleting Nodes from a Cluster</h3>
 <p>To delete a node from the Traffic Server cluster, just roll back
 <code>proxy.config.cluster.type</code> to the default value 3 and reload.</p>

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html Sun May 15 01:09:23 2011
@@ -135,7 +135,7 @@ Server connections, you must do the foll
 </ul>
 </li>
 </ul>
-<h5 id="to_configure_ssl_termination_for_clienttraffic_server_connections___configuresslterminationforclienttsconnections">To configure SSL termination for client/Traffic Server connections:  ##### {#configureSSLterminationforclient/TSconnections}</h5>
+<h5 id="configureSSLterminationforclientTSconnections">To configure SSL termination for client/Traffic Server connections:</h5>
 <ol>
 <li>Edit the following variables in the <code>SSL Termination</code> section of the <code>records.config</code> file: <ul>
 <li><a href="../configuration-files/records.config#proxy.config.ssl.enabled"><em><code>proxy.config.ssl.enabled</code></em></a></li>