no code changes, fixed some typos

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

docs/doxygen/overviews/nonenglish.h

@@ -110,7 +110,7 @@ wxLocale::GetSystemEncodingName) by the user's operating system.
 By convention, you should only use characters without diacritics (i.e. 7-bit
 ASCII strings) for msgids in the source code and write them in English.
 
-If you port software to wxWindows, you may be confronted with legacy source
+If you port software to wxWidgets, you may be confronted with legacy source
 code containing non-English string literals. Instead of translating the strings
 in the source code to English and putting the original strings into message
 catalog, you may configure wxWidgets to use non-English msgids and translate to

docs/doxygen/overviews/unicode.h

@@ -198,7 +198,7 @@ work. Here are some examples, using a wxString object @c s and some integer @c
 n:
 
  - Writing @code switch ( s[n] ) @endcode doesn't work because the argument of
-   the switch statement must an integer expression so you need to replace
+   the switch statement must be an integer expression so you need to replace
    @c s[n] with @code s[n].GetValue() @endcode. You may also force the
    conversion to @c char or @c wchar_t by using an explicit cast but beware that
    converting the value to char uses the conversion to current locale and may

docs/doxygen/overviews/xrc.h

@@ -31,7 +31,7 @@ There are several advantages to using XRC resources:
 @li The XRC format uses sizers for flexibility, allowing dialogs to be
     resizable and highly portable.
 @li The XRC format is a wxWidgets standard, and can be generated or
-    postprocessed by any program that understands it. As it is basedon the XML
+    postprocessed by any program that understands it. As it is based on the XML
     standard, existing XML editors can be used for simple editing purposes.
 
 XRC was written by Vaclav Slavik.