diff --git a/BLOGPOST.md b/BLOGPOST.md
index b286c5ea..0d5d131f 100644
--- a/BLOGPOST.md
+++ b/BLOGPOST.md
@@ -76,10 +76,10 @@ Debezium extracts/consumes database events in real time and this could cause too
 which is not optimal for batch processing especially when near realtime data feed is sufficient.
 To avoid this problem it's possible to use following configuration and increase batch size per commit
 
-**MaxBatchSizeWait**: This setting adds delay based on debezium metrics, 
-it periodically monitors streaming queue size, and it starts processing events when it reaches `debezium.source.max.batch.size` value 
+**MaxBatchSizeWait**: uses debezium metrics to optimize batch size, it periodically reads streaming queue current size and waits until it reaches to `max.batch.size`
+maximum wait and check intervals are controlled by `debezium.sink.batch.batch-size-wait.max-wait-ms`, `debezium.sink.batch.batch-size-wait.wait-interval-ms` properties
 during the wait debezium events are collected in memory (in debezium streaming queue) and this way each commit receives more and consistent batch size
-this setting should be configured together with `debezium.source.max.queue.size` and `debezium.source.max.batch.size` debezium properties
+Note: this setting should be configured together with `debezium.source.max.queue.size` and `debezium.source.max.batch.size` debezium properties
 
 example setting:
 ```properties