Fixed various typos.

Applied patch by snowleopard2 fixing a bunch of typos such as misspellings and double words in the documentation. Combined the patch with some local queued typos waiting to be committed as well as adding new typo fixes inspired by the patch.

Function names with American spelling were not changed nor was third-party code touched. The only code changes involve some changes in strings that are translated ("Can not" -> "Cannot").

Closes #13063 (again).

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

docs/changes.txt

@@ -266,7 +266,7 @@ Changes in behaviour which may result in compilation errors
 
 - Virtual wxHtmlParser::AddText() takes wxString, not wxChar*, argument now.
 
-- Functions that took wxChar* arguments that could by NULL in wxWidgets 2.8
+- Functions that took wxChar* arguments that could be NULL in wxWidgets 2.8
   are deprecated and passing NULL to them won't compile anymore, wxEmptyString
   must be used instead.
 
@@ -321,7 +321,7 @@ Changes in behaviour which may result in compilation errors
   without enclosing parentheses results in warnings from g++ with -Wparentheses,
   add parentheses around the if statement body to work around it.
 
-- wxList::Member() now returns book and not a pointer/iterator. This shouldn't
+- wxList::Member() now returns bool and not a pointer/iterator. This shouldn't
   require any changes as it was always meant to be used for checking for the
   presence of an element in the list only. If you used it as Find(), simple do
   use Find() instead.
@@ -614,7 +614,7 @@ All (GUI):
   dismissed immediately as text control grabbed the focus).
 - wxPropertyGrid: added wxPG_EX_MULTIPLE_SELECTION.
 - wxPropertyGrid: added functions for editing property labels.
-- wxPropertyGrid: many fixes to property validation failure behavior. Added
+- wxPropertyGrid: many fixes to property validation failure behaviour. Added
   new flags: wxPG_VFB_SHOW_MESSAGEBOX and wxPG_VFB_SHOW_MESSAGE_ON_STATUSBAR.
 - wxPropertyGrid: Added wxPropertyGrid::DedicateKey().
 - wxPropertyGrid: wxArrayStringProperty now uses wxEditableListBox.
@@ -2245,7 +2245,7 @@ All:
 - Unicode support in wxODBC is now fully implemented
 - A new data type specific to wxWidgets called SQL_C_WXCHAR has been introduced.
   SQL_C_WXCHAR should be used rather than SQL_C_CHAR to ensure transparent
