applied typos and spelling error fixes patch from Olly Betts

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15779 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/base/readme.txt

@@ -25,7 +25,7 @@ threads, sockets and much more. Some of the other utility classes allow you to
 parse the command line, limit the number of instances of your program
 executing simultaneously (portably!) and so on.
 
-1. Requirments and supported platforms
+1. Requirements and supported platforms
 --------------------------------------
 
  wxBase can be compiled and used under Win32, mostly any modern Unix system

docs/bugs.txt

@@ -49,7 +49,7 @@ DETAILS:
   some reason.
 
 - On SGI IRIX 6.4, XtDestroyWidget in ~wxWindow causes a crash in
-  some cicumstances. This is being looked into. Meanwhile, a
+  some circumstances. This is being looked into. Meanwhile, a
   possible workaround is to remove the final XtDestroyWidget line in ~wxWindow
   (window.cpp). This will mean that child windows will only get
   destroyed when frames and dialogs are destroyed, so dynamic subwindow
@@ -207,7 +207,7 @@ DETAILS: Around line 1234 or the common/docview.cpp file following code exists..
 if (!theTemplate)
     theTemplate=templates[FilterIndex] ;
 
-The problem is tat FilterIndex is one based and the templates array is zero based. The correct
+The problem is that FilterIndex is one based and the templates array is zero based. The correct
 thing might be to use FilterIndex-1 as the index. Else the following scenario will
 cause a crash.
 
@@ -222,13 +222,13 @@ I understand that it is very
 hard to figure out the template
 when the user does not select
 one of the known extensions but
-this simple fix might atleast
+this simple fix might at least
 avoid the crash....
 
 I started playing with wxMSW
 just this morning and have not
 yet figured out exactly how to
-submit a fix. I atleast wanted
+submit a fix. I at least wanted
 to report it. Besides what I do
 for the MSW might not be correct
 for the other platforms :-)
@@ -292,7 +292,7 @@ output to freeze when the limit was reached.
 FIXED+BY: Vasu Harish
 IDENTIFIED+BY: Vasu Harish
 PLATFORMS: wxMSW
-SHORT+DESCRIPTION: wxTextCtrl clogs output occassionally when the text size limit is reached
+SHORT+DESCRIPTION: wxTextCtrl clogs output occasionally when the text size limit is reached
 WORKAROUND: In the check for (len > limit) condition in wxTextCtrl::AdjustSpaceLimit()
 call, added the condition to check for the len==limit. 
 visitor_email_address: vasuh@bullant.net
@@ -339,7 +339,7 @@ is used.
 FIXED+BY: Alexey V. Exarevsky (patched into wxWin 12/1/2000 by JACS)
 IDENTIFIED+BY: Alexey V. Exarevsky
 PLATFORMS: wxMSW, compiled by VC++ 6.0
-SHORT+DESCRIPTION: Print/Print preveiw to default printer in NT
+SHORT+DESCRIPTION: Print/Print preview to default printer in NT
 Submit: Submit
 WORKAROUND: I have moved lines that free
 memory below the lines that
@@ -351,7 +351,7 @@ wxWINDOWS+VERSION: 2.1.11
 DATE+FIXED:
 DATE+IDENTIFIED: 14/01/2000
 DETAILS: I run my linux boxes headless and use a Windows box for an XServer... every sample I have tried so far
-hangs in a loop tring to get an acceptable font for something or other... here is the GDB trace
+hangs in a loop trying to get an acceptable font for something or other... here is the GDB trace
 #1102 0x40203d19 in wxMessageBox ()
 #1103 0x401aee31 in wxFontMapper::GetAltForEncoding ()
 #1104 0x40287c45 in wxLoadQueryNearestFont ()

docs/changes.txt

@@ -41,12 +41,12 @@ All (GUI):
   in the switch()es, you must rewrite them to use if()s instead
 
   You may also define WXWIN_COMPATIBILITY_EVENT_TYPES to get the old behaviour
-  but this is strongly discouraged, please consider changing your codei
+  but this is strongly discouraged, please consider changing your code
   instead!
 
 ! wxDialog does not derive from wxPanel any longer - if you were using it in
   your code, please update it. The quick fix for the most cases is to replace
-  the occurences of wxPanel with wxWindow.
+  the occurrences of wxPanel with wxWindow.
 
 ! if you handle (and don't skip) EVT_KEY_DOWN, the EVT_CHAR event is not
   generated at all, so you must call event.Skip() in your OnKeyDown() if
@@ -458,7 +458,7 @@ wxMSW:
 - fixed "missing" initial resize of wxMDIChildFrame
 - wxFrame restores focus better
 - Now ignore wxTHICK_FRAME in wxWindow constructor: only relevant to
-  frames anddialogs, interferes with other window styles otherwise
+  frames and dialogs, interferes with other window styles otherwise
   (sometimes you'd get a thick frame in a subwindow)
 - wxTextCtrl insertion point set to the beginning of the control by SetValue
 - Fix so wxMDIParentFrame is actually shown when Show(TRUE) is called.
@@ -541,7 +541,7 @@ all (GUI):
 
 - Added wxImage::Rotate.
 - new wxCalendarCtrl class for picking a date interactively
-- wxMenu(Bar)::Insert() and Remove() functions for dynamic menu menagament
+- wxMenu(Bar)::Insert() and Remove() functions for dynamic menu management
 - wxToolBar supports arbitrary controls (not only buttons) and can be
   dynamically changed (Delete/Insert functions)
 - vertical toolbars supported by MSW and GTK native wxToolBar classes
@@ -557,7 +557,7 @@ all (GUI):
 - wxScrolledWindow now has keyboard interface
 - wxTextEntryDialog may be used for entering passwords (supports wxTE_PASSWORD)
 - added wxEncodingConverter and improved wxFontMapper
-  for dealing with convertions between different encodings,
+  for dealing with conversions between different encodings,
   charsets support in wxLocale and wxHTML
 - wxDragImage class added
 - samples/help improved to show standard and advanced HTML help
@@ -599,11 +599,11 @@ wxHTML:
   including faster search, bookmarks, printing, setup dialog
   and cross-platform binary compatible .cached files for faster
   loading of large helpbooks, case insensitive search
-  splitted into 3 parts: wxHtmlHelpData, Frame and Controller
+  split into 3 parts: wxHtmlHelpData, Frame and Controller
 - added support for charsets and <meta> tag
 - added support for font faces and justified paragraphs,
   taken some steps to prepare wxHTML for frames
-- added dynamic pushing/poping of wxHtmlParser tag handlers
+- added dynamic pushing/popping of wxHtmlParser tag handlers
 - improved HTML printing
 - added extensive table of HTML characters substitutions (&nbsp; etc.)
 - fixed wxHtmlWindow flickering, several minor bugfixes
@@ -866,7 +866,7 @@ wxMotif:
   global memory operators (usually OK) and #defining new to be
   WXDEBUG_NEW (sometimes it might not be OK).
 - Added time.cpp to makefile; set wxUSE_DATETIME to 1.
-- Added a parent-existance check to popup menu code to make it not crash.
+- Added a parent-existence check to popup menu code to make it not crash.
 - Added some optimization in wxWindow::SetSize to produce less flicker.
   It remains to be seen whether this produces any resize bugs.
 
@@ -922,7 +922,7 @@ wxMSW:
 - wxConfig API improved, documentation updated.
 - Printing classes name conventions cleaned up.
 - wxUpdateUIEvent now derives from wxCommandEvent
-  so event can travel up the window hierachy.
+  so event can travel up the window hierarchy.
 
 Alpha 14, July 31st 1998
 ------------------------
@@ -1183,7 +1183,7 @@ Generic:
 - Added wxMouseEvent::GetPosition and
   wxMouseEvent::GetLogicalPosition, both returning wxPoints.
 - Made wxSize and wxRect contain longs not ints.
-- Cured some lemory leaks (thanks Vadim).
+- Cured some memory leaks (thanks Vadim).
 - Tidied up OnIdle and introduced RequestMore/MoreRequested so
   will only keep processing OnIdle if it returns TRUE from
   MoreRequested.
@@ -1212,7 +1212,7 @@ All:
   implementation updated to use these base classes.
 - wxHelpInstance now separated into wxHelpControllerBase (base
   for all implementations), wxWinHelpController (uses standard
-  WinHelp), wxXLPHelPController (talks to wxHelp by DDE or
+  WinHelp), wxXLPHelpController (talks to wxHelp by DDE or
   TCP/IP). There will be others eventually, such as
   wxHTMLHelpController for Microsoft (and Netscape?) HTML Help.
 - Added Vadim Zeitlin's wxString class plus
@@ -1293,7 +1293,7 @@ At this point, the following has been achieved:
   Windows types where needed e.g. WXHWND.
 - PrologIO revised.
 - wxScrolledWindow, wxStatusBar and new MDI classes added.
-  MDI is now achived using separate classes, not window styles.
+  MDI is now achieved using separate classes, not window styles.
 - wxSystemSettings added, and made use of to reflect standard
   Windows settings.
 - SetButtonFont/SetLabelFont replaced by SetFont; font and colour

docs/gtk/changes.txt

@@ -20,7 +20,7 @@ in wxFilterStream and wxBufferedStream.
 
 Implemented new ref-counting for GDI classes.
 
-New implemenation of wxCondition.
+New implementation of wxCondition.
 
 Implemented actual comparisons between GDI classes instead of
 comparing just the ref-count.
@@ -65,7 +65,7 @@ wxStaticBox honours wxALIGN_XXX styles
 Reworked wxConfig class interface.
 
 Reworked wxDynamicLibary class for loading classes (particularly
-wxWindows classes) from dynmic libraries.
+wxWindows classes) from dynamic libraries.
 
 Removed wxObjectStream class.
 
@@ -74,7 +74,7 @@ Further improvements to wxFileName class.
 *** wxWindows 2.3.2 ***
 
 Addition of wxFileName class to handler DOS, Unix, Mac and VMS filenames
-and paths in a platform independant way.
+and paths in a platform independent way.
 
 Addition of a wxPopupWindow class to imitate temporary windows such
 as those used combo boxes or in tool tips.
@@ -104,7 +104,7 @@ reading support for ICO files. BMP can be saved in various bit depths now.
 Fixed some incompatibilities with GTK 1.2.10.
 
 Partially reworked build system for installation of multiple builds and
-cross coompilations.
+cross compilations.
 
 Improved wxSizer-based layout system for better support for dynamic
 layout.
@@ -142,7 +142,7 @@ Patch for better 8-bit-display support.
 
 Corrected log error message box.
 
-Implememted wxCommandEvent::IsSelection() for wxListBox.
+Implemented wxCommandEvent::IsSelection() for wxListBox.
 
 Corrected wxListBox::Set() for sorted mode.
 
@@ -164,7 +164,7 @@ Synchronized release with wxMSW again.
 Fixed bugs in HTTP code.
 
 Implemented wxNO_FULL_REPAINT_ON_RESIZE whenever possible
-and reduced flicker a little (no longer diables GTK's own
+and reduced flicker a little (no longer disables GTK's own
 anti-flicker code).
 
 Always have a clipping region equivalent to the update
@@ -191,7 +191,7 @@ Adobe fonts).
 Fixed wxSizer bug that made items with option
 flags greater than 1 report a wrong size.
 
-Fixed many incompatibilties with GTK themes -
+Fixed many incompatibilities with GTK themes -
 essentially a backport from the 2.3 branch.
 
 Added missing wxImage::Paste() for transparent
@@ -284,10 +284,10 @@ MANY bugfixes.
 
 Build fix. RPMs no loner require GTK's include files.
 
-An extra library for the OpenGl class now gets builts
+An extra library for the OpenGl class now gets built
 *** 19th March 2000: wxWindows 2.1.14 released ***
 
-An extra library for the OpenGl class now gets builts
+An extra library for the OpenGl class now gets built
 and installed. There is also an extra RPM for this
 small class now.
 
@@ -309,7 +309,7 @@ standards.
 Renamed wx-config to wxgtk-config so that motif can be co-installed
 on the same machine (with wxmotif-config).
 
-Speed up for drawing by resuing once created DCs instead of
+Speed up for drawing by reusing once created DCs instead of
 creating and destroying them all the time.
 
 Corrections to clipping region code (among others related to
@@ -359,7 +359,7 @@ Fixed endianness problems in image code.
 
 Minor fixes for sockets related to GUI reentrance. Also
 improved the IPV address class and added more error
-checking and rekated things.
+checking and related things.
 
 Many enhancements to wxHTML, more tags supported, better support
 for non-western texts etc.
@@ -380,7 +380,7 @@ Fixed problem with shared contexts in OpenGl canvas.
 
 Fixed keyboard handling in wxCheckListBox.
 
-Corrected the completely unfunctional TIFF code.
+Corrected the completely nonfunctional TIFF code.
 
 Various minor corrections to wxWizard, wxCalendarCtrl and other
 complex controls.
@@ -395,7 +395,7 @@ Build-fixes for various platforms and compilers.
 
 Who has a BigEndian computer (e.g. Sparc or PowerPC) that runs a 15
 and/or 16 bit colour mode? I need this for testing purposes, i.e. this
-person could help me by running a small testprogram and sending
+person could help me by running a small test program and sending
 me the output.
 
 Improved support for GTK's themes, changes in font sizes (and
@@ -509,7 +509,7 @@ conversion on big-endian architectures (such as Solaris),
 where color values get exchanged. I'd need help on this
 one as I have no BE computer.
 
-Enlightment has struck the majority of the developers and
+Enlightenment has struck the majority of the developers and
 they have chosen to use the Linux kernel numbering scheme
 for wxWindows from now on. This means that the next stable
 release will be called wxWindows 2.2.X, development snapshots
@@ -566,7 +566,7 @@ from Python and C++. Also HTML printing has been added.
 
 wxSpinCtrl added. Like a wxSpinButton and a wxTextCtrl.
 
-Changed the beaviour of the popular new wxFileDialog to
+Changed the behaviour of the popular new wxFileDialog to
 not forget the once typed file name when changing the
 directory.
 
@@ -610,7 +610,7 @@ A handler to read PCX file (in most variants) has been added.
 A number of problems with compressed and socket streams have
 been solved.
 
-Changed behavour of wxTextStream to make use of deliminators
+Changed behaviour of wxTextStream to make use of delimiters
 and default to space as the standard C++ stream do.
 
 Changes to tab traversal code to better reflect MSW code.
@@ -622,7 +622,7 @@ Made default button action work in more cases.
 28th August '99: Ninth wxGTK 2.1 snapshot released
 
 As the old makefile system didn't work, I trashed it and wrote
-a new one - mo more GNU. This, of course, caused a lot of people
+a new one - no more GNU. This, of course, caused a lot of people
 to start sing their song of complaints - any change is a good
 opportunity to complain, but the effect of the change is that
 we now have shared library support on Linux and Solaris (and
@@ -636,7 +636,7 @@ for using CVS versions are also much less (any make, any compiler,
 no other tools).
 
 Split RPMs into two, one for run-time requirements and one
-for developement (mostly headers).
+for development (mostly headers).
 
 Addition of new layout classes that work like Java's, GTK's
 or Qt`s - basically, you pack item in a box and let it tell
@@ -671,7 +671,7 @@ Small updates to socket code. The MSW version is still missing.
 
 Implemented wxBitmapDataObject class.
 
-Added wxFFileStream using FILE* instead if file desrcriptor.
+Added wxFFileStream using FILE* instead if file descriptor.
 Useful for creating a "cerr" like class as in normal C++.
 Also added "endl" for use with wxTextStream and fixed a few
 minor problems with buffered streams etc.
@@ -704,7 +704,7 @@ Controls now send the same messages (or more importantly none if
 changed programmatically) as per wxMSW.
 
 New implementation of wxSocket using an intermediate library called
-GSocket. This willl hopefully change in the future.
+GSocket. This will hopefully change in the future.
 
 Reworked in-place editing of wxListCtrl and wxTreeCtrl.
 
@@ -727,11 +727,11 @@ New documentation.
 
 New version of wxPython, of course.
 
-Fixed in unenclosed number of other bugs...
+Fixed an undisclosed number of other bugs...
 
 25th June '99: Seventh wxGTK 2.1 snapshot released
 
-Many fixes to th new makefile system. The last version gave
+Many fixes to the new makefile system. The last version gave
 immediate crashes on all Unices except Linux when linked
 dynamically against an application. I reordered the object
 files in the library as I guess that this was the cause.
@@ -755,10 +755,10 @@ The biggest change is the completely rewritten configure/makefile
 system using automake. The main argument for switching to automake
 is that the resulting makefiles should be more portable so that
 people can use the native make utilities instead of GNU make. The
-new makefile sytem also handles dependencies correctly, allows for
+new makefile system also handles dependencies correctly, allows for
 shared-only compilation, can be invoked from any directory for
-concurrent builds wihtin one source tree, uses libtool for greater
+concurrent builds within one source tree, uses libtool for greater
-shared-library platform support, has a functinonal "make uninstall",
+shared-library platform support, has a functional "make uninstall",
 works with GTK, Motif and WINE, conforms better to GNU standards
 as far as configure option names are concerned and is easier to
 maintain.
@@ -827,10 +827,10 @@ This is mostly a bug-fix release. We are having funny
 times to make wxGTK work well with different micro
 versions of GTK 1.2 - which is very close to impossible.
 All versions give warnings, although their number might
-vary a lot. I use GTK 1.2.3 and only get wanrnings in
+vary a lot. I use GTK 1.2.3 and only get warnings in
 one sample (notebook) and that one is due to a bug in
 GTK - some people using GTK 1.2.2 reported hundreds of warnings
-getting spitted out for what seems like no reason.
+getting spat out for what seems like no reason.
 
 This snapshot contains the beginnings of our merging of
 headers, meaning that in the future all ports will
@@ -905,7 +905,7 @@ This is mostly a bug-fix release. This affects wxSocket, wxThread,
 and a few GUI classes. Also more work has been done and window
 placement and decorations etc. which we hope to have finished now.
 
-Applied patches for FreeBSD and SGI compilation (not yet finshed).
+Applied patches for FreeBSD and SGI compilation (not yet finished).
 
 Updated wxPython to beta 9.
 
@@ -941,7 +941,7 @@ Internal changes required for wxOLE and addition of a very experimental
 wxOLE code section using GNOME's Bonobo library (from GNOME's CVS).
 
 New version of wxPython that works with the wxGTK 2.1.
-This now includes a very comprensive test/demo suite. Thanks to
+This now includes a very comprehensive test/demo suite. Thanks to
 Robin Dunn, Harm v.d. Heijden and others. Beware of the hang-man...
 
 More fine tuning of focus handling and GUI widgets.
@@ -955,7 +955,7 @@ such as in wxXt and wxMSW.
 
 Rewritten MDI subsystem.
 
-Correcetions and additions to the printing framework including
+Corrections and additions to the printing framework including
 a paper type database (Julian).
 
 Several controls now support more style flags for modifying
@@ -1015,7 +1015,7 @@ wxPython still doesn't compile, I think.
 
 This is the first developers' version of wxWindows 2.1 for GTK. It's main
 new feature is that it supports GTK 1.2 (as opposed to GTK 1.0) which
-will make development within the GNOME evironment a lot easier.
+will make development within the GNOME environment a lot easier.
 
 Apart from the move to GTK 1.2 and the changes (some major) that were
 required as part of that work, enhancement or corrections have been
@@ -1025,17 +1025,17 @@ and a few GUI classes (accelerators in menus, listbox always with
 scrollbar, wxFrame honours Motif Window Manager hints, corrected tab
 traversal for broken GTK 1.0 widgets).
 
-There have been slight changes to the priting dialogs and their
+There have been slight changes to the printing dialogs and their
 setup data (which might break apps using this code in previous
 versions). Also, a bug concerning printing white has been fixed
 (actually not tested).
 
 Although this is only the first 2.1 snapshot, there is little reason not
 to use it as many bugs from version 2.0 have been corrected. There are,
-pf course, still a few problem left with GTK 1.2 (some of which relate
+of course, still a few problem left with GTK 1.2 (some of which relate
 to bugs in GTK).
 
-I think I preserved backward compatility with GTK 1.0 and if not it
+I think I preserved backward compatibility with GTK 1.0 and if not it
 should be easy to fix - but mostly I don't care.
 
 Drag'N'Drop is currently completely broken. Also, wxPython currently
@@ -1043,9 +1043,9 @@ doesn't compile with this release. The OpenGL canvas still seems to
 work.
 
 Major targets for the final release (still a long way): a new configure
-system, support JPEG and GIF formats, wxHTML, super-duppah frame layout
+system, support JPEG and GIF formats, wxHTML, super-duper frame layout
 stuff, syntax-highlighting editor, possibly Unicode, possibly some GNOME
-gooddies, possibly world domination.
+goodies, possibly world domination.
 
 
 
@@ -1074,14 +1074,14 @@ Applied compile fixes for Solaris (different flavours and compilers).
 This is the fourth beta release and it contains mostly bug fixes and
 updates for documentation.
 
-Tracked a few more cases, where the bahaviour between wxMSW and wxGTK
+Tracked a few more cases, where the behaviour between wxMSW and wxGTK
 differed. This was the case for closing a dialog or frame as well as
 for clearing a device context or setting its background colour and some
 other minor details.
 
-Most standard dialogs have been face-liftet a little.
+Most standard dialogs have been face-lifted a little.
 
-Implememted default buttons for GTK.
+Implemented default buttons for GTK.
 
 Fixed many bugs. You guessed it.
 
@@ -1169,7 +1169,7 @@ Tkinter is dead, Java is dead, wxPython rules! That's all there is to say.
 Although only a few new classes have been added, many have been polished
 up substantially, the most visible are wxListCtrl, wxTreeCtrl and
 all classes related to printing. Also the DialogEd now functions
-much better than before. Drag'n'Drop is fucntional but probably won't
+much better than before. Drag'n'Drop is functional but probably won't
 be perfect until we use GTK 1.2 and its much improved DnD features.
 
 wxClipboard has arrived and works for text. Other formats have not been
@@ -1181,7 +1181,7 @@ include his very nice work later.
 
 wxDirDialog has been added (thanks to Harm von der Heijden).
 
-The entite "tab traveral" system for moving from item to item in
+The entire "tab traversal" system for moving from item to item in
 a dialog has been rewritten. It now completely overrides the
 not-so-well-done GTK native tab system.
 
@@ -1204,7 +1204,7 @@ resulting in unexpected behaviour so it was decided to remove these
 constructors.
 
 As the number of users and the number of test programs and samples
-is steadialy rising the core classes of wxWindows for MSW and GTK 1.0
+is steadily rising the core classes of wxWindows for MSW and GTK 1.0
 can be considered to be very stable if not outright bug-free. I haven't
 seen a crash for weeks now and wxWindows' internal debug features also
 have improved every week, making stepping-through with a debugger almost

docs/gtk/install.txt

@@ -36,11 +36,13 @@ If you want to remove wxWindows on Unix you can do this:
 
 If you want to do some more serious cross-platform programming with wxWindows,
 such as for GTK and Motif, you can now build two complete libraries and use
-them concurretly. For this end, you have to create a directory for each build
+them concurrently. For this end, you have to create a directory for each build
 of wxWindows - you may also want to create different versions of wxWindows
 and test them concurrently. Most typically, this would be a version configured
-with --enable-debug_flag and one without. Note, that only one build can currently
+with --enable-debug_flag and one without. Note, that only one build can
-be installed, so you'd have to use local version of the library for that purpose.
+currently be installed, so you'd have to use local version of the library for
+that purpose.
+
 For building three versions (one GTK, one Motif and a debug version of the GTK
 source) you'd do this:
 
@@ -84,7 +86,7 @@ support definitely won't).
 
 You get errors during compilation: The reason is that you probably have a
 broken compiler, which includes a lot of old gcc versions. In particular, if
-you use gcc 2.8 you have to disable optimsation as the compiler will give up
+you use gcc 2.8 you have to disable optimisation as the compiler will give up
 with an internal compiler error.
 
 You get immediate segfault when starting any sample or application: This is
@@ -122,7 +124,7 @@ YOU USE AND WHAT ERROR WAS REPORTED. I know this has no effect, but I tried...
 -----------------------
 
 wxWindows/GTK requires the GTK+ library to be installed on your system. It has
-to be a stable version, preferebly version 1.2.10 (at least 1.2.3 is required,
+to be a stable version, preferably version 1.2.10 (at least 1.2.3 is required,
 1.2.7 is strongly recommended).
 
 You can get the newest version of the GTK+ from the GTK homepage at:
@@ -189,7 +191,7 @@ as described above.
 
 If you have pthreads library installed, but have a gtk version
 which does not yet support threading, you need to explicitly
-diable threading by using the option --disable-threads.
+disable threading by using the option --disable-threads.
 
 Note that configure assumes your flex will generate files named
 "lexyy.c", not "lex.yy.c". If you have a version which does
@@ -284,8 +286,9 @@ The following options handle the kind of library you want to build.
     --enable-no_deps        Enable compilation without creation of
                             dependency information.
 
-    --enable-permissive     Enable compilation without creation of
+    --enable-permissive     Enable compilation without checking for strict
-                            giving erros as soon as you compile with
+                            ANSI conformance.  Useful to prevent the build
+                            dying with errors as soon as you compile with
                             Solaris' ANSI-defying headers.
 
     --enable-mem_tracing    Add built-in memory tracing.
@@ -343,7 +346,7 @@ are
 
     --disable-clipboard     Disables Clipboard.
 
-    --disable-serial        Disables object instance serialiasation.
+    --disable-serial        Disables object instance serialisation.
 
     --disable-streams       Disables the wxStream classes.
 
@@ -377,9 +380,9 @@ make yourself some coffee, as it will take some time. On an old
 warning messages depending in your compiler.
 
 If you want to be more selective, you can change into a specific
-directiry and type "make" there.
+directory and type "make" there.
 
-Then you may install the library and it's header files under
+Then you may install the library and its header files under
 /usr/local/include/wx and /usr/local/lib respectively. You
 have to log in as root (i.e. run "su" and enter the root
 password) and type
@@ -420,7 +423,7 @@ clean:
 	rm -f *.o minimal
 
 This is certain to become the standard way unless we decide
-to sitch to tmake.
+to stick to tmake.
 
 2) The other way creates a project within the source code
 directories of wxWindows. For this endeavour, you'll need

docs/gtk/makewxgtk

@@ -3,7 +3,7 @@
 # and makes wxGTK.
 # Call from top-level wxWindows directory.
 # Note that this uses standard (but commonly-used) configure options;
-# if you're feeling braven, you may wish to compile with threads.
+# if you're feeling brave, you may wish to compile with threads.
 # -- Julian Smart
 rm -f *.cache
 chmod a+x configure config.sub config.guess samples/configure demos/configure contrib/configure

docs/html/faqgen.htm

@@ -130,10 +130,10 @@ platform-independent code, such as the wxTreeCtrl and wxListCtrl classes.<P>
 No. This is a much-discussed topic that has (many times) ended with the conclusion that it is in
 wxWindows&#39; best interests to avoid use of templates. Not all compilers can handle
 templates adequately so it would dramatically reduce the number of compilers
-and platforms that could be supported. It would also be undersirable to make
+and platforms that could be supported. It would also be undesirable to make
 wxWindows dependent on another large library that may have to be downloaded and installed.
 In addition, use of templates can lead to executable bloat, which is something
-wxWindows 2 is strenously trying to avoid.<P>
+wxWindows 2 is strenuously trying to avoid.<P>
 
 The standard C++ string class is not used, again because it is not available to all compilers,
 and it is not necessarily a very efficient implementation. Also, we retain more flexibility

docs/html/faqmac.htm

@@ -30,11 +30,11 @@ See also <a href="faq.htm">top-level FAQ page</a>.
 <li><a href="#macosx">How is the Mac OS X port different from the Classic Mac OS port?</a></li>
 <li><a href="#macclassic">How are improvements to the Classic Mac OS port integrated into the Mac OS X port?</a></li>
 <li><a href="#compilers">What compilers are supported?</a></li>
-<li><a href="#filetypes">How does CVS handle file types/creators under Mac OS 8.x /9.x?</a></li>
+<li><a href="#filetypes">How does CVS handle file types/creators under Mac OS 8.x/9.x?</a></li>
-<li><a href="#filetypesx">How does CVS handle file types/creators under Mac OS X? </a></li>
+<li><a href="#filetypesx">How does CVS handle file types/creators under Mac OS X?</a></li>
-<li><a href="#cwpro53">What steps are required to build wxMac using CodeWarrior P ro 5.3?</a></li>
+<li><a href="#cwpro53">What steps are required to build wxMac using CodeWarrior Pro 5.3?</a></li>
 <li><a href="#buildx">What steps are required to build wxMac under Mac OS X?</a></li>
-<li><a href="#settings">What important settings are required in the CodeWarrior P roject Preferences?</a></li>
+<li><a href="#settings">What important settings are required in the CodeWarrior Project Preferences?</a></li>
 <li><a href="#smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></li>
 <li><a href="#aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></li>
 </ul>

docs/html/faqmot.htm

@@ -64,7 +64,7 @@ system is in preparation.
 
 <h3><a name="dialoged">Does Dialog Editor work with wxWindows for Motif?</a></h3>
 
-Suport for Dialog Editor is almost there, but there are some wrinkles to iron
+Support for Dialog Editor is almost there, but there are some wrinkles to iron
 out. You may find it&#39;s useful though: compile it and see.
 <P>
 

docs/html/faqmsw.htm

@@ -305,7 +305,7 @@ The templates are described in tmake ref manual (1-2 pages of text)
 and are quite simple. They do contain some Perl code, but my Perl is
 primitive (very C like) so it should be possible for anybody to make
 trivial modifications to it (I hope that only trivial modifications
-will be needed). I've tagged the ol makefiles as MAKEFILES_WITHOUT_TMAKE
+will be needed). I've tagged the old makefiles as MAKEFILES_WITHOUT_TMAKE
 in the cvs, so you can always retrieve them and compare the new ones,
 this will make it easier to solve the problems you might have.<P>
 

docs/html/gettext/gettext_1.html

@@ -444,7 +444,7 @@ While editing a PO file, PO mode allows for the easy browsing of
 auxiliary and compendium PO files, as well as for following references into
 the set of C program sources from which PO files have been derived.
 It has a few special features, among which are the interactive marking
-of program strings as translatable, and the validatation of PO files
+of program strings as translatable, and the validation of PO files
 with easy repositioning to PO file lines showing errors.
 
 </P>

docs/html/gettext/gettext_10.html

@@ -153,7 +153,7 @@ translator teams get interested in your package, and submit PO files.
 <P>
 It is worth adding here a few words about how the maintainer should
 ideally behave with PO files submissions.  As a maintainer, your role is
-to authentify the origin of the submission as being the representative
+to authenticate the origin of the submission as being the representative
 of the appropriate translating teams of the Translation Project (forward
 the submission to <TT>`translation@iro.umontreal.ca'</TT> in case of doubt),
 to ensure that the PO file format is not severely broken and does not

docs/html/gettext/gettext_12.html

@@ -17,7 +17,7 @@
 
 <P>
 The ISO 639 standard defines two character codes for many countries.
-All abreviations for countries or languages used in the Translation
+All abbreviations for countries or languages used in the Translation
 Project should come from this standard.
 
 </P>

docs/html/gettext/gettext_2.html

@@ -149,7 +149,7 @@ the full control she needs.
 The comment lines beginning with <KBD>#,</KBD> are special because they are
 not completely ignored by the programs as comments generally are.  The
 comma separated list of <VAR>flag</VAR>s is used by the <CODE>msgfmt</CODE>
-program to give the user some better disgnostic messages.  Currently
+program to give the user some better diagnostic messages.  Currently
 there are two forms of flags defined:
 
 </P>
@@ -171,7 +171,7 @@ search only.  See section <A HREF="gettext_5.html#SEC26">Fuzzy Entries</A>.
 <DT><KBD>no-c-format</KBD>
 <DD>
 These flags should not be added by a human.  Instead only the
-<CODE>xgettext</CODE> program adds them.  In an automatized PO file processing
+<CODE>xgettext</CODE> program adds them.  In an automated PO file processing
 system as proposed here the user changes would be thrown away again as
 soon as the <CODE>xgettext</CODE> program generates a new template file.
 
@@ -199,7 +199,7 @@ not having GNU Emacs handy should carefully continue reading on.
 <P>
 Each of <VAR>untranslated-string</VAR> and <VAR>translated-string</VAR> respects
 the C syntax for a character string, including the surrounding quotes
-and imbedded backslashed escape sequences.  When the time comes
+and embedded backslashed escape sequences.  When the time comes
 to write multi-line strings, one should not use escaped newlines.
 Instead, a closing quote should follow the last character on the
 line to be continued, and an opening quote should resume the string
@@ -540,7 +540,7 @@ merely use <KBD>x</KBD> for making the switch.
 There are many different ways for encoding a particular string into a
 PO file entry, because there are so many different ways to split and
 quote multi-line strings, and even, to represent special characters
-by backslahsed escaped sequences.  Some features of PO mode rely on
+by backslashed escaped sequences.  Some features of PO mode rely on
 the ability for PO mode to scan an already existing PO file for a
 particular string encoded into the <CODE>msgid</CODE> field of some entry.
 Even if PO mode has internally all the built-in machinery for

docs/html/gettext/gettext_3.html

@@ -94,7 +94,7 @@ numbers in the <CODE>"C"</CODE> locale format.  In some situation, it might
 also be a problem with the notation itself which makes it impossible to
 recognize whether the number is in the <CODE>"C"</CODE> locale or the local
 format.  This can happen if thousands separator characters are used.
-Some locales define this character accordfing to the national
+Some locales define this character according to the national
 conventions to <CODE>'.'</CODE> which is the same character used in the
 <CODE>"C"</CODE> locale to denote the decimal point.
 
@@ -524,7 +524,7 @@ Consider the following case:
 <P>
 While it is no problem to mark the string <CODE>"a default message"</CODE> it
 is not possible to mark the string initializers for <CODE>messages</CODE>.
-What is to be done?  We have to fulfill two tasks.  First we have to mark the
+What is to be done?  We have to fulfil two tasks.  First we have to mark the
 strings so that the <CODE>xgettext</CODE> program (see section <A HREF="gettext_4.html#SEC20">Invoking the <CODE>xgettext</CODE> Program</A>)
 can find them, and second we have to translate the string at runtime
 before printing them.

docs/html/gettext/gettext_4.html

@@ -106,7 +106,7 @@ Join messages with existing file.
 <DD>
 <DT><SAMP>`--keyword[=<VAR>word</VAR>]'</SAMP>
 <DD>
-Additonal keyword to be looked for (without <VAR>word</VAR> means not to
+Additional keyword to be looked for (without <VAR>word</VAR> means not to
 use default keywords).
 
 The default keywords, which are always looked for if not explicitly
@@ -194,7 +194,7 @@ adjacent strings, and escaped end of lines for continued strings.
 <H2><A NAME="SEC21" HREF="gettext_toc.html#TOC21">C Sources Context</A></H2>
 
 <P>
-PO mode is particularily powerful when used with PO files
+PO mode is particularly powerful when used with PO files
 created through GNU <CODE>gettext</CODE> utilities, as those utilities
 insert special comments in the PO files they generate.
 Some of these special comments relate the PO file entry to
@@ -205,7 +205,7 @@ exactly where the untranslated string appears in the program sources.
 When the translator gets to an untranslated entry, she is fairly
 often faced with an original string which is not as informative as
 it normally should be, being succinct, cryptic, or otherwise ambiguous.
-Before chosing how to translate the string, she needs to understand
+Before choosing how to translate the string, she needs to understand
 better what the string really means and how tight the translation has
 to be.  Most of times, when problems arise, the only way left to make
 her judgment is looking at the true program sources from where this
@@ -222,7 +222,7 @@ translator should not be shy at taking a look, once in a while.
 It is most probable that she will still be able to find some of the
 hints she needs.  She will learn quickly to not feel uncomfortable
 in program code, paying more attention to programmer's comments,
-variable and function names (if he dared chosing them well), and
+variable and function names (if he dared choosing them well), and
 overall organization, than to programmation itself.
 
 </P>

docs/html/gettext/gettext_5.html

@@ -70,7 +70,7 @@ See section <A HREF="gettext_5.html#SEC26">Fuzzy Entries</A>.
 
 <P>
 Each PO file entry may have a set of <STRONG>attributes</STRONG>, which are
-qualities given an name and explicitely associated with the entry
+qualities given an name and explicitly associated with the entry
 translation, using a special system comment.  One of these attributes
 has the name <CODE>fuzzy</CODE>, and entries having this attribute are said
 to have a fuzzy translation.  They are called fuzzy entries, for short.

docs/html/gettext/gettext_6.html

@@ -70,7 +70,7 @@ translation errors.  The <CODE>msgid</CODE> and <CODE>msgstr</CODE> strings are
 studied and compared.  It is considered abnormal that one string
 starts or ends with a newline while the other does not.
 
-Also, if the string represents a format sring used in a
+Also, if the string represents a format string used in a
 <CODE>printf</CODE>-like function both strings should have the same number of
 <SAMP>`%'</SAMP> format specifiers, with matching types.  If the flag
 <CODE>c-format</CODE> or <CODE>possible-c-format</CODE> appears in the special

docs/html/gettext/gettext_9.html

@@ -167,7 +167,7 @@ On the other end, people might enjoy their own language a lot, and be
 very motivated at providing to themselves the pleasure of having their
 beloved free software speaking their mother tongue.  They do themselves
 a personal favor, and do not pay that much attention to the number of
-people beneficiating of their work.
+people benefiting of their work.
 
 <LI>Misinterpretation
 

docs/html/news.htm

@@ -125,8 +125,8 @@ Among the many new features that have appeared since version 2.0
 was release are:
 
 <ul>
-<li> A great number of incompatiblities between the GTK and the MSW port have been removed. This
+<li> A great number of incompatibilities between the GTK and the MSW port have been removed. This
-holds escecially true for the way, time and order, controls send notifications to the user program.
+holds especially true for the way, time and order, controls send notifications to the user program.
 <li> Practically all widgets have been updated, removing bugs or adding missing features to
 specific ports (mostly the GTK port).
 <li> The GTK port now supports GTK version 1.2 as well as 1.0, giving access to the many new
@@ -134,7 +134,7 @@ features, such as e.g. menu accelerators.
 <li> Many of the non-GUI classes have been reworked and new ones added, the stream classes
 having undergone a complete rewrite.
 <li> The addition of code to handle Unicode has begun and is in an advanced state.
-<li> The Python bindings (wxPython) have been largely improved and upadted to the newest
+<li> The Python bindings (wxPython) have been largely improved and updated to the newest
 API and features.
 </ul>
 

docs/html/wxbook.htm

@@ -135,7 +135,7 @@ if you would like to contribute.
 
 <H3><a name="publication">Publication</a></H3>
 
-We wll investigate publishers, especially O'Reilly. We will have to get together
+We will investigate publishers, especially O'Reilly. We will have to get together
 several sample chapters to convince a publisher that the many-author approach will
 work.<P>
 

docs/latex/book/chap_images.tex

@@ -16,7 +16,7 @@ and one for blue, thus yielding the classical RGB acronym. Due to the
 simplicity of wxImage, you will do all kinds of image manipulation
 with this class, this includes loading images in various formats
 such as GIF, TIFF or JPEG (these and some more are supported by wxWindows 
-without further work), analyizing the image in terms of colour usage etc
+without further work), analyzing the image in terms of colour usage etc
 and applying filters to the image for higher-level manipulation, such
 as blurring, sharpening etc.
 

docs/latex/book/chap_install.tex

@@ -88,7 +88,7 @@ points to the correct library. There is no way to compile wxGTK if configure
 doesn't pass this test as all this test does is compile and link a GTK program.
 \item You get errors during compilation: The reason is that you probably have a broken 
 compiler, which includes almost everything that is called gcc. If you use gcc 2.8 
-you have to disable optimsation as the compiler will give up with an internal 
+you have to disable optimisation as the compiler will give up with an internal 
 compiler error.You get immediate segfault when starting any sample or application: This is either 
 due to having compiled the library with different flags or options than your program - 
 typically you might have the __WXDEBUG__ option set for the library but not for your 
@@ -120,7 +120,7 @@ report to one of the mailing lists.
 \wxheading{Libraries needed}
 
 wxWindows/GTK requires the GTK+ library to be installed on your system. It has to 
-be a stable version, preferebly version 1.2.3.
+be a stable version, preferably version 1.2.3.
 
 You can get the newest version of the GTK+ from the GTK homepage at:
 
@@ -188,7 +188,7 @@ as described above.
 
 If you have pthreads library installed, but have a gtk version
 which does not yet support threading, you need to explicitly
-diable threading by using the option --disable-threads.
+disable threading by using the option --disable-threads.
 
 Note that configure assumes your flex will generate files named
 "lexyy.c", not "lex.yy.c". If you have a version which does
@@ -300,9 +300,10 @@ The following options handle the kind of library you want to build.
 	--enable-no_deps        Enable compilation without creation of
 	                        dependency information.
 				
-	--enable-permissive     Enable compilation without creation of
+        --enable-permissive     Enable compilation without checking for strict
-	                        giving erros as soon as you compile with
+                                ANSI conformance.  Useful to prevent the build
-				            Solaris' ANSI-defying headers.
+                                dying with errors as soon as you compile with
+                                Solaris' ANSI-defying headers.
 				
 	--enable-mem_tracing    Add built-in memory tracing.
 				
@@ -359,7 +360,7 @@ are
 	
 	--disable-clipboard     Disables Clipboard.
 	
-	--disable-serial        Disables object instance serialiasation.
+	--disable-serial        Disables object instance serialisation.
 	
 	--disable-streams       Disables the wxStream classes.
 	
@@ -395,7 +396,7 @@ make yourself some coffee, as it will take some time. On an old
 warning messages depending in your compiler.
 
 If you want to be more selective, you can change into a specific
-directiry and type "make" there.
+directory and type "make" there.
 
 Then you may install the library and it's header files under
 /usr/local/include/wx and /usr/local/lib respectively. You
@@ -447,7 +448,7 @@ clean:
 \end{verbatim}
 
 This is certain to become the standard way unless we decide
-to sitch to tmake.
+to stick to tmake.
 
 2) The other way creates a project within the source code 
 directories of wxWindows. For this endeavour, you'll need

docs/latex/book/psbox.tex

@@ -479,7 +479,7 @@ press x or e) and rename it before retrying.}
 %
 % \textleftof\anybox: Sample text\endtext
 %   inserts "Sample text" on the left of \anybox ie \vbox, \psbox.
-%   \textrightof is the symmetric (not documented, too uggly)
+%   \textrightof is the symmetric (not documented, too ugly)
 % Welcome any suggestion about clean wraparound macros from
 %   TeXhackers reading this
 %

docs/latex/wx/app.tex

@@ -345,7 +345,7 @@ work and, in fact, probably won't.
 %%application have all been processed, wxWindows sends an OnIdle event to the application object. wxApp::OnIdle itself
 %%sends an OnIdle event to each application window, allowing windows to do idle processing such as updating
 %%their appearance. If either wxApp::OnIdle or a window OnIdle function requested more time, by
-%%caling \helpref{wxIdleEvent::RequestMore}{wxidleeventrequestmore}, wxWindows will send another OnIdle
+%%calling \helpref{wxIdleEvent::RequestMore}{wxidleeventrequestmore}, wxWindows will send another OnIdle
 %%event to the application object. This will occur in a loop until either a user event is found to be
 %%pending, or OnIdle requests no more time. Then all pending user events are processed until the system
 %%goes idle again, when OnIdle is called, and so on.
@@ -449,7 +449,7 @@ may wish to process it. The function returns TRUE if the message
 was processed, FALSE otherwise. If you use wxWindows with another class
 library with its own message loop, you should make sure that this
 function is called to allow wxWindows to receive messages. For example,
-to allow co-existance with the Microsoft Foundation Classes, override
+to allow co-existence with the Microsoft Foundation Classes, override
 the PreTranslateMessage function:
 
 \begin{verbatim}
@@ -587,7 +587,7 @@ wxWindows.
 Allows the programmer to specify whether the application will use the best visual
 on systems that support several visual on the same display. This is typically the
 case under Solaris and IRIX, where the default visual is only 8-bit whereas certain
-appications are supposed to run in TrueColour mode.
+applications are supposed to run in TrueColour mode.
 
 Note that this function has to be called in the constructor of the {\tt wxApp} 
 instance and won't have any effect when called later on.

docs/latex/wx/array.tex

@@ -97,7 +97,7 @@ class MyDirectory
 // now that we have MyDirectory declaration in scope we may finish the
 // definition of ArrayOfDirectories -- note that this expands into some C++
 // code and so should only be compiled once (i.e., don't put this in the
-// header, but into a source file or you will get linkin errors)
+// header, but into a source file or you will get linking errors)
 #include <wx/arrimpl.cpp> // this is a magic incantation which must be done!
 WX_DEFINE_OBJARRAY(ArrayOfDirectories);
 
@@ -177,7 +177,7 @@ amount, but no more than some maximal number which is defined by
 ARRAY\_MAXSIZE\_INCREMENT constant. Of course, this may lead to some memory
 being wasted (ARRAY\_MAXSIZE\_INCREMENT in the worst case, i.e. 4Kb in the
 current implementation), so the \helpref{Shrink()}{wxarrayshrink} function is
-provided to unallocate the extra memory. The \helpref{Alloc()}{wxarrayalloc} 
+provided to deallocate the extra memory. The \helpref{Alloc()}{wxarrayalloc} 
 function can also be quite useful if you know in advance how many items you are
 going to put in the array and will prevent the array code from reallocating the
 memory more times than needed.

docs/latex/wx/arrstrng.tex

@@ -26,14 +26,14 @@ array elements may be modified in place like this
     array.Last().MakeUpper();
 \end{verbatim}
 
-There is also a varian of wxArrayString called wxSortedArrayString which has
+There is also a variant of wxArrayString called wxSortedArrayString which has
 exactly the same methods as wxArrayString, but which always keeps the string
 in it in (alphabetical) order. wxSortedArrayString uses binary search in its 
-\helpref{Index}{wxarraystringindex} function (insteadf of linear search for
+\helpref{Index}{wxarraystringindex} function (instead of linear search for
 wxArrayString::Index) which makes it much more efficient if you add strings to
 the array rarely (because, of course, you have to pay for Index() efficiency
 by having Add() be slower) but search for them often. Several methods should
-not be used with sorted array (basicly, all which break the order of items)
+not be used with sorted array (basically, all which break the order of items)
 which is mentioned in their description.
 
 Final word: none of the methods of wxArrayString is virtual including its

docs/latex/wx/autoobj.tex

@@ -92,7 +92,7 @@ Gets the IDispatch pointer.
 \constfunc{bool}{GetInstance}{\param{const wxString\&}{ classId}}
 
 Retrieves the current object associated with a class id, and attaches the IDispatch pointer
-to this object. Returns TRUE if a pointer was succesfully retrieved, FALSE otherwise.
+to this object. Returns TRUE if a pointer was successfully retrieved, FALSE otherwise.
 
 Note that this cannot cope with two instances of a given OLE object being active simultaneously,
 such as two copies of Excel running. Which object is referenced cannot currently be specified.

docs/latex/wx/body.tex

@@ -176,7 +176,7 @@ and/or \urlref{http://www.wxwindows.org}{http://www.wxwindows.org}.}
 
 You can also buy a CD-ROM using the form on the Web site.
 
-\section{Acknowledgments}
+\section{Acknowledgements}
 
 Thanks are due to AIAI for being willing to release the original version of
 wxWindows into the public domain, and to our patient partners.

docs/latex/wx/calctrl.tex

@@ -29,7 +29,7 @@ font and without border, but setting custom attributes with
 create a custom attribute object and set it for the day you want to be
 displayed specially (note that the control will take ownership of the pointer,
 i.e. it will delete it itself). A day may be marked as being a holiday, even
-if it is not reckognized as oen by \helpref{wxDateTime}{tdateholidays} using 
+if it is not recognized as one by \helpref{wxDateTime}{tdateholidays} using 
 \helpref{SetHoliday}{wxcalendardateattrsetholiday} method.
 
 As the attributes are specified for each day, they may change when the month
@@ -70,7 +70,7 @@ direct input to member functions that take a
 
 \twocolwidtha{7cm}
 \begin{twocollist}\itemsep=7pt
-\twocolitem{{\bf EVT\_CALENDAR(id, func)}}{A day was double clickedi n the calendar.}
+\twocolitem{{\bf EVT\_CALENDAR(id, func)}}{A day was double clicked in the calendar.}
 \twocolitem{{\bf EVT\_CALENDAR\_SEL\_CHANGED(id, func)}}{The selected date changed.}
 \twocolitem{{\bf EVT\_CALENDAR\_DAY(id, func)}}{The selected day changed.}
 \twocolitem{{\bf EVT\_CALENDAR\_MONTH(id, func)}}{The selected month changed.}
@@ -148,7 +148,7 @@ Gets the currently selected date.
 \func{void}{EnableYearChange}{\param{bool }{enable = TRUE}}
 
 This function should be used instead of changing {\tt wxCAL\_NO\_YEAR\_CHANGE}
-style bit directly. It allows or disallows the user to chaneg the year
+style bit directly. It allows or disallows the user to change the year
 interactively.
 
 \membersection{wxCalendarCtrl::EnableMonthChange}\label{wxcalendarctrlenablemonthchange}
@@ -231,7 +231,7 @@ window style includes {\tt wxCAL\_SHOW\_HOLIDAYS} flag).
 
 \constfunc{const wxColour\&}{GetHolidayColourFg}{\void}
 
-Return the foregound colour currently used for holiday highlighting.
+Return the foreground colour currently used for holiday highlighting.
 
 \wxheading{See also}
 

docs/latex/wx/cmdevent.tex

@@ -41,7 +41,7 @@ wxTE\_PROCESS\_ENTER flag when creating the control if you want it to generate
 such events.}
 \twocolitem{{\bf EVT\_TEXT\_MAXLEN(id, func)}}{Process a wxEVT\_COMMAND\_TEXT\_MAXLEN command,
 which is generated by a wxTextCtrl control when the user tries to enter more
-characters into it than the limit previosuly set with 
+characters into it than the limit previously set with 
 \helpref{SetMaxLength}{wxtextctrlsetmaxlength}.}
 \twocolitem{{\bf EVT\_MENU(id, func)}}{Process a wxEVT\_COMMAND\_MENU\_SELECTED command,
 which is generated by a menu item.}

docs/latex/wx/cmdlpars.tex

@@ -178,7 +178,7 @@ combination of \helpref{AddSwitch}{wxcmdlineparseraddswitch},
 
 Using constructors or \helpref{SetDesc}{wxcmdlineparsersetdesc} uses a (usually 
 {\tt const static}) table containing the command line description. If you want
-to decide which options to acccept during the run-time, using one of the 
+to decide which options to accept during the run-time, using one of the 
 {\tt AddXXX()} functions above might be preferable.
 
 \membersection{Customization}\label{wxcmdlineparsercustomization}

docs/latex/wx/colour.tex

@@ -233,7 +233,7 @@ The default custom colours are all white.
 
 \func{void}{operator $=$}{\param{const wxColourData\&}{ data}}
 
-Assingment operator for the colour data.
+Assignment operator for the colour data.
 
 \section{\class{wxColourDatabase}}\label{wxcolourdatabase}
 

docs/latex/wx/command.tex

@@ -28,7 +28,7 @@ a new class and call this constructor from your own constructor.
 
 {\it canUndo} tells the command processor whether this command is undo-able. You
 can achieve the same functionality by overriding the CanUndo member function (if for example
-the criteria for undoability is context-dependant).
+the criteria for undoability is context-dependent).
 
 {\it name} must be supplied for the command processor to display the command name
 in the application's edit menu.

docs/latex/wx/config.tex

@@ -187,7 +187,7 @@ config file. All functions here return FALSE when there are no more items.
 
 You must pass the same index to GetNext and GetFirst (don't modify it).
 Please note that it is {\bf not} the index of the current item (you will have
-some great surprizes with wxRegConfig if you assume this) and you shouldn't
+some great surprises with wxRegConfig if you assume this) and you shouldn't
 even look at it: it is just a "cookie" which stores the state of the
 enumeration. It can't be stored inside the class because it would prevent you
 from running several enumerations simultaneously, that's why you must pass it

docs/latex/wx/critsect.tex

@@ -39,7 +39,7 @@ Default constructor initializes critical section object.
 
 \func{}{\destruct{wxCriticalSection}}{\void}
 
-Destructor frees the ressources.
+Destructor frees the resources.
 
 \membersection{wxCriticalSection::Enter}\label{wxcriticalsectionenter}
 

docs/latex/wx/crtslock.tex

@@ -9,7 +9,7 @@ and difficult to debug problems).
 Example of using it:
 
 \begin{verbatim}
-void SetFoo()
+void Set Foo()
 {
     // gs_critSect is some (global) critical section guarding access to the
     // object "foo"
@@ -59,5 +59,5 @@ Constructs a wxCriticalSectionLocker object associated with given
 
 \func{}{\destruct{wxCriticalSectionLocker}}{\void}
 
-Destuctor leaves the critical section.
+Destructor leaves the critical section.
 

docs/latex/wx/cursor.tex

@@ -69,7 +69,7 @@ Constructs a cursor using a cursor identifier.
 
 \func{}{wxCursor}{\param{const wxImage\&}{ image}}
 
-Constructs a cursor from a wxImage. The cursor is monochome, colors with the RGB elements all greater
+Constructs a cursor from a wxImage. The cursor is monochrome, colors with the RGB elements all greater
 than 127 will be foreground, colors less than this background. The mask (if any) will be used as transparent.
 
 In MSW the foreground will be white and the background black. The cursor is resized to 32x32
@@ -162,7 +162,7 @@ hotSpotY=0)}}{Constructs a cursor from a filename}
 \end{twocollist}}
 }
 
