First step in background erase optimization

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

diff --git a/docs/latex/wx/clientdat.tex b/docs/latex/wx/clientdat.tex
index 74bdbeeefd9cf341b213ce1dc9e6eaa51acd369f..f4aa0673e59372da21677a9b059bde57da1b73d2 100644 (file)
--- a/docs/latex/wx/clientdat.tex
+++ b/docs/latex/wx/clientdat.tex
@@ -4,7 +4,7 @@ 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
@@ -58,7 +58,7 @@ 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}