extracted the part of ProcessEvent() which is repeated multiple times during the...

[wxWidgets.git] / docs / doxygen / groups / funcmacro_thread.h

diff --git a/docs/doxygen/groups/funcmacro_thread.h b/docs/doxygen/groups/funcmacro_thread.h
index 1bcd6a900206e8cb4692ca81bb9e0e32241e0dc6..4fdc5dd02af4956c3e14a459c10344c1ea4b5a4b 100644 (file)
--- a/docs/doxygen/groups/funcmacro_thread.h
+++ b/docs/doxygen/groups/funcmacro_thread.h
@@ -11,17 +11,15 @@
 @defgroup group_funcmacro_thread Threads
 @ingroup group_funcmacro
 
-The functions and macros here mainly exist to make it writing the code which
-may be compiled in multi thread build (wxUSE_THREADS = 1) as well as in single
-thread configuration (wxUSE_THREADS = 0).
+The functions and macros here mainly exist to make it possible to write code
+which may be compiled in multi thread build (wxUSE_THREADS = 1) as well as in
+single thread configuration (wxUSE_THREADS = 0).
 
 For example, a static variable must be protected against simultaneous access by
 multiple threads in the former configuration but in the latter the extra
 overhead of using the critical section is not needed. To solve this problem,
-the wxCRITICAL_SECTION macro may be used to create and use the critical section
-only when needed.
-
-@header{wx/thread.h}
+the wxCRITICAL_SECTION() macro may be used to create and use the critical
+section only when needed.
 
 @sa wxThread, wxMutex, @ref overview_thread