X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/247aba106508dfd3c8beeff07817b0f2d6525c69..bf7945cef10c0844a32e95695c544d829da9293a:/docs/latex/wx/tcontain.tex?ds=sidebyside

diff --git a/docs/latex/wx/tcontain.tex b/docs/latex/wx/tcontain.tex
index 8f8cc6d47d..c2e7364f36 100644
--- a/docs/latex/wx/tcontain.tex
+++ b/docs/latex/wx/tcontain.tex
@@ -2,11 +2,11 @@
 
 Classes: \helpref{wxList}{wxlist}, \helpref{wxArray}{wxarray}
 
-wxWindows uses itself several container classes including (double) linked lists
+wxWindows uses itself several container classes including doubly-linked lists
 and dynamic arrays (i.e. arrays which expand automatically when they become
 full). For both historical and portability reasons wxWindows does not
 use STL which provides the standard implementation of many container classes in
-C++: first of all, wxWindows had existed well before STL was written and
+C++. First of all, wxWindows has existed since well before STL was written, and
 secondly we don't believe that today compilers can deal really well with all of
 STL classes (this is especially true for some less common platforms). Of
 course, the compilers are evolving quite rapidly and hopefully their progress
@@ -18,24 +18,24 @@ ones, but they are quite useful and may be compiled with absolutely any C++
 compiler. They're used internally by wxWindows, but may, of course, be used in
 your programs as well if you wish.
 
-The list classes in wxWindows are double-linked lists which may either own the
+The list classes in wxWindows are doubly-linked lists which may either own the
 objects they contain (meaning that the list deletes the object when it is
 removed from the list or the list itself is destroyed) or just store the
 pointers depending on whether you called or not 
 \helpref{wxList::DeleteContents}{wxlistdeletecontents} method.
 
-Dynamic arrays resemble to C arrays but with two important differences: they
+Dynamic arrays resemble C arrays but with two important differences: they
 provide run-time range checking in debug builds and they expand automatically
 the allocated memory when there is no more space for new items. They come in
 two sorts: the "plain" arrays which store either built-in types such as "char",
 "int" or "bool" or the pointers to arbitrary objects, or "object arrays" which
 own the object pointers to which they store.
 
-For the same portability reasons, container classes implementation in wxWindows
+For the same portability reasons, the container classes implementation in wxWindows
 does not use templates, but is rather based on C preprocessor i.e. is done with
 the macros: {\it WX\_DECLARE\_LIST} and {\it WX\_DEFINE\_LIST} for the linked
-lists and {\it WX\_DECLARE\_ARRAY}, {\it WX\_DECLARE\_OBJARRAY} and {\it
-WX\_DEFINE\_OBJARRAY} for the dynamic arrays. The "DECLARE" macro declares a
+lists and {\it WX\_DECLARE\_ARRAY}, {\it WX\_DECLARE\_OBJARRAY} and {\it WX\_DEFINE\_OBJARRAY} for
+the dynamic arrays. The "DECLARE" macro declares a
 new container class containing the elements of given type and is needed for all
 three types of container classes: lists, arrays and objarrays. The "DEFINE"
 classes must be inserted in your program in a place where the {\bf full
@@ -44,7 +44,7 @@ declaration), otherwise destructors of the container elements will not be
 called! As array classes never delete the items they contain anyhow, there is
 no WX\_DEFINE\_ARRAY macro for them.
 
-Examples of usage of these macros may be found in \helpref{wxList}{wxlist} and
+Examples of usage of these macros may be found in \helpref{wxList}{wxlist} and 
 \helpref{wxArray}{wxarray} documentation.
 
 Finally, wxWindows predefines several commonly used container classes. wxList