Resolve ambiguity between GetClientXXX() methods in wxOSX wxComboBox.

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

diff --git a/docs/doxygen/groups/funcmacro_atomic.h b/docs/doxygen/groups/funcmacro_atomic.h
index c7059dadf57d00abb4992b166b64147b4f2869b3..f3bb29371a5d3222adbb2f52e2335cf263fa698a 100644 (file)
--- a/docs/doxygen/groups/funcmacro_atomic.h
+++ b/docs/doxygen/groups/funcmacro_atomic.h
@@ -3,7 +3,7 @@
 // Purpose:     Atomic Operation function and macro group docs
 // Author:      wxWidgets team
 // RCS-ID:      $Id: funcmacro_gdi.h 52454 2008-03-12 19:08:48Z BP $
-// Licence:     wxWindows license
+// Licence:     wxWindows licence
 /////////////////////////////////////////////////////////////////////////////
 
 /**
@@ -14,17 +14,15 @@
 When using multi-threaded applications, it is often required to access or
 modify memory which is shared between threads. Atomic integer and pointer
 operations are an efficient way to handle this issue (another, less efficient,
-way is to use a mutex or critical section). A native implementation exists for
-Windows, Linux, Solaris and Mac OS X, for other OS, a wxCriticalSection is used
-to protect the data.
+way is to use a wxMutex or wxCriticalSection). A native implementation exists
+for Windows, Linux, Solaris and Mac OS X; for others, a wxCriticalSection is
+used to protect the data.
 
-One particular application is reference counting (used by so-called smart
-pointers).
+One particular application is reference counting (used by so-called
+@ref group_class_smartpointers "smart pointers").
 
 You should define your variable with the type wxAtomicInt in order to apply
 atomic operations to it.
 
-@header{wx/atomic.h}
-
 */