X-Git-Url: http://git.silcnet.org/gitweb/?a=blobdiff_plain;f=lib%2Fsilcclient%2FREADME;h=a9c9d485bf64d21034f256db6f7d59e788607944;hb=3df964f52d094db8ea9e8981fee73ff2a59e365c;hp=fef8dd769fef487af0e3cf8177a973fb4b496d6c;hpb=087575e2f4248e52d8db5900f757b847e65d9d91;p=silc.git

diff --git a/lib/silcclient/README b/lib/silcclient/README
index fef8dd76..a9c9d485 100644
--- a/lib/silcclient/README
+++ b/lib/silcclient/README
@@ -61,8 +61,7 @@ Using FSM
    set the old SilcPacket to the packet thread's state context and move back
    to the packet processor with silc_fsm_next and silc_fsm_continue_sync
    (always synchronously, never async).  This design may change later,
-   but for now this is it.  This also means that SILC_FSM_CALL must not
-   be used in packet processors because it returns SILC_FSM_WAIT.
+   but for now this is it.
 
 
 When to use FSM semaphore signalling?