diff --git a/src/warden-client/doc/CHANGELOG b/src/warden-client/doc/CHANGELOG
index a2fdab2d402286a797e36718b017c2039be69a6b..ee2d0d2b7be1a2375e2fb4f3989a5102f3dc9d20 100644
--- a/src/warden-client/doc/CHANGELOG
+++ b/src/warden-client/doc/CHANGELOG
@@ -1,6 +1,9 @@
 2012-00-00 v.2.1 stable version
 -------------------------------
 - receiving of all types of messages now supported
+- added support for batch processing
+- maximum number of events received ($MAX_RCV_EVENTS_LIMIT) in one batch can 
+  be set in etc/warden-client.conf. Default is 6000.
 
 
 2012-07-27 v.2.0 stable version and bugfix release of warden-client-2.0.0-beta
diff --git a/src/warden-client/doc/README b/src/warden-client/doc/README
index 20002393a38c824da37dc8383597c3746814ce62..cba389a5101174c2fa69672e044e959967aff749 100644
--- a/src/warden-client/doc/README
+++ b/src/warden-client/doc/README
@@ -210,6 +210,17 @@ F. Configuration
                     e.g. '/etc/ssl/certs/tcs-ca-bundle.pem' 
 
 
+    Client receives events in batches. Maximum number of events received in one
+    batch can is set in MAX_RCV_EVENTS_LIMIT. Note that this option only
+    affects clients that receives events from the Warden server (e.g., uses
+    lib/WardenClientReceive.pm module).
+
+    MAX_RCV_EVENTS_LIMIT - maximum number of events in one batch    
+                         - default set to 6000, which generates app. 250 MB
+                           of memory consumption.
+                         - only affects "receiving" clients
+
+
 --------------------------------------------------------------------------------
 G. Registration