-\perlnote{Contructors supported by wxPerl are:\par
+\perlnote{Constructors supported by wxPerl are:\par
 \begin{itemize}
 \item{Wx::Cursor->new( name, type, hotSpotX = 0, hotSpotY = 0 )}
 \item{Wx::Cursor->new( id )}

docs/latex/wx/dataobj.tex

@@ -36,7 +36,7 @@ enum Direction
 which allows to distinguish between them. See 
 \helpref{wxDataFormat}{wxdataformat} documentation for more about formats.
 
-Not surprizingly, being 'smart' comes at a price of added complexity. This is
+Not surprisingly, being 'smart' comes at a price of added complexity. This is
 reasonable for the situations when you really need to support multiple formats,
 but may be annoying if you only want to do something simple like cut and paste
 text.

docs/latex/wx/datetime.tex

@@ -546,14 +546,14 @@ DST convention and date and time formatting rules.
 
 \func{static bool}{IsDSTApplicable}{\param{int }{year = Inv\_Year}, \param{Country }{country = Country\_Default}}
 
-Returns {\tt TRUE} if DST was usedi n the given year (the current one by
+Returns {\tt TRUE} if DST was used n the given year (the current one by
 default) in the given country.
 
 \membersection{wxDateTime::Now}\label{wxdatetimenow}
 
 \func{static wxDateTime}{Now}{\void}
 
-Returns the object corresopnding to the current time.
+Returns the object corresponding to the current time.
 
 Example:
 
@@ -564,7 +564,7 @@ Example:
 
 Note that this function is accurate up to second: 
 \helpref{wxDateTime::UNow}{wxdatetimeunow} should be used for better precision
-(but it is less efficient and might not be availabel on all platforms).
+(but it is less efficient and might not be available on all platforms).
 
 \wxheading{See also}
 
@@ -599,7 +599,7 @@ same as \helpref{Now()}{wxdatetimenow}, but the time part is set to $0$).
 
 \func{static wxDateTime}{UNow}{\void}
 
-Returns the object corresopnding to the current time including the
+Returns the object corresponding to the current time including the
 milliseconds if a function to get time with such precision is available on the
 current platform (supported under most Unices and Win32).
 
@@ -677,7 +677,7 @@ since Jan 1, 1970.
 
 \func{wxDateTime\&}{Set}{\param{const struct tm\& }{tm}}
 
-Sets the date and tiem from the broken down representation in the standard
+Sets the date and time from the broken down representation in the standard
 {\tt tm} structure.
 
 \pythonnote{Unsupported.}
@@ -690,7 +690,7 @@ Sets the date from the so-called {\it Julian Day Number}.
 
 By definition, the Julian Day Number, usually abbreviated as JDN, of a
 particular instant is the fractional number of days since 12 hours Universal
-Coordinated Time (Greenwhich mean noon) on January 1 of the year -4712 in the
+Coordinated Time (Greenwich mean noon) on January 1 of the year -4712 in the
 Julian proleptic calendar.
 
 \pythonnote{This method is named {\tt SetJDN} in wxPython.}
@@ -916,7 +916,7 @@ Returns {\tt TRUE} if this date lies strictly between the two others,
 \constfunc{bool}{IsBetween}{\param{const wxDateTime\& }{t1}, \param{const wxDateTime\& }{t2}}
 
 Returns {\tt TRUE} if \helpref{IsStrictlyBetween}{wxdatetimeisstrictlybetween}
-is {\tt TRUE} or if the date is equal to one of the limi values.
+is {\tt TRUE} or if the date is equal to one of the limit values.
 
 \wxheading{See also}
 
@@ -1016,7 +1016,7 @@ the character immediately following the part of the string which could be
 parsed. If the entire string contains only the date in RFC 822 format,
 the returned pointer will be pointing to a {\tt NUL} character.
 
-This function is intenionally strict, it will return an error for any string
+This function is intentionally strict, it will return an error for any string
 which is not RFC 822 compliant. If you need to parse date formatted in more
 free ways, you should use \helpref{ParseDateTime}{wxdatetimeparsedatetime} or
 \helpref{ParseDate}{wxdatetimeparsedate} instead.
@@ -1088,7 +1088,7 @@ Please see its description for the meaning of {\it format} parameter.
 
 It also accepts a few wxWindows-specific extensions: you can optionally specify
 the width of the field to follow using {\tt printf(3)}-like syntax and the
-format specificator {\tt \%l} can be used to get the number of milliseconds.
+format specification {\tt \%l} can be used to get the number of milliseconds.
 
 \wxheading{See also}
 
@@ -1179,7 +1179,7 @@ Returns the copy of this object to which
 
 Sets the date to the {\it n}-th {\it weekday} in the given month of the given
 year (the current month and year are used by default). The parameter {\it n}
-may be either opsitive (counting from the beginning of the month) or negative
+may be either positive (counting from the beginning of the month) or negative
 (counting from the end of it).
 
 For example, {\tt SetToWeekDay(2, wxDateTime::Wed)} will set the date to the

docs/latex/wx/datistrm.tex

@@ -1,7 +1,7 @@
 \section{\class{wxDataInputStream}}\label{wxdatainputstream}
 
 This class provides functions that read binary data types in a
-portable way. Data can be read in either big-endian or litte-endian
+portable way. Data can be read in either big-endian or little-endian
 format, little-endian being the default on all architectures.
 
 If you want to read data from text files (or streams) use 

docs/latex/wx/datostrm.tex

@@ -1,7 +1,7 @@
 \section{\class{wxDataOutputStream}}\label{wxdataoutputstream}
 
 This class provides functions that write binary data types in a
-portable way. Data can be written in either big-endian or litte-endian
+portable way. Data can be written in either big-endian or little-endian
 format, little-endian being the default on all architectures.
 
 If you want to write data to text files (or streams) use 

docs/latex/wx/db.tex

@@ -733,7 +733,7 @@ of processing.
 
 Older form (pre-2.3/2.4 of wxWindows) of the
 \helpref{wxDb::IsFwdOnlyCursors}{wxdbisfwdonlycursors}.  This method is
-provided for backward compatability only.  The method
+provided for backward compatibility only.  The method
 \helpref{wxDb::IsFwdOnlyCursors}{wxdbisfwdonlycursors} should be
 used in place of this method.
 
@@ -3105,7 +3105,7 @@ If the function returns a FALSE value due to the table not existing, a log
 entry is recorded for the datasource connection indicating the problem
 that was detected when checking for table existence.  Note that it is usually
 best for the calling routine to check for the existence of the table and for
-sufficent user privileges to access the table in the mode (wxDB\_QUERY\_ONLY or
+sufficient user privileges to access the table in the mode (wxDB\_QUERY\_ONLY or
 !wxDB\_QUERY\_ONLY) before trying to open the table for the best possible
 explanation as to why a table cannot be opened.
 

docs/latex/wx/dc.tex

@@ -694,7 +694,7 @@ Gets the current text foreground colour (see \helpref{wxDC::SetTextForeground}{w
 
 Gets the current user scale factor (set by \helpref{SetUserScale}{wxdcsetuserscale}).
 
-\perlnote{In wxPerl this method takes no arguments and returna a two element
+\perlnote{In wxPerl this method takes no arguments and return a two element
  array {\tt ( x, y )}}
 
 \membersection{wxDC::LogicalToDeviceX}\label{wxdclogicaltodevicex}
@@ -913,7 +913,7 @@ measurement used to convert logical units to device units. Note that
 in X, text drawing isn't handled consistently with the mapping mode; a
 font is always specified in point size. However, setting the {\it
 user scale} (see \helpref{wxDC::SetUserScale}{wxdcsetuserscale}) scales the text appropriately. In
-Windows, scaleable TrueType fonts are always used; in X, results depend
+Windows, scalable TrueType fonts are always used; in X, results depend
 on availability of fonts, but usually a reasonable match is found.
 
 Note that the coordinate origin should ideally be selectable, but for
@@ -998,7 +998,7 @@ Starts a document page (only relevant when outputting to a printer).
 \section{\class{wxDCClipper}}\label{wxdcclipper}
 
 This is a small helper class which sets the specified to its constructor
-clipping region and then automatically destroyes it in its destructor. Using
+clipping region and then automatically destroys it in its destructor. Using
 it ensures that unwanted clipping region is not left set on the DC.
 
 \wxheading{Derived from}
@@ -1028,5 +1028,5 @@ specified rectangle.
 
 \func{}{\destruct{wxDCClipper}}{\void}
 
-Destructor: destroyes the clipping region set in the constructor.
+Destructor: destroys the clipping region set in the constructor.
 

docs/latex/wx/dialog.tex

@@ -43,7 +43,7 @@ dialog to respond to system close events.
 \twocolitem{\windowstyle{wxSTAY\_ON\_TOP}}{The dialog stays on top of all other windows (Windows only).}
 \twocolitem{\windowstyle{wxNO\_3D}}{Under Windows, specifies that the child controls
 should not have 3D borders unless specified in the control.}
-\twocolitem{\windowstyle{wxDIALOG\_NO\_PARENT}}{By default, the dialogs crated
+\twocolitem{\windowstyle{wxDIALOG\_NO\_PARENT}}{By default, the dialogs created
 with {\tt NULL} parent window will be given the 
 \helpref{applications top level window}{wxappgettopwindow} as parent. Use this
 style to prevent this from happening and create a really orphan dialog (note
@@ -55,7 +55,7 @@ style and must be set by calling \helpref{SetExtraStyle}{wxwindowsetextrastyle}
 \end{twocollist}
 
 Under Unix or Linux, MWM (the Motif Window Manager) or other window managers
-reckognizing the MHM hints should be running for any of these styles to have an
+recognizing the MHM hints should be running for any of these styles to have an
 effect.
 
 See also \helpref{Generic window styles}{windowstyles}.

docs/latex/wx/dialup.tex

@@ -11,7 +11,7 @@
 
 \section{\class{wxDialUpManager}}\label{wxdialupmanager}
 
-This class encapsulates functions dealing with veryfying the connection status
+This class encapsulates functions dealing with verifying the connection status
 of the workstation (connected to the Internet via a direct connection,
 connected through a modem or not connected at all) and to establish this
 connection if possible/required (i.e. in the case of the modem).
@@ -91,7 +91,7 @@ their number (may be $0$).
 
 \func{bool}{Dial}{\param{const wxString\& }{nameOfISP = wxEmptyString}, \param{const wxString\& }{username = wxEmptyString}, \param{const wxString\& }{password = wxEmptyString}, \param{bool }{async = TRUE}}
 
-Dial the given ISP, use {\it username} and {\it password} to authentificate.
+Dial the given ISP, use {\it username} and {\it password} to authenticate.
 
 The parameters are only used under Windows currently, for Unix you should use 
 \helpref{SetConnectCommand}{wxdialupmanagersetconnectcommand} to customize this
@@ -175,7 +175,7 @@ algorithm may think about it.
 
 \func{bool}{EnableAutoCheckOnlineStatus}{\param{size\_t }{nSeconds = 60}}
 
-Enable automatical checks for the connection status and sending of 
+Enable automatic checks for the connection status and sending of 
 {\tt wxEVT\_DIALUP\_CONNECTED/wxEVT\_DIALUP\_DISCONNECTED} events. The interval
 parameter is only for Unix where we do the check manually and specifies how
 often should we repeat the check (each minute by default). Under Windows, the

docs/latex/wx/dir.tex

@@ -95,7 +95,7 @@ to test for errors.
 
 \func{}{\destruct{wxDir}}{\void}
 
-Destructor cleans up the associated ressources. It is not virtual and so this
+Destructor cleans up the associated resources. It is not virtual and so this
 class is not meant to be used polymorphically.
 
 \membersection{wxDir::Open}\label{wxdiropen}

docs/latex/wx/dirctrl.tex

@@ -113,7 +113,7 @@ Gets the currently-selected directory or filename.
 
 Gets selected filename path only (else empty string).
 
-This function doen't count a directory as a selection.
+This function doesn't count a directory as a selection.
 
 \membersection{wxGenericDirCtrl::GetFilter}\label{wxgenericdirctrlgetfilter}
 

docs/latex/wx/dllload.tex

@@ -74,7 +74,7 @@ No base class
 
 \wxheading{Data structures}
 
-This header defines a platfrom-dependent {\tt wxDllType} typedef which stores
+This header defines a platform-dependent {\tt wxDllType} typedef which stores
 a handle to a loaded DLLs on the given platform.
 
 \latexignore{\rtfignore{\wxheading{Members}}}
@@ -123,8 +123,8 @@ an error occured.
 
 This function loads a shared library into memory, with {\it libname} being the
 name of the library: it may be either the full name including path and
-(platform-dependent) extenesion, just the basename (no path and no extension)
+(platform-dependent) extension, just the basename (no path and no extension)
-or a basename with extentsion. In the last two cases, the library will be
+or a basename with extension. In the last two cases, the library will be
 searched in all standard locations.
 
 Returns a handle to the loaded DLL. Use {\it success} parameter to test if it

docs/latex/wx/dobjsmpl.tex

@@ -30,7 +30,7 @@ The objects supporting rendering the data must override
 \helpref{GetDataSize}{wxdataobjectsimplegetdatasize} and 
 \helpref{GetDataHere}{wxdataobjectsimplegetdatahere} while the objects which
 may be set must override \helpref{SetData}{wxdataobjectsimplesetdata}. Of
-course, the objects supporting both operations must override all threee
+course, the objects supporting both operations must override all three
 methods.
 
 \wxheading{Derived from}

docs/latex/wx/docmanag.tex

@@ -118,7 +118,7 @@ Adds the template to the document manager's template list.
 
 \func{bool}{CloseDocuments}{\param{bool }{force = TRUE}}
 
-Closes all currentled opened documents.
+Closes all currently opened documents.
 
 \membersection{wxDocManager::CreateDocument}
 

docs/latex/wx/encconv.tex

@@ -36,7 +36,7 @@ Constructor.
 
 \func{bool}{Init}{\param{wxFontEncoding }{input\_enc}, \param{wxFontEncoding }{output\_enc}, \param{int }{method = wxCONVERT\_STRICT}}
 
-Initialize convertion. Both output or input encoding may
+Initialize conversion. Both output or input encoding may
 be wxFONTENCODING\_UNICODE, but only if wxUSE\_ENCODING is set to 1.
 All subsequent calls to \helpref{Convert()}{wxencodingconverterconvert} 
 will interpret its argument
@@ -113,7 +113,7 @@ under given platform. Supported platforms:
 \item wxPLATFORM\_CURRENT
 \end{itemize}
 
-wxPLATFORM\_CURRENT means the plaform this binary was compiled for.
+wxPLATFORM\_CURRENT means the platform this binary was compiled for.
 
 Examples:
 

docs/latex/wx/fdrepdlg.tex

@@ -98,7 +98,7 @@ dialog and calling them has no effect later.
 
 \wxheading{Data structures}
 
-Flages used by 
+Flags used by 
 \helpref{wxFindReplaceData::GetFlags()}{wxfindreplacedatagetflags} and
 \helpref{wxFindDialogEvent::GetFlags()}{wxfinddialogeventgetflags}:
 

docs/latex/wx/ffile.tex

@@ -160,7 +160,7 @@ The number of bytes read.
 
 \func{bool}{Seek}{\param{long }{ofs}, \param{wxSeekMode }{mode = wxFromStart}}
 
-Seeks to the specified position and returs TRUE on success.
+Seeks to the specified position and returns TRUE on success.
 
 \wxheading{Parameters}
 

docs/latex/wx/fildatob.tex

@@ -8,7 +8,7 @@ under Unix which makes it possible to receive files from them using this
 class.
 
 {\bf Warning:} Under all non-Windows platforms this class is currently
-"input-only", i.e. you can receieve the files from another application, but
+"input-only", i.e. you can receive the files from another application, but
 copying (or dragging) file(s) from a wxWindows application is not currently
 supported.
 

docs/latex/wx/filename.tex

@@ -71,7 +71,7 @@ enum wxPathNormalize
 
 wxFileName currently supports the file names in the Unix, DOS/Windows, Mac OS
 and VMS formats. Although these formats are quite different, wxFileName tries
-to treat them all in the sam generic way. It supposes that all file names
+to treat them all in the same generic way. It supposes that all file names
 consist of the following parts: the volume (also known as drive under Windows
 or device under VMS), the path which is a sequence of directory names separated
 by the \helpref{path separators}{wxfilenamegetpathseparators} and the full
@@ -169,7 +169,7 @@ Copy constructor.
 \func{}{wxFileName}{\param{const wxString\& }{fullpath}, \param{wxPathFormat }{format = wxPATH\_NATIVE}}
 
 From a full filename: if it terminates with a '/', a directory path
-is contructed (the name will be empty), otherwise a file name and
+is constructed (the name will be empty), otherwise a file name and
 extension are extracted from it
 
 \func{}{wxFileName}{\param{const wxString\& }{path}, \param{const wxString\& }{name}, \param{wxPathFormat }{format = wxPATH\_NATIVE}}

docs/latex/wx/filesys.tex

@@ -95,7 +95,7 @@ Returns actual path (set by \helpref{ChangePathTo}{wxfilesystemchangepathto}).
 \func{wxString}{FindFirst}{\param{const wxString\& }{wildcard}, \param{int }{flags = 0}}
 
 Works like \helpref{wxFindFirstFile}{wxfindfirstfile}. Returns name of the first
-filename (withing filesystem's current path) that matches {\it wildcard}. {\it flags} may be one of
+filename (within filesystem's current path) that matches {\it wildcard}. {\it flags} may be one of
 wxFILE (only files), wxDIR (only directories) or 0 (both).
 
 \membersection{wxFileSystem::FindNext}\label{wxfilesystemfindnext}

docs/latex/wx/filesysh.tex

@@ -116,7 +116,7 @@ Example : GetRightLocation("file:myzipfile.zip\#zip:index.htm") == "index.htm"
 \func{virtual wxString}{FindFirst}{\param{const wxString\& }{wildcard}, \param{int }{flags = 0}}
 
 Works like \helpref{wxFindFirstFile}{wxfindfirstfile}. Returns name of the first
-filename (withing filesystem's current path) that matches {\it wildcard}. {\it flags} may be one of
+filename (within filesystem's current path) that matches {\it wildcard}. {\it flags} may be one of
 wxFILE (only files), wxDIR (only directories) or 0 (both).
 
 This method is only called if \helpref{CanOpen}{wxfilesystemhandlercanopen} returns TRUE.

docs/latex/wx/filetype.tex

@@ -56,7 +56,7 @@ These parameters may be useful to the program used to open, edit, view or print
 the message, so, for example, an e-mail client program will have to pass them to
 this program. Because wxFileType itself can not know about these parameters,
 it uses MessageParameters class to query them. The default implementation only
-requiers the caller to provide the file name (always used by the program to be
+requires the caller to provide the file name (always used by the program to be
 called - it must know which file to open) and the MIME type and supposes that
 there are no other parameters. If you wish to supply additional parameters, you
 must derive your own class from MessageParameters and override GetParamValue()
@@ -191,7 +191,7 @@ retrieved from \helpref{MessageParameters}{wxfiletypemessageparameters} class.
 
 \func{static wxString}{ExpandCommand}{\param{const wxString\&}{ command}, \param{MessageParameters\&}{ params}}
 
-This function is primarly intended for GetOpenCommand and GetPrintCommand
+This function is primarily intended for GetOpenCommand and GetPrintCommand
 usage but may be also used by the application directly if, for example, you want
 to use some non default command to open the file.
 
@@ -199,7 +199,7 @@ The function replaces all occurrences of
 
 \twocolwidtha{7cm}
 \begin{twocollist}\itemsep=0pt
-\twocolitem{format specificator}{with}
+\twocolitem{format specification}{with}
 \twocolitem{\%s}{the full file name}
 \twocolitem{\%t}{the MIME type}
 \twocolitem{\%\{param\}}{the value of the parameter {\it param}}

docs/latex/wx/fltinstr.tex

@@ -4,7 +4,7 @@
 \section{\class{wxFilterInputStream}}\label{wxfilterinputstream}
 
 A filter stream has the capability of a normal stream but it can be placed on top
-of another stream. So, for example, it can uncompress or uncrypt the data which are read
+of another stream. So, for example, it can uncompress or decrypt the data which are read
 from another stream and pass it to the requester.
 
 \wxheading{Derived from}

docs/latex/wx/font.tex

@@ -144,7 +144,7 @@ is the encoding set by calls to
 say, KOI8 to create all fonts by default with KOI8 encoding. Initially, the
 default application encoding is the same as default system encoding.}
 \twocolitem{{\bf wxFONTENCODING\_ISO8859\_1...15}}{ISO8859 encodings.}
-\twocolitem{{\bf wxFONTENCODING\_KOI8}}{The standard russian encoding for Internet.}
+\twocolitem{{\bf wxFONTENCODING\_KOI8}}{The standard Russian encoding for Internet.}
 \twocolitem{{\bf wxFONTENCODING\_CP1250...1252}}{Windows encodings similar to ISO8859 (but not identical).}
 \end{twocollist}
 If the specified encoding isn't available, no font is created.
@@ -153,7 +153,7 @@ If the specified encoding isn't available, no font is created.
 \wxheading{Remarks}
 
 If the desired font does not exist, the closest match will be chosen.
-Under Windows, only scaleable TrueType fonts are used.
+Under Windows, only scalable TrueType fonts are used.
 
 See also \helpref{wxDC::SetFont}{wxdcsetfont}, \helpref{wxDC::DrawText}{wxdcdrawtext}
 and \helpref{wxDC::GetTextExtent}{wxdcgettextextent}.

docs/latex/wx/fontdlg.tex

@@ -140,7 +140,7 @@ The default value is FALSE.
 
 \func{void}{operator $=$}{\param{const wxFontData\&}{ data}}
 
-Assingment operator for the font data.
+Assignment operator for the font data.
 
 \section{\class{wxFontDialog}}\label{wxfontdialog}
 

docs/latex/wx/frame.tex

@@ -287,7 +287,7 @@ Iconizes or restores the frame.
 
 \wxheading{Parameters}
 
-\docparam{izonize}{If TRUE, iconizes the frame; if FALSE, shows and restores it.}
+\docparam{iconize}{If TRUE, iconizes the frame; if FALSE, shows and restores it.}
 
 \wxheading{See also}
 

docs/latex/wx/fs.tex

@@ -65,7 +65,7 @@ Include file is <wx/fs\_zip.h>. URL is in form "archive.zip\#zip:filename".}
 \twocolitem{{\bf wxMemoryFSHandler}}{This handler allows you to access 
 data stored in memory (such as bitmaps) as if they were regular files.
 See \helpref{wxMemoryFSHandler documentation}{wxmemoryfshandler} for details.
-Include file is <wx/fs\_mem.h>. UURL is prefixed with memory:, e.g. 
+Include file is <wx/fs\_mem.h>. URL is prefixed with memory:, e.g. 
 "memory:myfile.htm"}
 \end{twocollist}
 

docs/latex/wx/fsfile.tex

@@ -9,8 +9,8 @@ This class represents a single file opened by \helpref{wxFileSystem}{wxfilesyste
 It provides more information than wxWindow's input stream 
 (stream, filename, mime type, anchor).
 
-{\bf Note:} Any pointer returned by wxFSFile's member is valid
+{\bf Note:} Any pointer returned by a method of wxFSFile is valid
-only as long as wxFSFile object exists. For example a call to GetStream()
+only as long as the wxFSFile object exists. For example a call to GetStream()
 doesn't {\it create} the stream but only returns the pointer to it. In
 other words after 10 calls to GetStream() you will obtain ten identical
 pointers.

docs/latex/wx/function.tex

@@ -466,7 +466,7 @@ calling \helpref{wxEnableTopLevelWindows(FALSE)}{wxenabletoplevelwindows}.
 
 For asynchronous execution, however, the return value is the process id and
 zero value indicates that the command could not be executed. As an added
-complication, the return value of $-1$ in this case indicattes that we didn't
+complication, the return value of $-1$ in this case indicates that we didn't
 launch a new process, but connected to the running one (this can only happen in
 case of using DDE under Windows for command execution). In particular, in this,
 and only this, case the calling code will not get the notification about
@@ -532,7 +532,7 @@ application. See \helpref{wxCloseEvent}{wxcloseevent} and \helpref{wxApp}{wxapp}
 \func{int}{wxKill}{\param{long}{ pid}, \param{int}{ sig = wxSIGTERM}, \param{wxKillError }{*rc = NULL}}
 
 Equivalent to the Unix kill function: send the given signal {\it sig} to the
-process with PID {\it pid}. The valud signal values are
+process with PID {\it pid}. The valid signal values are
 
 \begin{verbatim}
 enum wxSignal
@@ -814,7 +814,7 @@ TRUE if successful.
 
 Copies {\it file1} to {\it file2}, returning TRUE if successful. If
 {\it overwrite} parameter is TRUE (default), the destination file is overwritten
-if it exists, but if {\it overwrite} is FALSE, the functions failes in this
+if it exists, but if {\it overwrite} is FALSE, the functions fails in this
 case.
 
 \membersection{::wxGetCwd}\label{wxgetcwd}
@@ -2460,7 +2460,7 @@ data in big-endian format.
 
 wxWindows uses its own RTTI ("run-time type identification") system which
 predates the current standard C++ RTTI and so is kept for backwards
-compatribility reasons but also because it allows some things which the
+compatibility reasons but also because it allows some things which the
 standard RTTI doesn't directly support (such as creating a class from its
 name).
 

docs/latex/wx/grid.tex

@@ -478,7 +478,7 @@ Returns the current height of the column labels.
 
 \func{wxString}{GetColLabelValue}{\param{int }{col}}
 
-Returns the specifed column label. The default grid table class provides column labels of
+Returns the specified column label. The default grid table class provides column labels of
 the form A,B...Z,AA,AB...ZZ,AAA... If you are using a custom grid table you can override 
 \helpref{wxGridTableBase::GetColLabelValue}{wxgridtablebasegetcollabelvalue} to provide
 your own labels. 
@@ -581,7 +581,7 @@ Returns the colour used for grid lines.
 
 \func{bool}{GridLinesEnabled}{\void}
 
-Returnes TRUE if drawing of grid lines is turned on, FALSE otherwise.
+Returns TRUE if drawing of grid lines is turned on, FALSE otherwise.
 
 \membersection{wxGrid::GetLabelBackgroundColour}\label{wxgridgetlabelbackgroundcolour}
 
@@ -636,7 +636,7 @@ Returns the current width of the row labels.
 
 \func{wxString}{GetRowLabelValue}{\param{int }{row}}
 
-Returns the specifed row label. The default grid table class provides numeric row labels.
+Returns the specified row label. The default grid table class provides numeric row labels.
 If you are using a custom grid table you can override 
 \helpref{wxGridTableBase::GetRowLabelValue}{wxgridtablebasegetcollabelvalue} to provide
 your own labels. 
@@ -897,7 +897,7 @@ deselected; if TRUE the row will be added to the existing selection.
 
 \func{void}{SetCellAlignment}{\param{int }{align}}
 
-Sets the horizontal and vertial alignment for grid cell text at the specified location.
+Sets the horizontal and vertical alignment for grid cell text at the specified location.
 
 Horizontal alignment should be one of wxALIGN\_LEFT, wxALIGN\_CENTRE or wxALIGN\_RIGHT. \\
 Vertical alignment should be one of wxALIGN\_TOP, wxALIGN\_CENTRE or wxALIGN\_BOTTOM.
@@ -1046,7 +1046,7 @@ The memory requirements for this could become prohibitive if your grid is very l
 
 \func{void}{SetDefaultCellAlignment}{\param{int }{horiz}, \param{int }{vert}}
 
-Sets the default horizontal and vertial alignment for grid cell text.
+Sets the default horizontal and vertical alignment for grid cell text.
 
 Horizontal alignment should be one of wxALIGN\_LEFT, wxALIGN\_CENTRE or wxALIGN\_RIGHT.
 

docs/latex/wx/gridevt.tex

@@ -125,7 +125,7 @@ Position in pixels at which the event occurred.
 
 \func{int}{GetRow}{\void}
 
-Row at which the evnet occurred.
+Row at which the event occurred.
 
 \membersection{wxGridEvent::MetaDown}\label{wxgrideventmetadown}
 
@@ -207,7 +207,7 @@ Bottom row of the rectangular area that was (de)selected.
 
 \func{int}{GetLeftCol}{\void}
 
-Left column of the rectangualr area that was (de)selected.
+Left column of the rectangular area that was (de)selected.
 
 \membersection{wxGridRangeSelectEvent::GetRightCol}\label{wxgridrangeselecteventgetrightcol}
 
@@ -219,7 +219,7 @@ Right column of the rectangular area that was (de)selected.
 
 \func{wxGridCellCoords}{GetTopLeftCoords}{\void}
 
-Top left corner of the rectangular area that was (de)delected.
+Top left corner of the rectangular area that was (de)selected.
 
 \membersection{wxGridRangeSelectEvent::GetTopRow}\label{wxgridrangeselecteventgettoprow}
 

docs/latex/wx/hashmap.tex

@@ -27,7 +27,7 @@ whose interface is a subset of the interface of STL containers.
     h2["Bill"] = "ABC";
     wxString tmp = h2["Bill"];
     // since element with key "Joe" is not present, this will return
-    // the devault value, that is an empty string in the case of wxString
+    // the default value, that is an empty string in the case of wxString
     MyClass tmp2 = h2["Joe"];
 
     // iterate over all the elements in the class

docs/latex/wx/helpinst.tex

@@ -24,7 +24,7 @@ compiled into wxWindows; otherwise wxExtHelpController is used (for invoking an
 browser).
 \end{itemize}
 
-The remaining help controller classess need to be named
+The remaining help controller classes need to be named
 explicitly by an application that wishes to make use of them.
 
 There are currently the following help controller classes defined:
@@ -33,7 +33,7 @@ There are currently the following help controller classes defined:
 \item wxWinHelpController, for controlling Windows Help.
 \item wxCHMHelpController, for controlling MS HTML Help. To use this, you need to set wxUSE\_MS\_HTML\_HELP
 to 1 in setup.h and have htmlhelp.h header from Microsoft's HTML Help kit (you don't need
-VC++ specific htmlhelp.lib because wxWindows loads neccessary DLL at runtime and so it
+VC++ specific htmlhelp.lib because wxWindows loads necessary DLL at runtime and so it
 works with all compilers).
 \item wxBestHelpController, for controlling MS HTML Help or, if Microsoft's runtime is
 not available, \helpref{wxHtmlHelpController}{wxhtmlhelpcontroller}. You need to provide

docs/latex/wx/htcell.tex

@@ -237,7 +237,7 @@ Sets unique cell identifier. Default value is no identifier, i.e. empty string.
 
 \func{void}{SetLink}{\param{const wxHtmlLinkInfo\& }{link}}
 
-Sets the hypertext link asocciated with this cell. (Default value
+Sets the hypertext link associated with this cell. (Default value
 is \helpref{wxHtmlLinkInfo}{wxhtmllinkinfo}("", "") (no link))
 
 \membersection{wxHtmlCell::SetNext}\label{wxhtmlcellsetnext}

docs/latex/wx/htdcrend.tex

@@ -37,7 +37,7 @@ inch wide on typical printer. With pixel\_scale = 3.0 it would be 3 inches.)
 
 \wxheading{Parameters}
 
-\docparam{maxwidth}{width of the area (on this DC) that is equivalent to screen's width, 
+\docparam{maxwidth}{width of the area (on this DC) that is equivalent to the screen's width, 
 in pixels (you should set it to page width minus margins). 
 
 {\bf Note:} In the current implementation

docs/latex/wx/hthelpct.tex

@@ -91,7 +91,7 @@ top-level directory. This ZIP archive must have .zip or .htb extension
 (the latter stands for "HTML book"). In other words, {\tt AddBook("help.zip")} is possible and, in fact,
 recommended way.
 
-If {\it show\_wait\_msg} is TRUE then a decorationless window with progress message is displayed.
+If {\it show\_wait\_msg} is TRUE then a decoration-less window with progress message is displayed.
 
 \membersection{wxHtmlHelpController::CreateHelpFrame}\label{wxhtmlhelpcontrollercreatehelpframe}
 

docs/latex/wx/htlnkinf.tex

@@ -1,6 +1,6 @@
 \section{\class{wxHtmlLinkInfo}}\label{wxhtmllinkinfo}
 
-This class stores all neccessary information about hypertext
+This class stores all necessary information about hypertext
 links (as represented by {\tt <A>} tag in HTML documents). In 
 current implementation it stores URL and target frame name. 
 {\it Note that frames are not currently supported by wxHTML!}

docs/latex/wx/htmlcell.tex

@@ -37,7 +37,7 @@ a container {\it within an already opened container}. This new container is a
 {\it sub-container} of the old one. (If you want to create a new container with
 the same depth level you can call {\tt CloseContainer(); OpenContainer();}.)
 
-Use \helpref{CloseContaier}{wxhtmlwinparserclosecontainer} to close the 
+Use \helpref{CloseContainer}{wxhtmlwinparserclosecontainer} to close the 
 container. This doesn't create a new container with same depth level but
 it returns "control" to the parent container.
 

docs/latex/wx/htparser.tex

@@ -7,7 +7,7 @@
 
 This class handles the {\bf generic} parsing of HTML document: it scans
 the document and divide it into blocks of tags (where one block
-consists of begining and ending tag and of text between these
+consists of beginning and ending tag and of text between these
 two tags).
 
 It is independent from wxHtmlWindow and can be used as stand-alone parser
@@ -15,7 +15,7 @@ It is independent from wxHtmlWindow and can be used as stand-alone parser
 see InetGet sample for example).
 
 It uses system of tag handlers to parse the HTML document. Tag handlers
-are not staticaly shared by all instances but are created for each
+are not statically shared by all instances but are created for each
 wxHtmlParser instance. The reason is that the handler may contain
 document-specific temporary data used during parsing (e.g. complicated
 structures like tables).
@@ -48,7 +48,7 @@ Constructor.
 
 \func{void}{AddTag}{\param{const wxHtmlTag\& }{tag}}
 
-This may (and may not) be overwriten in derived class.
+This may (and may not) be overwritten in derived class.
 
 This method is called each time new tag is about to be added. 
 {\it tag} contains information about the tag. (See \helpref{wxHtmlTag}{wxhtmltag}
@@ -76,7 +76,7 @@ All handlers are deleted on object deletion.
 
 \func{virtual void}{AddWord}{\param{const char* }{txt}}
 
-Must be overwriten in derived class.
+Must be overwritten in derived class.
 
 This method is called by \helpref{DoParsing}{wxhtmlparserdoparsing}
 each time a part of text is parsed. {\it txt} is NOT only one word, it is
@@ -140,7 +140,7 @@ in derived class)
 
 Opens given URL and returns {\tt wxFSFile} object that can be used to read data
 from it. This method may return NULL in one of two cases: either the URL doesn't
-point to any valid resource or the URL is blocked by overriden implementation
+point to any valid resource or the URL is blocked by overridden implementation
 of {\it OpenURL} in derived class.
 
 \wxheading{Parameters}

docs/latex/wx/htprint.tex

@@ -95,6 +95,6 @@ file). It is used to determine path for loading images, for example.}
 
 \func{void}{SetMargins}{\param{float }{top = 25.2}, \param{float }{bottom = 25.2}, \param{float }{left = 25.2}, \param{float }{right = 25.2}, \param{float }{spaces = 5}}
 
-Sets margins in milimeters. Defaults to 1 inch for margins and 0.5cm for space
+Sets margins in millimeters. Defaults to 1 inch for margins and 0.5cm for space
 between text and header and/or footer
 

docs/latex/wx/httag.tex

@@ -45,7 +45,7 @@ ending tag.
 See explanation (returned position is marked with `|'):
 
 \begin{verbatim}
-bla bla bla <MYTAG> bla bla intenal text</MYTAG> bla bla
+bla bla bla <MYTAG> bla bla internal text</MYTAG> bla bla
                    |
 \end{verbatim}
 
@@ -59,7 +59,7 @@ ending tag.
 See explanation (returned position is marked with `|'):
 
 \begin{verbatim}
-bla bla bla <MYTAG> bla bla intenal text</MYTAG> bla bla
+bla bla bla <MYTAG> bla bla internal text</MYTAG> bla bla
                                         |
 \end{verbatim}
 
@@ -73,7 +73,7 @@ ending tag.
 See explanation (returned position is marked with `|'):
 
 \begin{verbatim}
-bla bla bla <MYTAG> bla bla intenal text</MYTAG> bla bla
+bla bla bla <MYTAG> bla bla internal text</MYTAG> bla bla
                                                |
 \end{verbatim}
 
@@ -158,7 +158,7 @@ is ending itself) of course doesn't have ending tag.
 
 \constfunc{bool}{HasParam}{\param{const wxString\& }{par}}
 
-Returns TRUE if the tag has parameter of the given name. 
+Returns TRUE if the tag has a parameter of the given name. 
 Example : {\tt <FONT SIZE=+2 COLOR="\#FF00FF">} has two parameters named
 "SIZE" and "COLOR".
 
@@ -177,17 +177,18 @@ Returns TRUE if this tag is ending one.
 
 \constfunc{wxString}{ScanParam}{\param{const wxString\& }{par}, \param{const wxChar *}{format}, \param{void *}{value}}
 
-This method scans given parameter. Usage is exactly the same as sscanf's 
+This method scans the given parameter. Usage is exactly the same as sscanf's 
-usage except that you don't pass string but parameter name as the first parameter
+usage except that you don't pass a string but a parameter name as the first
-and that you can only retrieve one value (i.e. you can use only one "\%" element
+argument
+and you can only retrieve one value (i.e. you can use only one "\%" element
 in {\it format}).
 
 
 \wxheading{Parameters}
 
-\docparam{par}{The name of tag you want to query}
+\docparam{par}{The name of the tag you want to query}
 
 \docparam{format}{scanf()-like format string.}
 
-\docparam{value}{pointer to a variable to store value in }
+\docparam{value}{pointer to a variable to store the value in }
 

docs/latex/wx/httaghnd.tex

@@ -45,7 +45,7 @@ are delimited by ','. Example : {\tt "I,B,FONT,P" }
 \func{virtual bool}{HandleTag}{\param{const wxHtmlTag\& }{tag}}
 
 This is the core method of each handler. It is called each time
-one of supported tags is detected. {\it tag} contains all neccessary
+one of supported tags is detected. {\it tag} contains all necessary
 info (see \helpref{wxHtmlTag}{wxhtmltag} for details).
 
 \wxheading{Return value}
@@ -66,14 +66,14 @@ bool MyHandler::HandleTag(const wxHtmlTag& tag)
 }
 \end{verbatim}
 
-You shouldn't call ParseInner if the tag is not paired with ending one.
+You shouldn't call ParseInner if the tag is not paired with an ending one.
 
 \membersection{wxHtmlTagHandler::ParseInner}\label{wxhtmltaghandlerparseinner}
 
 \func{void}{ParseInner}{\param{const wxHtmlTag\& }{tag}}
 
 This method calls parser's \helpref{DoParsing}{wxhtmlparserdoparsing} method
-for the string between this tag and paired ending tag:
+for the string between this tag and the paired ending tag:
 
 \begin{verbatim}
 ...<A HREF="x.htm">Hello, world!</A>...

docs/latex/wx/httagmod.tex

@@ -5,7 +5,7 @@
 \section{\class{wxHtmlTagsModule}}\label{wxhtmltagsmodule}
 
 This class provides easy way of filling wxHtmlWinParser's table of
-tag handlers. It is used almost exclusively together with set of
+tag handlers. It is used almost exclusively together with the set of
 \helpref{TAGS\_MODULE\_* macros}{handlers}
 
 \wxheading{Derived from}
@@ -28,14 +28,14 @@ tag handlers. It is used almost exclusively together with set of
 
 \func{virtual void}{FillHandlersTable}{\param{wxHtmlWinParser }{*parser}}
 
-You must override this method. In most common case it is body consists
+You must override this method. In most common case its body consists
-only of lines of following type:
+only of lines of the following type:
 
 \begin{verbatim}
 parser -> AddTagHandler(new MyHandler);
 \end{verbatim}
 
-I recommend using {\bf TAGS\_MODULE\_*} macros.
+I recommend using the {\bf TAGS\_MODULE\_*} macros.
 
 \wxheading{Paremeters}
 

docs/latex/wx/http.tex

@@ -30,7 +30,7 @@ You will be notified when the EOF is reached by an error.
 \wxheading{Note}
 
 You can know the size of the file you are getting using \helpref{wxStreamBase::GetSize()}{wxstreambasegetsize}.
-But there is a limitation: as HTTP servers aren't obliged to pass the size ofi
+But there is a limitation: as HTTP servers aren't obliged to pass the size of
 the file, in some case, you will be returned 0xfffffff by GetSize(). In these
 cases, you should use the value returned by \helpref{wxInputStream::LastRead()}{wxinputstreamlastread}:
 this value will be 0 when the stream is finished.

docs/latex/wx/htwindow.tex

@@ -285,7 +285,7 @@ This function sets font sizes and faces.
 \wxheading{Parameters}
 
 \docparam{normal\_face}{This is face name for normal (i.e. non-fixed) font. 
-It can be either empty string (then the default face is choosen) or
+It can be either empty string (then the default face is chosen) or
 platform-specific face name. Examples are "helvetica" under Unix or
 "Times New Roman" under Windows.}
 
@@ -309,7 +309,7 @@ Under Windows:
     SetFonts("", "", {7, 8, 10, 12, 16, 22, 30});
 \end{verbatim}
 
-Athough it seems different the fact is that the fonts are of approximately
+Although it seems different the fact is that the fonts are of approximately
 same size under both platforms (due to wxMSW / wxGTK inconsistency)
 
 \membersection{wxHtmlWindow::SetPage}\label{wxhtmlwindowsetpage}

docs/latex/wx/htwinprs.tex

@@ -35,7 +35,7 @@ The product of parsing is a wxHtmlCell (resp. wxHtmlContainer) object.
 \func{}{wxHtmlWinParser}{\param{wxHtmlWindow }{*wnd}}
 
 Constructor. Don't use the default one, use constructor with
-{\it wnd} paremeter ({\it wnd} is pointer to associated \helpref{wxHtmlWindow}{wxhtmlwindow})
+{\it wnd} parameter ({\it wnd} is pointer to associated \helpref{wxHtmlWindow}{wxhtmlwindow})
 
 \membersection{wxHtmlWinParser::AddModule}\label{wxhtmlwinparseraddmodule}
 
@@ -98,7 +98,7 @@ know the height of the current font, call {\tt GetDC -> GetCharWidth()}
 
 \constfunc{wxHtmlContainerCell*}{GetContainer}{\void}
 
-Returns pointer to the currectly opened container (see \helpref{Overview}{cells}).
+Returns pointer to the currently opened container (see \helpref{Overview}{cells}).
 Common use:
 
 \begin{verbatim}

docs/latex/wx/hworld.tex

@@ -1,7 +1,7 @@
 \section{wxWindows Hello World sample}\label{helloworld}
 
 As many people have requested a mini-sample to be published here
-so that some quick judgments concerning syntax
+so that some quick judgment concerning syntax
 and basic principles can be made, you can now look at wxWindows'
 "Hello World":
 

docs/latex/wx/image.tex

@@ -18,7 +18,7 @@ creation of a \helpref{wxMask}{wxmask} object associated to the bitmap object.
 \wxheading{Available image handlers}
 
 The following image handlers are available. {\bf wxBMPHandler} is always
-installed by default. To use other image formats, install the appropiate
+installed by default. To use other image formats, install the appropriate
 handler with \helpref{wxImage::AddHandler}{wximageaddhandler} or 
 \helpref{wxInitAllImageHandlers}{wxinitallimagehandlers}.
 
@@ -349,7 +349,7 @@ Returns the blue intensity at the given coordinate.
 
 Returns the image data as an array. This is most often used when doing
 direct image manipulation. The return value points to an array of
-chararcters in RGBGBRGB... format.
+characters in RGBGBRGB... format.
 
 \membersection{wxImage::GetGreen}\label{wximagegetgreen}
 

docs/latex/wx/imaglist.tex

@@ -118,7 +118,7 @@ Draws a specified image onto a device context.
 \twocolitem{{\bf wxIMAGELIST\_DRAW\_NORMAL}}{Draw the image normally.}
 \twocolitem{{\bf wxIMAGELIST\_DRAW\_TRANSPARENT}}{Draw the image with transparency.}
 \twocolitem{{\bf wxIMAGELIST\_DRAW\_SELECTED}}{Draw the image in selected state.}
-\twocolitem{{\bf wxIMAGELIST\_DRAW\_FOCUSED}}{Draw the image in a focussed state.}
+\twocolitem{{\bf wxIMAGELIST\_DRAW\_FOCUSED}}{Draw the image in a focused state.}
 \end{twocollist}
 }
 

docs/latex/wx/inputstr.tex

@@ -96,7 +96,7 @@ Returns the current stream position.
 \func{size\_t}{Ungetch}{\param{const char*}{ buffer}, \param{size\_t}{ size}}
 
 This function is only useful in {\it read} mode. It is the manager of the "Write-Back"
-buffer. This buffer acts like a temporary buffer where datas which has to be
+buffer. This buffer acts like a temporary buffer where data which has to be
 read during the next read IO call are put. This is useful when you get a big
 block of data which you didn't want to read: you can replace them at the top
 of the input queue by this way.

docs/latex/wx/keyevent.tex

@@ -49,7 +49,7 @@ simpler.
 {\bf Note for Windows programmers:} The key and char events in wxWindows are
 similar to but slightly different from Windows {\tt WM\_KEYDOWN} and
 {\tt WM\_CHAR} events. In particular, Alt-x combination will generate a char
-event in wxWindows (unless it is used as an acclerator).
+event in wxWindows (unless it is used as an accelerator).
 
 {\bf Tip:} be sure to call {\tt event.Skip()} for events that you don't process in
 key event function, otherwise menu shortcuts may cease to work under Windows.

docs/latex/wx/layalgor.tex

@@ -40,7 +40,7 @@ bottom of the remaining client area. This scheme implies that order of window cr
 Say you wish to have an extra toolbar at the top of the frame, a project window to the left of
 the MDI client window, and an output window above the status bar. You should therefore create
 the windows in this order: toolbar, output window, project window. This ensures that the toolbar and
-output window take up space at the top and bottom, and then the remaining height inbetween is used for
+output window take up space at the top and bottom, and then the remaining height in-between is used for
 the project window.
 
 wxLayoutAlgorithm is quite independent of the way in which

docs/latex/wx/list.tex

@@ -38,7 +38,7 @@ macros):
 
     ...
 
-    // the only requirment for the rest is to be AFTER the full declaration of
+    // the only requirement for the rest is to be AFTER the full declaration of
     // MyListElement (for WX_DECLARE_LIST forward declaration is enough), but
     // usually it will be found in the source file and not in the header
 

docs/latex/wx/listbox.tex

@@ -52,7 +52,7 @@ See also \helpref{window styles overview}{windowstyles}.
 \twocolitem{{\bf EVT\_LISTBOX(id, func)}}{Process a wxEVT\_COMMAND\_LISTBOX\_SELECTED event,
 when an item on the list is selected.}
 \twocolitem{{\bf EVT\_LISTBOX\_DCLICK(id, func)}}{Process a wxEVT\_COMMAND\_LISTBOX\_DOUBLECLICKED event,
-when the listbox is doubleclicked.}
+when the listbox is double-clicked.}
 \end{twocollist}
 
 \wxheading{See also}
@@ -251,7 +251,7 @@ Use this with a multiple selection listbox.
 \pythonnote{The wxPython version of this method takes no parameters
 and returns a tuple of the selected items.}
 
-\perlnote{In wxPerl this method takes no parameters and returna the
+\perlnote{In wxPerl this method takes no parameters and return the
 selected items as a list.}
 
 \membersection{wxListBox::GetString}\label{wxlistboxgetstring}

docs/latex/wx/listctrl.tex

@@ -353,7 +353,7 @@ Returns the rectangle representing the item's size and position, in client coord
 ID and code and returns the wxRect.}
 
 \perlnote{In wxPerl this method takes only the {\bf item} parameter and
-retutrns a Wx::Rect ( or undef ).}
+returns a Wx::Rect ( or undef ).}
 
 \membersection{wxListCtrl::GetItemSpacing}\label{wxlistctrlgetitemspacing}
 
@@ -381,7 +381,7 @@ Gets the item text for this item.
 
 \constfunc{long}{GetNextItem}{\param{long }{item}, \param{int }{geometry = wxLIST\_NEXT\_ALL}, \param{int }{state = wxLIST\_STATE\_DONTCARE}}
 
-Searches for an item with the given goemetry or state, starting from
+Searches for an item with the given geometry or state, starting from
 {\it item} but excluding the {\it item} itself. If {\it item} is -1,
 the first item that matches the specified flags will be returned.
 
@@ -722,7 +722,7 @@ string or image at a given location.}
 This method can only be used with virtual list controls. It is used to indicate
 to the control the number of items it contains. After calling it, the main
 program should be ready to handle calls to various item callbacks (such as
-\helpref{OnGetItemText}{wxlistctrlongetitemtext}) for all vitems in the range
+\helpref{OnGetItemText}{wxlistctrlongetitemtext}) for all items in the range
 from $0$ to {\it count}.
 
 \membersection{wxListCtrl::SetItemData}\label{wxlistctrlsetitemdata}

docs/latex/wx/locale.tex

@@ -370,7 +370,7 @@ This only applies to subsequent invocations of AddCatalog()!
 \func{static void}{AddLanguage}{\param{const wxLanguageInfo\& }{info}}
 
 Adds custom, user-defined language to the database of known languages. This
-database is used in conjuction with the first form of 
+database is used in conjunction with the first form of 
 \helpref{Init}{wxlocaleinit}. 
 
 wxLanguageInfo is defined as follows:

docs/latex/wx/log.tex

@@ -136,7 +136,7 @@ documentation.
 
 Finally, the {\it wxLog::DoLog()} function automatically prepends a time stamp
 to all the messages. The format of the time stamp may be changed: it can be
-any string with \% specificators fully described in the documentation of the
+any string with \% specifications fully described in the documentation of the
 standard {\it strftime()} function. For example, the default format is
 "[\%d/\%b/\%y \%H:\%M:\%S] " which gives something like "[17/Sep/98 22:10:16] "
 (without quotes) for the current date. Setting an empty string as the time
@@ -292,7 +292,7 @@ user). (Almost) for internal use only.
 
 \func{static void}{SetVerbose}{\param{bool }{ verbose = TRUE}}
 
-Activates or desactivates verbose mode in which the verbose messages are
+Activates or deactivates verbose mode in which the verbose messages are
 logged as the normal ones instead of being silently dropped.
 
 \membersection{wxLog::GetVerbose}\label{wxloggetverbose}

docs/latex/wx/longlong.tex

@@ -18,7 +18,7 @@ the other cases which ensures that it is the most efficient solution for
 working with 64 bit integers independently of the architecture.
 
 wxLongLong defines all usual arithmetic operations such as addition,
-substraction, bitwise shifts and logical operations as well as multiplication
+subtraction, bitwise shifts and logical operations as well as multiplication
 and division (not yet for the machines without native {\it long long}). It
 also has operators for implicit construction from and conversion to the native 
 {\it long long} type if it exists and {\it long}.
@@ -86,13 +86,13 @@ platform-dependent way.  Not in wxULongLong.
 
 \constfunc{long}{GetHi}{\void}
 
-Returnes the high 32 bits of 64 bit integer.
+Returns the high 32 bits of 64 bit integer.
 
 \membersection{wxLongLong::GetLo}\label{wxlonglonggetlo}
 
 \constfunc{unsigned long}{GetLo}{\void}
 
-Returnes the low 32 bits of 64 bit integer.
+Returns the low 32 bits of 64 bit integer.
 
 \membersection{wxLongLong::GetValue}\label{wxlonglonggetvalue}
 

docs/latex/wx/mbcnvut8.tex

@@ -34,7 +34,7 @@ protocols, and database fields. Notable properties include:
 \item Null bytes do not occur in the encoding, except when there's an actual Unicode
 null character
 \item Preserves sort ordering for plain 8-bit comparison routines like strcmp()
-\item High bit patterns unambiguates character boundaries, and makes it easy to
+\item High bit patterns disambiguates character boundaries, and makes it easy to
 detect whether a string is encoded with UTF-8 or not
 \end{itemize}
 

docs/latex/wx/memorydc.tex

@@ -46,7 +46,7 @@ can be reselected into another memory DC.
 Constructs a new memory device context.
 
 Use the {\it Ok} member to test whether the constructor was successful
-in creating a useable device context. Don't forget to select a bitmap
+in creating a usable device context. Don't forget to select a bitmap
 into the DC before drawing on it.
 
 \membersection{wxMemoryDC::SelectObject}

docs/latex/wx/menu.tex

@@ -12,7 +12,7 @@ associated command but just makes a separator line appear in the menu.
 Menu items may be either normal items, check items or radio items. Normal items
 don't have any special properties while the check items have a boolean flag
 associated to them and they show a checkmark in the menu when the flag is set.
-wxWindows automatically togles the flag value when the item is clicked and its
+wxWindows automatically toggles the flag value when the item is clicked and its
 value may be retrieved using either \helpref{IsChecked}{wxmenuischecked} method
 of wxMenu or wxMenuBar itself or by using 
 \helpref{wxEvent::IsChecked}{wxcommandeventischecked} when you get the menu
@@ -659,7 +659,7 @@ menu bar.}
 \pythonnote{Only the default constructor is supported in wxPython.
 Use wxMenuBar.Append instead.}
 
-\perlnote{wxPerl only supports the first contructor: 
+\perlnote{wxPerl only supports the first constructor: 
 use {\tt Append} instead.}
 
 \membersection{wxMenuBar::\destruct{wxMenuBar}}
@@ -789,7 +789,7 @@ The found menu item object, or NULL if one was not found.
 
 \constfunc{wxString}{GetHelpString}{\param{int}{ id}}
 
-Gets the help string associated with the menu item identifer.
+Gets the help string associated with the menu item identifier.
 
 \wxheading{Parameters}
 

docs/latex/wx/menuevt.tex

@@ -26,7 +26,7 @@ functions that take a wxMenuEvent argument.
 \twocolitem{{\bf EVT\_MENU\_OPEN(func)}}{A menu is about to be opened.}
 \twocolitem{{\bf EVT\_MENU\_CLOSE(func)}}{A menu has been just closed.}
 \twocolitem{{\bf EVT\_MENU\_HIGHLIGHT(id, func)}}{The menu item with the
-speicifed id has been highlighted: used to show help prompts in the status bar
+specified id has been highlighted: used to show help prompts in the status bar
 by \helpref{wxFrame}{wxframe}}
 \twocolitem{{\bf EVT\_MENU\_HIGHLIGHT\_ALL(func)}}{A menu item has been
 highlighted, i.e. the currently selected menu item has changed.}

docs/latex/wx/menuitem.tex

@@ -111,7 +111,7 @@ Returns the item kind, one of {\tt wxItem\_Separator}, {\tt wxItem\_Normal},
 \constfunc{wxString}{GetLabel}{\void}
 
 Returns the text associated with the menu item without any accelerator
-characaters it might contain.
+characters it might contain.
 
 \wxheading{See also}
 
@@ -122,7 +122,7 @@ characaters it might contain.
 
 \func{static wxString}{GetLabelFromText}{\param{const wxString\& }{text}}
 
-Strips all accelerator characeters and mnemonics from the given {\it text}.
+Strips all accelerator characters and mnemonics from the given {\it text}.
 For example,
 
 \begin{verbatim}