X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/b82827dd43caa489eade15cc02edef7fb79e8c20..6d78998725b53eea209c0fa845b5a25fe5b512d2:/docs/latex/wx/critsect.tex

diff --git a/docs/latex/wx/critsect.tex b/docs/latex/wx/critsect.tex
index 2bc984a077..d9cd0c0df1 100644
--- 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 exactly for the same 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
@@ -18,10 +18,18 @@ possible instead of directly using wxCriticalSection for the same reasons
 
 None.
 
+\wxheading{Include files}
+
+<wx/thread.h>
+
+\wxheading{Library}
+
+\helpref{wxBase}{librarieslist}
+
 \wxheading{See also}
 
 \helpref{wxThread}{wxthread}, \helpref{wxCondition}{wxcondition}, 
-\helpref{wxMutexLocker}{wxmutexlocker}, \helpref{wxCriticalSection}{wxcriticalsection}
+\helpref{wxCriticalSectionLocker}{wxcriticalsectionlocker}
 
 \latexignore{\rtfignore{\wxheading{Members}}}
 
@@ -35,7 +43,7 @@ Default constructor initializes critical section object.
 
 \func{}{\destruct{wxCriticalSection}}{\void}
 
-Destructor frees the ressources.
+Destructor frees the resources.
 
 \membersection{wxCriticalSection::Enter}\label{wxcriticalsectionenter}
 