-  behavior between Unicode and non-unicode builds
+  behaviour between Unicode and non-unicode builds
 - BLOB example added to samples/db (thanks to Casey O'Donnell)
 - use wxStream::GetLength() instead of deprecated GetSize()
 - wxGetOsDescription() is now more precise (Olly Betts)
@@ -2392,7 +2392,7 @@ All:
 - sped up wxHTTP and wxFTP
 - added wxStringInput/OutputStreams
 - added wxFileConfig::Save(wxOutputStream)
-- fixed wxString's behavior with inserted null characters
+- fixed wxString's behaviour with inserted null characters
 
 All (GUI):
 

docs/cocoa/coding_patterns.txt

@@ -75,7 +75,7 @@ methods in a different manner.
 Because the Cocoa view hierarchy isn't a perfect match with the wxWidgets hierarchy, there are some conventions
 used to resolve this conflict.  The first is that m_cocoaNSView is defined to be the view which most-closely
 represents the wxWidgets view.  For instance, a wxButton has an NSButton instance and a wxStaticBox has an NSBox
-instance.  Unfortunately, wxWidgets defines some behavior that Cocoa cannot directly implement.  This is primarily
+instance.  Unfortunately, wxWidgets defines some behaviour that Cocoa cannot directly implement.  This is primarily
 window scrolling (e.g. without using a wxScrolledWindow) and window hiding.
 
 Scrolling is implemented in a separate class known as wxWindowCocoaScrollView.  This class does not fit into
@@ -89,7 +89,7 @@ This is an artifact of the pre-Panther days of Cocoa where there was no method f
 
 What these classes do is provide a Cocoa view that sits between the wxWidget's parent window's view and the
 m_cocoaNSView provided by the window.  The wxWindow class has a GetNSViewForSuperview() method that returns either
-the m_cocoaNSView (if the window does not need scrolling behavior and is not hidden) or returns the scroll view
+the m_cocoaNSView (if the window does not need scrolling behaviour and is not hidden) or returns the scroll view
 for the case of scrolling or the dummy view in the case of hiding.  As the name suggests, the method is used
 from the parent wxWindow (the superview) when it sends something like an addSubview: message.  The method is under
 no circumstances intended to be used as the receiver of an addSubview message.  In fact, not even the GetNSView()

docs/doxygen/mainpages/utilities.h

@@ -12,7 +12,7 @@
 
 In addition to the wxWidgets libraries (see @ref page_libs), some utilities
 are available to the users in the @c utils hierarchy (even if some of them are
-explicitely coinceived for wxWidgets maintainance and will probably be of
+explicitly conceived for wxWidgets maintainance and will probably be of
 little use to others).
 
 Please note that these utilities do represent only the utilities developed
@@ -71,7 +71,7 @@ can even correct them automatically. It uses the XML outputs of the gccxml utili
 (see http://www.gccxml.org) and of the Doxygen utility (see http://www.doxygen.org)
 to do the comparisons.
 
-It's explicitely designed for wxWidgets documentation needs and is probably of little
+It's explicitly designed for wxWidgets documentation needs and is probably of little
 use for anything else than wxWidgets docs reviewing.
 
 You can find it in @c utils/ifacecheck.

docs/doxygen/overviews/archive.h

@@ -361,7 +361,7 @@ attempts to update it if it is still around.
 The documentation for each archive entry type gives the details of what
 meta-data becomes available and when. For generic programming, when the worst
 case must be assumed, you can rely on all the fields of wxArchiveEntry being
-fully populated when GetNextEntry() returns, with the the following exceptions:
+fully populated when GetNextEntry() returns, with the following exceptions:
 
 @li wxArchiveEntry::GetSize(): Guaranteed to be available after the entry has
     been read to wxInputStream::Eof(), or wxArchiveInputStream::CloseEntry()

docs/doxygen/overviews/config.h

@@ -23,7 +23,7 @@ information. They were especially designed for this usage and, although may
 probably be used for many other things as well, should be limited to it. It
 means that this information should be:
 
-@li Typed, i.e. strings or numbers for the moment. You can not store binary
+@li Typed, i.e. strings or numbers for the moment. You cannot store binary
     data, for example.
 @li Small. For instance, it is not recommended to use the Windows registry for
     amounts of data more than a couple of kilobytes.

docs/doxygen/overviews/customwidgets.h

@@ -26,7 +26,7 @@ and is obviously easier and faster.
 However there are situations where you need to show some particular kind of data
 which is not suited to any existing control.
 In these cases rather than hacking an existing control for something it has not
-been coinceived for, it's better to write a new widget.
+been conceived for, it's better to write a new widget.
 
 
 @section overview_customwidgets_how How to write the custom widget

docs/doxygen/overviews/propgrid.h

@@ -794,7 +794,7 @@ wxTextCtrl, they navigate between adjacent properties. As such:
 @section propgrid_customizing Customizing Properties (without sub-classing)
 
 In this section are presented miscellaneous ways to have custom appearance
-and behavior for your properties without all the necessary hassle
+and behaviour for your properties without all the necessary hassle
 of sub-classing a property class etc.
 
 @subsection propgrid_customimage Setting Value Image
@@ -957,7 +957,7 @@ wxPropertyGrid::CenterSplitter() method. <b>However, be sure to call it after
 the sizer setup and SetSize calls!</b> (ie. usually at the end of the
 frame/dialog constructor)
 
-  Splitter centering behavior can be customized using
+  Splitter centering behaviour can be customized using
 wxPropertyGridInterface::SetColumnProportion(). Usually it is used to set
 non-equal column proportions, which in essence stops the splitter(s) from
 being 'centered' as such, and instead just auto-resized.
@@ -994,7 +994,7 @@ Version of wxPropertyGrid bundled with wxWidgets 2.9+ has various backward-
 incompatible changes from version 1.4, which had a stable API and will remain
 as the last separate branch.
 
-Note that in general any behavior-breaking changes should not compile or run
+Note that in general any behaviour-breaking changes should not compile or run
 without warnings or errors.
 
 @subsection propgrid_compat_general General Changes
@@ -1005,14 +1005,14 @@ without warnings or errors.
     with keyboard. This change allowed fixing broken tab traversal on wxGTK
     (which is open issue in wxPropertyGrid 1.4).
 
-  - wxPG_EX_UNFOCUS_ON_ENTER style is removed and is now default behavior.
+  - wxPG_EX_UNFOCUS_ON_ENTER style is removed and is now default behaviour.
     That is, when enter is pressed, editing is considered done and focus
     moves back to the property grid from the editor control.
 
   - A few member functions were removed from wxPropertyGridInterface.
     Please use wxPGProperty's counterparts from now on.
 
-  - wxPGChoices now has proper Copy-On-Write behavior.
+  - wxPGChoices now has proper Copy-On-Write behaviour.
 
   - wxPGChoices::SetExclusive() was renamed to AllocExclusive().
 
@@ -1026,15 +1026,15 @@ without warnings or errors.
     now use wxPropertyGridInterface::GetEditableState() instead.
 
   - wxPG_EX_DISABLE_TLP_TRACKING is now enabled by default. To get the old
-    behavior (recommended if you don't use a system that reparents the grid
+    behaviour (recommended if you don't use a system that reparents the grid
     on its own), use the wxPG_EX_ENABLE_TLP_TRACKING extra style.
 
   - Extended window style wxPG_EX_LEGACY_VALIDATORS was removed.
 
-  - Default property validation failure behavior has been changed to
+  - Default property validation failure behaviour has been changed to
     (wxPG_VFB_MARK_CELL | wxPG_VFB_SHOW_MESSAGEBOX), which means that the
     cell is marked red and wxMessageBox is shown. This is more user-friendly
-    than the old behavior, which simply beeped and prevented leaving the
+    than the old behaviour, which simply beeped and prevented leaving the
     property editor until a valid value was entered.
 
   - wxPropertyGridManager now has same Get/SetSelection() semantics as

docs/doxygen/overviews/refcount.h

@@ -47,7 +47,7 @@ will return @true if two objects are identical and not only if they share the
 same data.
 
 Note that wxWidgets follows the <em>STL philosophy</em>: when a comparison
-operator can not be implemented efficiently (like for e.g. wxImage's ==
+operator cannot be implemented efficiently (like for e.g. wxImage's ==
 operator which would need to compare the entire image's data, pixel-by-pixel),
 it's not implemented at all. That's why not all reference counted classes
 provide comparison operators.

docs/doxygen/overviews/referencenotes.h

@@ -15,7 +15,7 @@ that descriptions of inherited member functions are not duplicated in derived
 classes unless their behaviour is different. So in using a class such as
 wxScrolledWindow, be aware that wxWindow functions may be relevant.
 
-Where not explicitely stated, size and position arguments may usually be given a
+Where not explicitly stated, size and position arguments may usually be given a
 value of ::wxDefaultSize and ::wxDefaultPosition, in which case wxWidgets will
 choose suitable values.
 

docs/doxygen/overviews/thread.h

@@ -7,7 +7,7 @@
 /////////////////////////////////////////////////////////////////////////////
 
 /*
-    NOTE: we explicitely don't name wxMutexGUIEnter() and wxMutexGUILeave()
+    NOTE: we explicitly don't name wxMutexGUIEnter() and wxMutexGUILeave()
           as they're not safe. See also ticket #10366.
 */
 

docs/doxygen/overviews/unicode.h

@@ -230,7 +230,7 @@ problems:
   - Using a cast to force the issue (listed only for completeness):
     @code printf("Hello, %s", (const char *)s.c_str()) @endcode
 
- - The result of @c c_str() can not be cast to @c char* but only to @c const @c
+ - The result of @c c_str() cannot be cast to @c char* but only to @c const @c
    @c char*. Of course, modifying the string via the pointer returned by this
    method has never been possible but unfortunately it was occasionally useful
    to use a @c const_cast here to pass the value to const-incorrect functions.

docs/doxygen/overviews/windowids.h

@@ -36,7 +36,7 @@ There are two ways to generate an ID.  One way is to start at a negative
 number, and for each new ID, return the next smallest number.  This is fine for
 systems that can use the full range of negative numbers for IDs, as this
 provides more than enough IDs and it would take a very very long time to run
-out and wrap around.  However, some systems can not use the full range of the
+out and wrap around.  However, some systems cannot use the full range of the
 ID value. Windows, for example, can only use 16 bit IDs, and only has about
 32000 possible automatic IDs that can be generated by wxWindow::NewControlId.
 If the program runs long enough, depending on the program itself, using this

docs/doxygen/overviews/windowsizing.h

@@ -43,7 +43,7 @@ some simple explanations of things.
     the minimal size.
 
 @li @b "Maximum Size": just like for the minimal size, the maximum size is normally
-    explicitely set by the programmer with the wxWindow::SetMaxSize() method or
+    explicitly set by the programmer with the wxWindow::SetMaxSize() method or
     with wxWindow::SetSizeHints().
     Top-level windows such as wxFrame will not allow the user to resize the frame above
     the maximum size.

docs/doxygen/overviews/xrc_format.h

@@ -1792,7 +1792,7 @@ wxWizardPageSimple classes. They both support the following properties
 @endTable
 
 wxWizardPageSimple pages are automatically chained together; wxWizardPage pages
-transitions must be handled programatically.
+transitions must be handled programmatically.
 
 
 @section overview_xrcformat_sizers Sizers

docs/os2/install.txt

@@ -73,7 +73,7 @@ it, EMX is following the example of the unix ports.
 Compilation with VisualAge
 --------------------------
 
-In addition to VisualAge V3.0 Fixpack 8 you will need the following inorder
+In addition to VisualAge V3.0 Fixpack 8 you will need the following in order
 to successfully build and use wxWidgets for OS/2:
 
 1.  IBM OS/2 Toolkit Version 4.5 or later
@@ -130,7 +130,7 @@ the following three modules from your temp.def file, db.cpp, dbgrid.cpp and
 dbtable.cpp.  save you changes to temp.def.  Delete wx23.def and rename your
 temp.def to wx23.def and you are ready to go.
 
-I hope to clean up the .dll builds at some point before the the library is
+I hope to clean up the .dll builds at some point before the library is
 a full fledged production caliber product.  Fortunately EMX and Watcom can use
 the import and export pragmas successfully negating the need for manual .def
 files.  VA 3.0, unfortunately in C++ does not properly export the mangled

docs/publicity/WoWoW30.html

@@ -250,7 +250,7 @@ and may thus be the most important changes from a user's perspective
 	<LI><P ALIGN=JUSTIFY>Added a new sizer which can wrap across
 	multiple lines. See <A HREF="http://docs.wxwidgets.org/trunk/classwx_wrap_sizer.html">wxWrapSizer</A>.</P>
 	<LI><P ALIGN=JUSTIFY>Added multi-sample and anti-aliasing support
-	the the OpenGL canvas and separated wxGLCanvas and wxGLContext. See
+	to the OpenGL canvas and separated wxGLCanvas and wxGLContext. See
 	<A HREF="http://docs.wxwidgets.org/trunk/classwx_g_l_canvas.html">wxGLCanvas</A>.</P>
 	<LI><P ALIGN=JUSTIFY>Added wxNativeContainerWindow in order to
 	construct a wxTopLevelWindow from a native window handle (MSW and

docs/tech/tn0003.txt

@@ -177,7 +177,7 @@ commands are optionals.
 
 Also note that if you use @section and @subsection in the class description
 (at the beginning), you should use as the section's anchor name "xxxx_yyyy"
-where "xxxx" is the the class name without the initial "wx" in lowercase
+where "xxxx" is the class name without the initial "wx" in lowercase
 and "yyyy" is a lowercase word which uniquely identifies that section.
 E.g.: