svn commit: r1080008 - /trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext

[ig...@apache.org]

Author: igalic
Date: Wed Mar  9 21:22:11 2011
New Revision: 1080008

URL: http://svn.apache.org/viewvc?rev=1080008&view=rev
Log:
Fixing links

Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext?rev=1080008&r1=1080007&r2=1080008&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext Wed Mar  9 21:22:11 2011
@@ -78,7 +78,7 @@ satisfy future requests.
 Traffic Server provides explicit proxy caching, in which the user’s
 client software must be configured to send requests directly to Traffic
 Server. Explicit proxy caching is described in the
-[Explicit Proxy Caching](/docs/admin/explicit) section.
+[Explicit Proxy Caching](explicit-proxy-caching) section.
 
 
 ### Traffic Server as a Reverse Proxy ### {#reverse-proxy}
@@ -88,7 +88,7 @@ server to which the user is trying to co
 server’s advertised hostname resolves to Traffic Server, which acts as
 the real origin server). The reverse proxy feature is also called
 server acceleration. Reverse proxy is described in more detail in
-[Reverse Proxy and HTTP Redirects](/docs/admin/reverse).
+[Reverse Proxy and HTTP Redirects](reverse-proxy-http-redirects).
 
 
 ### Traffic Server in a Cache Hierarchy ### {#cache-hierachy}
@@ -102,7 +102,7 @@ to similar caching products.
 
 Traffic Server supports ICP (Internet Cache Protocol) peering.
 Hierarchical caching is described in more detail in
-[Hierarchical Caching](/docs/admin/hier).
+[Hierarchical Caching](hierachical-caching).
 
 
 ## Traffic Server Components ## {#ats-components}
@@ -130,7 +130,7 @@ If all of the cache disks fail, then Tra
 proxy-only mode. You can partition the cache to reserve a certain
 amount of disk space for storing data for specific protocols and origin
 servers. For more information about the cache, see
-[Configuring the Cache](/docs/admin/cache).
+[Configuring the Cache](configuring-cache).
 
 
 ### The RAM Cache ### {#ram-cache}
@@ -140,7 +140,7 @@ popular objects. This RAM cache serves t
 as possible and reduces load on disks, especially during temporary
 traffic peaks. You can configure the RAM cache size to suit your needs;
 for detailed information, refer to
-[Changing the Size of the RAM Cache](/docs/admin/cache#ChangingSizeRAMCache).
+[Changing the Size of the RAM Cache](configuring-cache#ChangingSizeRAMCache).
 
 
 ### The Host Database ### {#host-db}
@@ -247,9 +247,9 @@ and monitoring:
   they contain information specific to protocol or hosts.
 
 Traffic analysis options are described in more detail in
-[Monitoring Traffic](/docs/admin/monitor);
+[Monitoring Traffic](monitoring-traffic);
 Traffic Server logging options are described in
-[Working with Log Files](/docs/admin/log).
+[Working with Log Files](working-log-files).
 
 
 ## Traffic Server Security Options ## {#security}
@@ -274,5 +274,5 @@ following:
 * Control access via SSL (Secure Sockets Layer).
 
 Traffic Server security options are described in more detail in
-[Security Options](/docs/admin/secure).
+[Security Options](security-options).