wxVector<T> is header-based, use @nolibrary

[wxWidgets.git] / docs / doxygen / overviews / roughguide.h

diff --git a/docs/doxygen/overviews/roughguide.h b/docs/doxygen/overviews/roughguide.h
index 5aa71e3f36204d5ac642a396e7f644b345862f65..7a65f19f8c29417aebd69420c12334c218789dac 100644 (file)
--- a/docs/doxygen/overviews/roughguide.h
+++ b/docs/doxygen/overviews/roughguide.h
@@ -1,14 +1,14 @@
 /////////////////////////////////////////////////////////////////////////////
-// Name:        roughguide
+// Name:        roughguide.h
 // Purpose:     topic overview
 // Author:      wxWidgets team
 // RCS-ID:      $Id$
 // Licence:     wxWindows license
 /////////////////////////////////////////////////////////////////////////////
 
-/*!
+/**
 
-@page overview_roughguide Writing a wxWidgets Application: A Rough Guide
+@page overview_roughguide A Quick Guide to Writing Applications
 
 To set a wxWidgets application going, you will need to derive a wxApp class and
 override wxApp::OnInit.
@@ -50,13 +50,13 @@ you need wxHelp and the wxHelpController class to control wxHelp.
 
 GUI applications aren't all graphical wizardry. List and hash table needs are
 catered for by wxList and wxHashMap. You will undoubtedly need some
-platform-independent @ref functions_file, and you may find it handy to
+platform-independent @ref page_func_cat_file, and you may find it handy to
 maintain and search a list of paths using wxPathList. There's many
-@ref functions_miscellany of operating system methods and other functions.
+@ref page_func_cat_misc of operating system methods and other functions.
 
-@seealso
+@see
 
-@li @ref page_categories
+@li @ref page_class_cat
 
 */