Update _posts/2026-01-08-measuring-debezium-server-performance-mysql-streaming.adoc

Co-authored-by: roldanbob <23705736+roldanbob@users.noreply.github.com>
Signed-off-by: Alvar Viana Gomez <alvigo92@gmail.com>

Author: AlvarVG

_posts/2026-01-08-measuring-debezium-server-performance-mysql-streaming.adoc

@@ -232,7 +232,7 @@ The next chart highlights that the maximum number of operations per second is pr
 
 But, *what is Debezium Server's observed upper bound in number of operations per second?* 
 
-In this comparison we can see the relationship between MySQL and Debezium Server throughput. The initial peak observed at the start of the execution is the desired value we are targeting for this execution.
+In this next chart we compare the relationship between MySQL and Debezium Server throughput. The initial peak observed at the start of the execution matches the value that we are targeting for this execution.
 MySQL fails to keep pace at such high values (1500 operations per second in 1 table). On the Debezium side, the throughput closely mirrors MySQL activity. 
 In the lower panel, you can see that Debezium's internal queue maintains a high and stable capacity throughout the execution, with no indication of saturation or backlog accumulation.
 Overall, the chart confirms that Debezium Server processes MySQL changes efficiently and in near real time, and that the throughput behavior is driven by the database write pattern rather than by downstream processing constraints.