Always use wxFULL_REPAINT_ON_RESIZE for generic status bar.

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

diff --git a/docs/latex/wx/critsect.tex b/docs/latex/wx/critsect.tex
index 0851745cd818528e7cab78b85d899f900d62b672..83cf6fb8c7ce17a65cea791dfab975947b391854 100644 (file)
--- a/docs/latex/wx/critsect.tex
+++ b/docs/latex/wx/critsect.tex
@@ -1,7 +1,7 @@
 \section{\class{wxCriticalSection}}\label{wxcriticalsection}
 
-A critical section object is used for the same exactly purpose as 
-\helpref{mutexes}{wxMutex}. The only difference is that under Windows platform
+A critical section object is used for exactly the same purpose as 
+\helpref{mutexes}{wxmutex}. The only difference is that under Windows platform
 critical sections are only visible inside one process, while mutexes may be
 shared between processes, so using critical sections is slightly more
 efficient. The terminology is also slightly different: mutex may be locked (or
@@ -25,7 +25,7 @@ None.
 \wxheading{See also}
 
 \helpref{wxThread}{wxthread}, \helpref{wxCondition}{wxcondition}, 
-\helpref{wxMutexLocker}{wxmutexlocker}, \helpref{wxCriticalSection}{wxcriticalsection}
+\helpref{wxCriticalSectionLocker}{wxcriticalsectionlocker}
 
 \latexignore{\rtfignore{\wxheading{Members}}}
 
@@ -39,7 +39,7 @@ Default constructor initializes critical section object.
 
 \func{}{\destruct{wxCriticalSection}}{\void}
 
-Destructor frees the ressources.
+Destructor frees the resources.
 
 \membersection{wxCriticalSection::Enter}\label{wxcriticalsectionenter}