X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/adcb6f88ee32eb508d64e86c22ad193fec8b95cf..ccef4c3ad16fe5bf4365569c431f1208d79eb0ef:/docs/doxygen/overviews/runtimeclass.h?ds=sidebyside

diff --git a/docs/doxygen/overviews/runtimeclass.h b/docs/doxygen/overviews/runtimeclass.h
index dd16fe7db9..9050ac9b6e 100644
--- a/docs/doxygen/overviews/runtimeclass.h
+++ b/docs/doxygen/overviews/runtimeclass.h
@@ -2,28 +2,14 @@
 // Name:        runtimeclass.h
 // Purpose:     topic overview
 // Author:      wxWidgets team
-// RCS-ID:      $Id$
-// Licence:     wxWindows license
+// Licence:     wxWindows licence
 /////////////////////////////////////////////////////////////////////////////
 
 /**
 
 @page overview_rtti Runtime Type Information (RTTI)
 
-@li @ref overview_rtti_intro
-@li @ref overview_rtti_classinfo
-@li @ref overview_rtti_example
-
-@see
-
-@li wxObject
-@li wxClassInfo
-
-
-<hr>
-
-
-@section overview_rtti_intro Introduction
+@tableofcontents
 
 One of the failings of C++ used to be that no runtime information was provided
 about a class and its position in the inheritance hierarchy. Another, which
@@ -35,7 +21,7 @@ Most C++ GUI frameworks overcome these limitations by means of a set of macros
 and functions and wxWidgets is no exception. As it originated before the
 addition of RTTI to the C++ standard and as support for it is still missing
 from some (albeit old) compilers, wxWidgets doesn't (yet) use it, but provides
-it's own macro-based RTTI system.
+its own macro-based RTTI system.
 
 In the future, the standard C++ RTTI will be used though and you're encouraged
 to use whenever possible the wxDynamicCast macro which, for the implementations
@@ -72,6 +58,8 @@ The function wxCreateDynamicObject can be used to construct a new object of a
 given type, by supplying a string name. If you have a pointer to the
 wxClassInfo object instead, then you can simply call wxClassInfo::CreateObject.
 
+@see wxObject
+
 
 @section overview_rtti_classinfo wxClassInfo
 
@@ -79,7 +67,7 @@ This class stores meta-information about classes. An application may use macros
 such as DECLARE_DYNAMIC_CLASS and IMPLEMENT_DYNAMIC_CLASS to record runtime
 information about a class, including:
 
-@li It's position in the inheritance hierarchy.
+@li Its position in the inheritance hierarchy.
 @li The base class name(s) (up to two base classes are permitted).
 @li A string representation of the class name.
 @li A function that can be called to construct an instance of this class.
@@ -93,11 +81,6 @@ You can get the wxClassInfo for a class by using the CLASSINFO macro, e.g.
 CLASSINFO(wxFrame). You can get the wxClassInfo for an object using
 wxObject::GetClassInfo.
 
-@see
-
-@li wxObject
-@li wxCreateDynamicObject
-
 
 @section overview_rtti_example Example
 
@@ -128,4 +111,3 @@ wxFrame::wxFrame()
 @endcode
 
 */
-