Added wxDataViewTreeCtrl

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

diff --git a/docs/latex/wx/tconfig.tex b/docs/latex/wx/tconfig.tex
index 6baf8c59a5894a0ad07ce27404e3d2922fdb6eb5..92475c75ebc1b6f98b3f5330d6911493a5024a2e 100644 (file)
--- a/docs/latex/wx/tconfig.tex
+++ b/docs/latex/wx/tconfig.tex
@@ -1,4 +1,4 @@
-\section{Config classes overview}\label{wxconfigoverview}
+\section{wxConfig classes overview}\label{wxconfigoverview}
 
 Classes: \helpref{wxConfig}{wxconfigbase}
 
@@ -13,7 +13,7 @@ information. They were especially designed for this usage and, although may
 probably be used for many other things as well, should be limited to it. It
 means that this information should be:
 
-\begin{enumerate}
+\begin{enumerate}\itemsep=0pt
 \item Typed, i.e. strings or numbers for the moment. You can not store
 binary data, for example.
 \item Small. For instance, it is not recommended to use the Windows
@@ -23,7 +23,7 @@ consumption point of view.
 \end{enumerate}
 
 On the other hand, the features provided make them very useful for storing all
-kinds of small to medium volumes of hierarchically-organized, heterogenous
+kinds of small to medium volumes of hierarchically-organized, heterogeneous
 data. In short, this is a place where you can conveniently stuff all your data
 (numbers and strings) organizing it in a tree where you use the
 filesystem-like paths to specify the location of a piece of data. In
@@ -35,9 +35,8 @@ configuration files. Other (future) implementations of wxConfigBase might also
 understand GTK resource files or their analogues on the KDE side.
 
 In any case, each implementation of wxConfigBase does its best to
-make the data look the same way everywhere. Due
-to the limitations of the underlying physical storage as in the case of
-wxIniConfig, it may not implement 100\% of the base class functionality.
+make the data look the same way everywhere. Due to limitations of the underlying 
+physical storage, it may not implement 100\% of the base class functionality.
 
 There are groups of entries and the entries themselves. Each entry contains either a string or a number
 (or a boolean value; support for other types of data such as dates or