More warning and error fixes (work in progress with Tinderbox).

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

diff --git a/docs/latex/wx/tthreads.tex b/docs/latex/wx/tthreads.tex
index c06ddbc3c480cbfc0a36c6d22f06257c53575c7a..29b0eb9e254ee03bdc0e2505e428afb54366b33b 100644 (file)
--- a/docs/latex/wx/tthreads.tex
+++ b/docs/latex/wx/tthreads.tex
@@ -38,14 +38,14 @@ more robust and will undoubtedly save you countless problems (example: under
 Win32 a thread can only access GDI objects such as pens, brushes, \&c created by
 itself and not by the other threads).
 
-For communication between secondar threads and the main thread, use may use 
+For communication between secondary threads and the main thread, you may use 
 \helpref{wxEvtHandler::AddPendingEvent}{wxevthandleraddpendingevent}
 or its short version \helpref{wxPostEvent}{wxpostevent}. These functions
 have thread safe implementation so that they can be used as they are for
-sending event from one thread to another. However there is no built in method
+sending events from one thread to another. However there is no built in method
 to send messages to the worker threads and you will need to use the available
 synchronization classes to implement the solution which suits your needs
-yourself. In particular, please notice that it is \emph{not} enough to derive
+yourself. In particular, please note that it is \emph{not} enough to derive
 your class from \helpref{wxThread}{wxthread} and 
 \helpref{wxEvtHandler}{wxevthandler} to send messages to it: in fact, this does
 \emph{not} work at all.