From 85bdb5c3b5450397a37d5b8acee8f450df6827a0 Mon Sep 17 00:00:00 2001
From: Akash Keshari <1994keshari@gmail.com>
Date: Tue, 22 Jul 2025 12:42:43 +0530
Subject: [PATCH] Manager is ItwermReader

Signed-off-by: Akash Keshari <1994keshari@gmail.com>
---
 spring-batch-docs/modules/ROOT/pages/scalability.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spring-batch-docs/modules/ROOT/pages/scalability.adoc b/spring-batch-docs/modules/ROOT/pages/scalability.adoc
index 48f711e6b2..9755525ec6 100644
--- a/spring-batch-docs/modules/ROOT/pages/scalability.adoc
+++ b/spring-batch-docs/modules/ROOT/pages/scalability.adoc
@@ -260,7 +260,7 @@ The manager component is a single process, and the workers are multiple remote p
 This pattern works best if the manager is not a bottleneck, so the processing must be more
 expensive than the reading of items (as is often the case in practice).
 
-The manager is an implementation of a Spring Batch `Step` with the `ItemWriter` replaced
+The manager is an implementation of a Spring Batch `Step` with the `ItemReader` replaced
 by a generic version that knows how to send chunks of items to the middleware as
 messages. The workers are standard listeners for whatever middleware is being used (for
 example, with JMS, they would be `MesssageListener` implementations), and their role is