X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/98ba1eee5d1b107e66c9fd28963b95f46fdefe89..e18e78a7cc106a75e5228c51edd982436682633d:/docs/doxygen/overviews/dc.h

diff --git a/docs/doxygen/overviews/dc.h b/docs/doxygen/overviews/dc.h
index f7bd09cf41..8cc019ddb0 100644
--- a/docs/doxygen/overviews/dc.h
+++ b/docs/doxygen/overviews/dc.h
@@ -6,21 +6,21 @@
 // Licence:     wxWindows license
 /////////////////////////////////////////////////////////////////////////////
 
-/*!
+/**
 
- @page overview_dc Device context overview
+ @page overview_dc Device Contexts
 
  Classes: wxBufferedDC, wxBufferedPaintDC, wxDC, wxPostScriptDC,
-          wxMetafileDC, wxMemoryDC, wxPrinterDC, wxScreenDC, wxClientDC, 
+          wxMetafileDC, wxMemoryDC, wxPrinterDC, wxScreenDC, wxClientDC,
           wxPaintDC, wxWindowDC.
 
  A wxDC is a @e device context onto which graphics and text can be drawn.
- The device context is intended to represent a number of output devices in a 
+ The device context is intended to represent a number of output devices in a
  generic way, with the same API being used throughout.
 
  Some device contexts are created temporarily in order to draw on a window.
  This is @true of wxScreenDC, wxClientDC, wxPaintDC, and wxWindowDC.
- The following describes the differences between these device contexts and 
+ The following describes the differences between these device contexts and
  when you should use them.
 
  @li @b wxScreenDC. Use this to paint on the screen, as opposed to an individual window.