[Spread-cvs] commit: r306 - trunk/docs

[jschultz at spread.org]

Author: jschultz
Date: 2006-02-20 20:12:20 -0500 (Mon, 20 Feb 2006)
New Revision: 306

Modified:
   trunk/docs/MultithreadedClients.txt
Log:
Fixed some broken english to say what I think you meant to say.



Modified: trunk/docs/MultithreadedClients.txt
===================================================================
--- trunk/docs/MultithreadedClients.txt	2006-02-20 21:44:44 UTC (rev 305)
+++ trunk/docs/MultithreadedClients.txt	2006-02-21 01:12:20 UTC (rev 306)
@@ -3,7 +3,7 @@
 
 The Spread system supports both single-threaded client applications and multi-threaded client applications. As much as possible it tries to provide both types with high-efficiency interfaces and API's. However, writing multi-threaded applications entails some unavoidable increase in complexity, both at the API level and with performance considerations and so this document attempts to explain how best to utilize Spread from multi-threaded applications.
 
-Spread exports several different APIs for client applications. The core Spread API provides extended virtual synchrony semantics and is defined in the sp.h header and consists of functions beginning with the SP_ prefix. The Flush Spread API provides Virtual Synchrony semantics and is defined in the fl.h header and consists of functions beginning with the FL_ prefix. Both APIs can be used by multithreaded applications and are written to be 'thread-safe' (taking not of some specific semantic limitations explained below). 
+Spread exports several different APIs for client applications. The core Spread API provides extended virtual synchrony semantics and is defined in the sp.h header and consists of functions beginning with the SP_ prefix. The Flush Spread API provides Virtual Synchrony semantics and is defined in the fl.h header and consists of functions beginning with the FL_ prefix. Both APIs can be used by multithreaded applications and are written to be 'thread-safe' (not taking into account some of the specific semantic limitations explained below). 
 
 Linking and Libraries: