Updating MSW file list.

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

diff --git a/docs/latex/wx/tguide.tex b/docs/latex/wx/tguide.tex
index 66f12ccc00f82150211528b465f26811b99122cd..c78f52a3454e34c2dc4c02a70371e4b6e9064009 100644 (file)
--- a/docs/latex/wx/tguide.tex
+++ b/docs/latex/wx/tguide.tex
@@ -1,6 +1,6 @@
-\section{Writing a wxWindows application: a rough guide}\label{roughguide}
+\section{Writing a wxWidgets application: a rough guide}\label{roughguide}
 
-To set a wxWindows application going, you will need to derive a \helpref{wxApp}{wxapp} class and
+To set a wxWidgets application going, you will need to derive a \helpref{wxApp}{wxapp} class and
 override \helpref{wxApp::OnInit}{wxapponinit}.
 
 An application must have a top-level \helpref{wxFrame}{wxframe} or \helpref{wxDialog}{wxdialog} window.
@@ -42,7 +42,7 @@ need wxHelp and the \helpref{wxHelpController}{wxhelpcontroller} class to contro
 wxHelp.
 
 GUI applications aren't all graphical wizardry. List and hash table needs are
-catered for by \helpref{wxList}{wxlist}, \helpref{wxStringList}{wxstringlist} and \helpref{wxHashMap}{wxhashmap}.
+catered for by \helpref{wxList}{wxlist} and \helpref{wxHashMap}{wxhashmap}.
 You will undoubtedly need some platform-independent \helpref{file functions}{filefunctions},
 and you may find it handy to maintain and search a list of paths using \helpref{wxPathList}{wxpathlist}.
 There's a \helpref{miscellany}{miscellany} of operating system and other functions.