don't always erase the background ourselves as this is incompatible with XP themed...

[wxWidgets.git] / docs / latex / wx / clientdat.tex

diff --git a/docs/latex/wx/clientdat.tex b/docs/latex/wx/clientdat.tex
index 74bdbeeefd9cf341b213ce1dc9e6eaa51acd369f..c4e37c629fddadd122dc6bf5b535eef7e4f2f661 100644 (file)
--- a/docs/latex/wx/clientdat.tex
+++ b/docs/latex/wx/clientdat.tex
@@ -4,11 +4,11 @@ All classes deriving from \helpref{wxEvtHandler}{wxevthandler}
 (such as all controls and \helpref{wxApp}{wxapp})
 can hold arbitrary data which is here referred to as "client data".
 This is useful e.g. for scripting languages which need to handle
-shadow objects for most of wxWindows' classes and which store
+shadow objects for most of wxWidgets' classes and which store
 a handle to such a shadow class as client data in that class.
 This data can either be of type void - in which case the data
 {\it container} does not take care of freeing the data again
-or it is of type wxClientData or its derivates. In that case the
+or it is of type wxClientData or its derivatives. In that case the
 container (e.g. a control) will free the memory itself later.
 Note that you {\it must not} assign both void data and data
 derived from the wxClientData class to a container.
@@ -52,13 +52,13 @@ Virtual destructor.
 This class is a mixin that provides storage and management of "client
 data." This data can either be of type void - in which case the data
 {\it container} does not take care of freeing the data again
-or it is of type wxClientData or its derivates. In that case the
+or it is of type wxClientData or its derivatives. In that case the
 container will free the memory itself later.
 Note that you {\it must not} assign both void data and data
 derived from the wxClientData class to a container.
 
 NOTE: This functionality is currently duplicated in wxEvtHandler in
-order to avoid having more than one vtable in that class heirachy.
+order to avoid having more than one vtable in that class hierarchy.
 
 \wxheading{See also}