diff --git a/src/warden-client/doc/README.cesnet b/src/warden-client/doc/README.cesnet
index b72568cab688bb3c5e516c37c6847f677460be33..c32f38d02fb255c84560d9c7bbece6d27e82114b 100644
--- a/src/warden-client/doc/README.cesnet
+++ b/src/warden-client/doc/README.cesnet
@@ -45,7 +45,8 @@ B. Registration
     * For receiver client:
       - hostname of the machine, where client runs,
       - client type = receiver,
-      - type of requested events (for example 'portscan', see below)
+      - whether client should receive all events, or type of requested
+        events (for example 'portscan', see below) otherwise
       - receiving of sent events from my organization = yes/no (organizations
         are separated based on the top-level and second-level domain),
       - CIDR from which client will communicate with Warden server.
@@ -138,7 +139,6 @@ D. Types of events
    * test - clients can use these at will when debugging/testing, these
             messages will be processed and stored, but ignored later
    * other - the rest, uncategorizable yet
-   * _any_ - clients can use these for receiving of all types of messages
 
    In case of complex scenarios with structured info more events with
    particular parts of information can be created.