- Removed EVENT_BUFFER_OVERFLOW event type.

CHANGES.txt

@@ -97,13 +97,15 @@ Next Release
     listener rejected the event), the rebuffered event is now inserted
     in the head of the listener event queue.  This doesn't guarantee
     event emission in natural ordering, because if a listener rejects
-    an event or dies while its processing an event, it can take an
+    an event or dies while it's processing an event, it can take an
     arbitrary amount of time for the event to be rebuffered, and other
-    events may be processed in the meantime.  But if listeners never
-    rejects an event or doesn't die while processing an event, this
+    events may be processed in the meantime.  But if pool listeners
+    never reject an event or don't die while processing an event, this
     guarantees that events will be emitted in the order that they were
     received because if all listeners are busy, the rebuffered event
-    will be treid again "first" on the next go-around.
+    will be tried again "first" on the next go-around.
+
+  - Removed EVENT_BUFFER_OVERFLOW event type.
 
 3.0a2
 

README.txt

@@ -1031,17 +1031,6 @@ Supervisor Events (New in 3.0)
       SUPERVISOR_STATE_CHANGE_STOPPING -- indicates that supervisor is
       stopping or restarting.
 
-    EVENT_BUFFER_OVERFLOW -- an event type raised when a listener
-    pool's event buffer is overflowed (as can happen when an event
-    listener pool cannot keep up with all of the events sent to it).
-    When the pool's event buffer is overflowed, the oldest event in
-    the buffer is thrown out.
-
-    The serialization of an EVENT_BUFFER_OVERFLOW body
-    is::
-
-      groupname:<name> eventtype:<type of discarded event>
-
 Event Listeners (New in 3.0)
 
   Supervisor event listeners are subprocesses which are treated almost