Corrected URCU doc

diff --git a/cds/urcu/details/base.h b/cds/urcu/details/base.h
index b008581d78b496bfb8f9c639e1a97a089ebf3441..8aa281072d38ca38015d9ee0d030f21f5d7cf518 100644 (file)
--- a/cds/urcu/details/base.h
+++ b/cds/urcu/details/base.h
@@ -24,19 +24,17 @@ namespace cds {
         - [2011] M.Desnoyers, P.McKenney, A.Stern, M.Dagenias, J.Walpole "User-Level
           Implementations of Read-Copy Update"
 
-        <b>Informal intruduction to user-space %RCU</b>
+        <b>Informal introduction to user-space %RCU</b>
 
         [<i>From Desnoyer's papers</i>] %RCU is a synchronization mechanism that was added to the
         Linux kernel in October of 2002. %RCU achieves scalability improvements by allowing
         reads to occur concurrently with updates. In contrast to conventional locking
         primitives that ensure mutual exclusion among concurrent threads regardless of whether
         they be readers or updaters, or with reader-writer locks that allow concurrent reads
-        but not in the presence of updates, %RCU supports concurrency between a single updater
-        and multiple readers. %RCU ensures that reads are coherent by maintaining multiple
-        versions of objects and ensuring that they are not freed up until all pre-existing readside
+        but not in the presence of updates, %RCU supports concurrency between multiple updaters
+        and multiple readers. %RCU ensures that data are not freed up until all pre-existing
         critical sections complete. %RCU defines and uses efficient and scalable mechanisms
-        for publishing and reading new versions of an object, and also for deferring reclamation
-        of old versions. These mechanisms distribute the work among read and update
+        for deferring reclamation of old data. These mechanisms distribute the work among read and update
         paths in such a way as to make read paths extremely fast.
 
         %RCU readers execute within %RCU read-side critical sections. Each such critical section begins with