remove incorrect comment in example

src/tests/01-ping-pong.ts

@@ -79,17 +79,7 @@ const server =
         SideEffect(logServerStats),
         SideEffect(sendResponse),
         Context<Cs>((ctx)=>({...ctx, responsesSent: ctx.responsesSent+1})),
-        Goto('awaiting-request') // for some reason, at this point there's a "received-request" waiting in the eventQueue, which gets processed before the "exit" then "entry" that get appended to the queue due to this Goto, which makes the Interpreter come right back to this State
-        /*
-          Server gets timer-finished, which sends response to client. 
-
-          But client, at the time, is not transitioning, so it immediately begins 
-          processing that event. The problem is that one of the sideeffects involved 
-          in processing that event is to send another request to the server, 
-          which hasn't yet even queued `exit`-then-`entry` events for its next state!
-          
-          So we have to ensure they get queued first, before processing the client.
-        */
+        Goto('awaiting-request')
       ),
     ),
   );