From 845d9fac0dfce1d4297bf1f531c690114756ca2c Mon Sep 17 00:00:00 2001
From: Diomidis Spinellis <dds@aueb.gr>
Date: Wed, 26 Jul 2006 14:34:36 +0000
Subject: [PATCH] Fix name into UmlGraphDoc (Stefan Birkner)

---
 doc/cd-umldoc.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/cd-umldoc.xml b/doc/cd-umldoc.xml
index af9143e..39ffccc 100644
--- a/doc/cd-umldoc.xml
+++ b/doc/cd-umldoc.xml
@@ -1,11 +1,11 @@
 <?xml version="1.0" ?>
 <!-- $Id$ -->
 <notes>
-UMLGraphDoc is a standard doclet wrapper that combines
+UmlGraphDoc is a standard doclet wrapper that combines
 the standard doclet output (javadoc documentation) along with auto-generated
 class diagrams for both packages and classes.
 
-The UMLGraphDoc process is driven by all the parameters that can be specified for
+The UmlGraphDoc process is driven by all the parameters that can be specified for
 UMLGraph and the standard doclet; each will be passed to the appropriate
 doclet.
 
@@ -19,13 +19,13 @@ The actual content of the diagrams depends on the kind of relations declared on
 class files (with the UMLGraph javadoc annotations) and/or on the kind of automated
 inference that UMLGraph is allowed to use.
 
-UMLGraph javadocs are now generated with UMLGraphDoc with the following ant target:
+UMLGraph javadocs are now generated with UmlGraphDoc with the following ant target:
 
 <fmtcode ext="xml">
 <target name="javadocs" depends="compile">
 	<javadoc sourcepath="${src}" packagenames="gr.spinellis.umlgraph.doclet.*" destdir="${javadoc}" 
 	         private="true">
-		<doclet name="gr.spinellis.umlgraph.doclet.UMLGraphDoc" path="${lib}/UMLGraph.jar">
+		<doclet name="gr.spinellis.umlgraph.doclet.UmlGraphDoc" path="${lib}/UMLGraph.jar">
 			<param name="-inferrel"/>
 			<param name="-inferdep"/>
 			<param name="-hide" value="java.*"/>
@@ -41,7 +41,7 @@ UMLGraph javadocs are now generated with UMLGraphDoc with the following ant targ
 </target>
 </fmtcode>
 
-When generating documentation with UMLGraphDoc you will encounter
+When generating documentation with UmlGraphDoc you will encounter
 at some point the "fur ball" effect: some central classes that
 have very complex context diagrams.
 To reduce this, you can avoid dependency inference