You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by bu...@apache.org on 2011/03/07 23:35:25 UTC
svn commit: r786646 -
/websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html
Author: buildbot
Date: Mon Mar 7 22:35:25 2011
New Revision: 786646
Log:
Staging update by buildbot
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html Mon Mar 7 22:35:25 2011
@@ -149,7 +149,7 @@ DNS resolver natively by directly issuin
than relying on slower, conventional resolver libraries. Since many DNS
queries can be issued in parallel and a fast DNS cache maintains
popular bindings in memory, DNS traffic is reduced.</p>
-<h3 id="traffic_server_processes_">Traffic Server Processes ###</h3>
+<h3 id="traffic-server-processes">Traffic Server Processes</h3>
<p>Traffic Server contains three processes that work together to serve
Traffic Server requests and manage/control/monitor the health of the
Traffic Server system. The three processes are described below:</p>