From 1c8df0d5f500a75e0c9140b9f702a24eca7175da Mon Sep 17 00:00:00 2001
From: dsyer <dsyer@2e8e966d-6415-0410-94b9-dc4e65435d03>
Date: Tue, 22 Apr 2008 09:26:10 +0000
Subject: [PATCH] wrong description of scope of execution context

---
 docs/src/site/docbook/reference/core.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/src/site/docbook/reference/core.xml b/docs/src/site/docbook/reference/core.xml
index 920c6a937..e73fafaa7 100644
--- a/docs/src/site/docbook/reference/core.xml
+++ b/docs/src/site/docbook/reference/core.xml
@@ -694,7 +694,7 @@
       <para>An <classname>ExecutionContext</classname> represents a collection
       of key/value pairs that are persisted and controlled by the framework in
       order to allow developers a place to store persistent state that is
-      scoped to a <classname>JobInstance</classname>. For those familiar with
+      scoped to a <classname>StepExecution</classname>. For those familiar with
       Quartz, it is very similar to <classname>JobDataMap</classname>. The
       best usage example is restart. Using flat file input as an example,
       while processing individual lines, the framework periodically persists
@@ -856,4 +856,4 @@
     logic that is not natural to split into read-(transform)-write phases,
     such as invoking a system command or a stored procedure.</para>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>