Make event overview doc more clear about instances of wxEvtHandler

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@49224 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

diff --git a/docs/latex/wx/tevent.tex b/docs/latex/wx/tevent.tex
index 282cde947f9b79ab8bcf8cff5cf2641471db55d8..064a8b6bfdf3f94b7700ee0effdffa8691d9c7c9 100644 (file)
--- a/docs/latex/wx/tevent.tex
+++ b/docs/latex/wx/tevent.tex
@@ -268,9 +268,9 @@ defining the appropriate event table, and then call
 \rtfsp\helpref{wxWindow::SetEventHandler}{wxwindowseteventhandler} (or, preferably,
 \rtfsp\helpref{wxWindow::PushEventHandler}{wxwindowpusheventhandler}) to make this
 event handler the object that responds to events. This way, you can avoid
-a lot of class derivation, and use the same event handler class (but different
+a lot of class derivation, and use instnaces of the same event handler class (but different
 objects as the same event handler object shouldn't be used more than once) to
-handle events from instances of different classes. If you ever have to call a window's event handler
+handle events from instances of different widget classes. If you ever have to call a window's event handler
 manually, use the GetEventHandler function to retrieve the window's event handler and use that
 to call the member function. By default, GetEventHandler returns a pointer to the window itself
 unless an application has redirected event handling using SetEventHandler or PushEventHandler.