Fixes in MUON documentation files

diff --git a/MUON/Doxyfile b/MUON/Doxyfile
index 706d6bf12d942468dfeb1d4658f69d3f025e94af..c0c1fc37c5fb32a69c052574922b13a325f5d5a2 100644 (file)
--- a/MUON/Doxyfile
+++ b/MUON/Doxyfile
@@ -23,7 +23,7 @@ PROJECT_NAME           = "AliRoot MUON"
 # This could be handy for archiving the generated documentation or 
 # if some version control system is used.
 
-PROJECT_NUMBER         = "Version CVS"
+PROJECT_NUMBER         = "Version SVN trunk"
 
 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
 # base path where the generated documentation will be put. 

diff --git a/MUON/Doxymain.h b/MUON/Doxymain.h
index 74c8dfeee73e11680a994dde309cac7ff884bf5c..775f5b4a239dc3614d67edaf209661de44a3e49a 100644 (file)
--- a/MUON/Doxymain.h
+++ b/MUON/Doxymain.h
@@ -19,6 +19,7 @@ Currently there are the documentation pages on
 - \ref README_sim
 - \ref README_rec
 - \ref README_base
+- \ref README_mchview 
 - \ref README_evaluation 
 - \ref README_fast
 - \ref README_raw 
@@ -27,7 +28,6 @@ Currently there are the documentation pages on
 - \ref README_geometry 
 - \ref README_trigger 
 - \ref README_shuttle 
-- \ref README_mchview 
 
 On this page you will find the first how to run the 
 simulation, reconstructin and evaluation chain. More details