From 8b9f5411b2ee7d57ca956d43faf2f797593d553d Mon Sep 17 00:00:00 2001
From: dsyer <dsyer@2e8e966d-6415-0410-94b9-dc4e65435d03>
Date: Sat, 24 May 2008 10:19:49 +0000
Subject: [PATCH] BATCH-304: rename BatchCommandLineLauncher in docs

---
 src/site/apt/getting-started.apt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/site/apt/getting-started.apt b/src/site/apt/getting-started.apt
index 79f42961b..69e0e8c98 100644
--- a/src/site/apt/getting-started.apt
+++ b/src/site/apt/getting-started.apt
@@ -29,7 +29,7 @@ Spring Batch Getting Started
 
   You can get a pretty good idea about how to set up a job by examining the unit tests in the <<<org.springframework.batch.sample>>> package (in <<<src/main/java>>>) and the configuration in <<<src/main/resources/jobs>>>.
 
-  To launch a job from the command line instead of a unit test use the <<<BatchCommandLineLauncher.main()>>> method (see Javadocs included in that class).
+  To launch a job from the command line instead of a unit test use the <<<CommandLineJobRunner.main()>>> method (see Javadocs included in that class).
 
 ** With Maven on the Command Line