always define wxUSE_RICHEDIT[2] -- this is better than never defining them (closes...

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

diff --git a/docs/doxygen/overviews/xrc.h b/docs/doxygen/overviews/xrc.h
index 56c8ad08c8e6b8d82b154f5ec573ffef6bcb719e..0ba7c0a3d1c49e6fc0596a8cc47b6dbad1c4c3ae 100644 (file)
--- a/docs/doxygen/overviews/xrc.h
+++ b/docs/doxygen/overviews/xrc.h
@@ -6,9 +6,9 @@
 // Licence:     wxWindows license
 /////////////////////////////////////////////////////////////////////////////
 
-/*!
+/**
 
-@page overview_xrc XML Based Resource System
+@page overview_xrc XML Based Resource System (XRC)
 
 Classes: wxXmlResource, wxXmlResourceHandler
 
@@ -466,7 +466,7 @@ initialized.
 
 A simple example will help understand how the scheme works. Suppose you have a
 XRC file defining a top level window @c TestWnd_Base, which subclasses wxFrame
-(any other class like @c wxDialog will do also), and has subwidgets wxTextCtrl A 
+(any other class like @c wxDialog will do also), and has subwidgets wxTextCtrl A
 and wxButton B.
 
 The XRC file and corresponding class definition in the header file will be
@@ -624,7 +624,7 @@ wxObject *MyControlXmlHandler::DoCreateResource()
     // do most of your work.
     // If e.g. the MyControl::Create function looks like:
     //
-    // bool MyControl::Create(wxWindow *parent, int id, 
+    // bool MyControl::Create(wxWindow *parent, int id,
     //                        const wxBitmap &first, const wxPoint &posFirst,
     //                        const wxBitmap &second, const wxPoint &posSecond,
     //                        const wxString &theTitle, const wxFont &titleFont,