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

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

diff --git a/docs/doxygen/overviews/richtextctrl.h b/docs/doxygen/overviews/richtextctrl.h
index 14515089cbf3d4bd80f54e6a787be78fcf0edb68..6f3dd7ea4bb86e0fff307517e0754bbc61e9abed 100644 (file)
--- a/docs/doxygen/overviews/richtextctrl.h
+++ b/docs/doxygen/overviews/richtextctrl.h
@@ -6,7 +6,7 @@
 // Licence:     wxWindows license
 /////////////////////////////////////////////////////////////////////////////
 
-/*!
+/**
 
 @page overview_richtextctrl wxRichTextCtrl Overview
 
@@ -89,10 +89,7 @@ You might mitigate this by providing the choice between wxTextCtrl and
 wxRichTextCtrl, with fewer features in the former case.
 
 A good way to understand wxRichTextCtrl's capabilities is to compile and run
-the sample, @c samples/richtext, and browse the code. The following screenshot
-shows the sample in action:
-
-@image html richtextctrl.bmp
+the sample, @c samples/richtext, and browse the code.
 
 
 @section overview_richtextctrl_example Code Example