minor

implementation.md

@@ -120,10 +120,9 @@ GWMonitorRequester is given a Monitor which is ChannelMonitorImpl
 Updates originate from the client side, entering as an argument when GWMonitorRequester::monitorEvent is called,
 and exiting to the server when passed as an argument of a call to ServerMonitorRequesterImpl::monitorEvent.
 
-When called, ServerMonitorRequesterImpl::monitorEvent enqueues itself for transmission.
+When an update is added to the monitor queue ServerMonitorRequesterImpl::monitorEvent is
+called, as notification that the queue is not empty, which enqueues itself for transmission.
 The associated TCP sender thread later calls ServerMonitorRequesterImpl::send(),
 which calls GWMonitor::poll() to de-queue an event, which it encodes to the senders bytebuffer.
 It then reschedules itself.
 
-
-ServerMonitorRequesterImpl::monitorEvent is a no-op???