wxFont can now raelly use the native fonts

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

diff --git a/docs/latex/wx/tconfig.tex b/docs/latex/wx/tconfig.tex
index 42c046ca35cf622bccf7ea0c9668589fb3a3ac17..cff03372180c698adad3506c8df59a9f37e168d4 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}
 
@@ -12,17 +12,18 @@ The config classes provide a way to store some application configuration
 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{itemize}
-\item{1.} Typed, i.e. strings or numbers for the moment. You can not store
+
+\begin{enumerate}\itemsep=0pt
+\item Typed, i.e. strings or numbers for the moment. You can not store
 binary data, for example.
-\item{2.} Small. For instance, it is not recommended to use the Windows
+\item Small. For instance, it is not recommended to use the Windows
 registry for amounts of data more than a couple of kilobytes.
-\item{3.} Not performance critical, neither from speed nor from a memory
+\item Not performance critical, neither from speed nor from a memory
 consumption point of view.
-\end{itemize}
+\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
@@ -31,7 +32,7 @@ particular, these classes were designed to be as easy to use as possible.
 From another point of view, they provide an interface which hides the
 differences between the Windows registry and the standard Unix text format
 configuration files. Other (future) implementations of wxConfigBase might also
-understand GTK ressource files or their analogues on the KDE side.
+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