svn commit: r786719 - in /websites/staging/trafficserver/trunk/content/docs/trunk/sdk: actions-guide/order.txt mutex-guide/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Wed Mar  9 02:12:25 2011
New Revision: 786719

Log:
Staging update by buildbot

Added:
    websites/staging/trafficserver/trunk/content/docs/trunk/sdk/actions-guide/order.txt
Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/sdk/mutex-guide/index.en.html

Added: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/actions-guide/order.txt
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/actions-guide/order.txt (added)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/actions-guide/order.txt Wed Mar  9 02:12:25 2011
@@ -0,0 +1,2 @@
+index
+hosts-lookup-api

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/mutex-guide/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/mutex-guide/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/mutex-guide/index.en.html Wed Mar  9 02:12:25 2011
@@ -72,7 +72,7 @@ section is very small, do not use it. If
 a variable and/or use atomic operations. If <code>TSMutexLock</code> is used in any case 
 other than the one recommended above, then the result will be a serious performance 
 impact. </p>
-<p><code>**TSMutexLockTry**</code>, on the other hand, attempts to lock the mutex only if 
+<p><strong><code>TSMutexLockTry</code></strong>, on the other hand, attempts to lock the mutex only if 
 it is unlocked (i.e., not being used by another thread). It should be used 
 in all cases other than the above mentioned <code>TSMutexLock</code> case. If the <code>TSMutexLockTry</code> 
 attempt fails, then you can schedule a future attempt (which must be at least