diff --git a/src/site/docbook/reference/step.xml b/src/site/docbook/reference/step.xml
index 85258d0ab..6dd1cbc09 100644
--- a/src/site/docbook/reference/step.xml
+++ b/src/site/docbook/reference/step.xml
@@ -1541,7 +1541,7 @@ itemWriter.write(items);
Jobs
Part of the flow in a job can be externalized as a separate bean
- definition, and then re-used. There are three ways to do this, and the
+ definition, and then re-used. There are two ways to do this, and the
first is to simply declare the flow as a reference to one defined
elsewhere:
@@ -1562,29 +1562,7 @@ itemWriter.write(items);
also a good way to separate the integration testing of the individual
flows.
- The second form of an externalized flow is to use a
- FlowStep. A FlowStep is an
- implementation of the Step interface that
- delegates processing to a flow defined as above with a
- <flow/> element in XML. There is also support
- for creating a FlowStep in XML directly:
-
- <job id="job">
- <step id="job1.flow1" flow="flow1" next="step3"/>
- <step id="step3" parent="s3"/>
-</job>
-
-<flow id="flow1">
- <step id="step1" parent="s1" next="step2"/>
- <step id="step2" parent="s2"/>
-</flow>The logic of execution of this job is the same
- as the previous example, but the data stored in the job repository is
- different: the Step "job1.flow1" gets its own
- entry in the repository. This can be useful for monitoring and reporting
- purposes, and moreover it can be used to give more structure to a partitioned step.
-
- The third form of an externalized flow is to use a
+ The other form of an externalized flow is to use a
JobStep. A JobStep is
similar to a FlowStep, but actually creates and
launches a separate job execution for the steps in the flow specified.