1. improved wxKill() implementation for Win32

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

diff --git a/docs/latex/wx/htmlcell.tex b/docs/latex/wx/htmlcell.tex
index b7288009104dc99a0cc8b9495cadb1ab7aaa46da..15a8508bcf47a5ebf9091d6581a695e53232074f 100644 (file)
--- a/docs/latex/wx/htmlcell.tex
+++ b/docs/latex/wx/htmlcell.tex
@@ -1,4 +1,4 @@
-\subsection{Cells and Containers}\label{cells}
+\section{Cells and Containers}\label{cells}
 
 This article describes mechanism used by 
 \helpref{wxHtmlWinParser}{wxhtmlwinparser} and 
@@ -25,12 +25,12 @@ See \helpref{wxHtmlContainerCell}{wxhtmlcontainercell},
 % Bitmap is corrupt!
 This image shows you cells and containers:
 
-\image{}{contbox.bmp}
+\helponly{\image{}{contbox.bmp}}
 \end{comment}
 \wxheading{Using Containers in Tag Handler}
 
 \helpref{wxHtmlWinParser}{wxhtmlwinparser} provides a user-friendly way
-of managing containers. It's based on the idea of opening and closing containers.
+of managing containers. It is based on the idea of opening and closing containers.
 
 Use \helpref{OpenContainer}{wxhtmlwinparseropencontainer} to open new
 a container {\it within an already opened container}. This new container is a 
@@ -45,9 +45,9 @@ it returns "control" to the parent container.
 % Bitmap corrupt!
 See explanation:
 
-\image{}{cont.bmp}
+\helponly{\image{}{cont.bmp}}
 \end{comment}
-It's clear there must be same number of calls to 
+It is clear there must be same number of calls to 
 OpenContainer as to CloseContainer...
 
 \wxheading{Example}
@@ -70,7 +70,7 @@ m_WParser -> OpenContainer();
 % Bitmap corrupt!
 and here is image of the situation:
 
-\image{}{hello.bmp}
+\helponly{\image{}{hello.bmp}}
 \end{comment}
 
 You can see that there was opened container before running the code. We closed