Release-1.2.17-20020804

1 files changed, 3 insertions, 3 deletions

diff --git a/doc/starting.doc b/doc/starting.doc
index 8d4bc16..85341e3 100644
--- a/doc/starting.doc
+++ b/doc/starting.doc
@@ -32,7 +32,7 @@ engine. See section \ref doxysearch_usage for more detailed usage information.
 Optionally, the executable \c doxywizard is a GUI front-end for editing 
 the configuration files that are used by doxygen.
 
-\subsection step1 Step 1: Creating a configuration file
+\section step1 Step 1: Creating a configuration file
 
 Doxygen uses a configuration file to determine all of its settings.
 Each project should get its own configuration file. A project can consist
@@ -106,7 +106,7 @@ It can also include the sources directly into the documentation by setting
 \ref cfg_inline_sources "INLINE_SOURCES" to \c YES (this can be handy for 
 code reviews for instance).
 
-\subsection step2 Step 2: Running doxygen
+\section step2 Step 2: Running doxygen
 
 To generate the documentation you can now enter:
 \verbatim
@@ -159,7 +159,7 @@ environment variable). Note that there are some limitations to the
 capabilities of the man page format, so some information 
 (like class diagrams, cross references and formulas) will be lost.
 
-\subsection step3 Step 3: Documenting the sources
+\section step3 Step 3: Documenting the sources
 
 Although documenting the source is presented as step 3, in a new project 
 this should of course be step 1. Here I assume