diff --git a/spring-batch-docs/modules/ROOT/pages/scalability.adoc b/spring-batch-docs/modules/ROOT/pages/scalability.adoc
index a28bfdb9bb..040d6fee1f 100644
--- a/spring-batch-docs/modules/ROOT/pages/scalability.adoc
+++ b/spring-batch-docs/modules/ROOT/pages/scalability.adoc
@@ -344,9 +344,8 @@ public Step step1Manager(JobRepository jobRepository) {
 }
 ----
 +
-Similar to the multi-threaded step's `throttleLimit` method, the `gridSize`
-method prevents the task executor from being saturated with requests from a single
-step.
+The `gridSize` method prevents the task executor from being saturated with requests from a
+single step.
 
 XML::
 +
@@ -362,17 +361,12 @@ configuration:
 </step>
 ----
 +
-Similar to the multi-threaded step's `throttle-limit` attribute, the `grid-size`
-attribute prevents the task executor from being saturated with requests from a single
-step.
+The `grid-size` attribute prevents the task executor from being saturated with requests
+from a single step.
 
 ====
 
 
-The unit test suite for
-https://github.com/spring-projects/spring-batch/tree/main/spring-batch-samples/src/main/resources/jobs[Spring
-Batch Samples] (see `partition*Job.xml` configuration) has a simple example that you can copy and extend.
-
 Spring Batch creates step executions for the partition called `step1:partition0` and so
 on. Many people prefer to call the manager step `step1:manager` for consistency. You can
 use an alias for the step (by specifying the `name` attribute instead of the `id`
@@ -554,6 +548,8 @@ The following example shows how to define late binding in XML:
 
 ====
 
+You can find a complete example in the https://github.com/spring-projects/spring-batch/tree/main/spring-batch-samples/src/main/java/org/springframework/batch/samples/partitioning[Partitioning Sample].
+
 [[remoteStep]]
 == Remote Step execution