--- libev/ev.pod 2008/02/01 13:53:56 1.128 +++ libev/ev.pod 2008/02/06 18:34:24 1.130 @@ -2080,7 +2080,8 @@ need elaborate support such as pthreads. That means that if you want to queue data, you have to provide your own -queue. And here is how you would implement locking: +queue. But at least I can tell you would implement locking around your +queue: =over 4 @@ -2127,7 +2128,7 @@ The strategy for threads is different, as you cannot (easily) block threads but you can easily preempt them, so to queue safely you need to -emply a traditional mutex lock, such as in this pthread example: +employ a traditional mutex lock, such as in this pthread example: static ev_async mysig; static pthread_mutex_t mymutex = PTHREAD_MUTEX_INITIALIZER; @@ -2944,7 +2945,7 @@ Priorities are implemented by allocating some space for each priority. When doing priority-based operations, libev usually has to linearly search all the priorities, but starting/stopping and activating -watchers becomes O(1) w.r.t. prioritiy handling. +watchers becomes O(1) w.r.t. priority handling. =item Sending an ev_async: O(1)