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

[wxWidgets.git] / docs / doxygen / overviews / debugging.h

diff --git a/docs/doxygen/overviews/debugging.h b/docs/doxygen/overviews/debugging.h
index 0eea7c5698bcf8bb5fac02f856a626c9d4953501..1bb7d01f18c8a99ea277d4cbe2feb2e2aebdcf23 100644 (file)
--- a/docs/doxygen/overviews/debugging.h
+++ b/docs/doxygen/overviews/debugging.h
@@ -11,7 +11,7 @@
 @page overview_debugging Debugging
 
 Classes, functions and macros: wxDebugContext, wxObject, wxLog,
-                                @ref group_funcmacro_log, @ref group_funcmacro_debugging
+                                @ref group_funcmacro_log, @ref group_funcmacro_debug
 
 Various classes, functions and macros are provided in wxWidgets to help you debug
 your application. Most of these are only available if you compile both wxWidgets,
@@ -73,7 +73,7 @@ compilers allow this definition to work properly, but most do.
 
 @section overview_debugging_dbgmacros Debug macros
 
-You should also use @ref group_funcmacro_debugging as part of a 'defensive programming'
+You should also use @ref group_funcmacro_debug as part of a 'defensive programming'
 strategy, scattering wxASSERTs liberally to test for problems in your code as early as
 possible.
 Forward thinking will save a surprising amount of time in the long run.