No code changes, fixed some typos.

Changed several occurrences of "it's" where "its" is meant, as well as a few other minor typos.

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

docs/doxygen/overviews/runtimeclass.h

@@ -35,7 +35,7 @@ Most C++ GUI frameworks overcome these limitations by means of a set of macros
 and functions and wxWidgets is no exception. As it originated before the
 addition of RTTI to the C++ standard and as support for it is still missing
 from some (albeit old) compilers, wxWidgets doesn't (yet) use it, but provides
-it's own macro-based RTTI system.
+its own macro-based RTTI system.
 
 In the future, the standard C++ RTTI will be used though and you're encouraged
 to use whenever possible the wxDynamicCast macro which, for the implementations
@@ -79,7 +79,7 @@ This class stores meta-information about classes. An application may use macros
 such as DECLARE_DYNAMIC_CLASS and IMPLEMENT_DYNAMIC_CLASS to record runtime
 information about a class, including:
 
-@li It's position in the inheritance hierarchy.
+@li Its position in the inheritance hierarchy.
 @li The base class name(s) (up to two base classes are permitted).
 @li A string representation of the class name.
 @li A function that can be called to construct an instance of this class.

docs/tech/tn0017.txt

@@ -1,7 +1,7 @@
                     How to write unit tests for wxWidgets
                     =====================================
 
- Unit tests for wxWidgets are written using small cppunit framework. To compile
+Unit tests for wxWidgets are written using small cppunit framework. To compile
 (but not to run) them you need to have it installed. Hence the first part of
 this note explains how to do it while the second one explains how to write the
 test.
@@ -17,7 +17,7 @@ I. CppUnit Installation
     - build everything in CppUnitLibraries.dsw work space
     - add include and lib subdirectories of the directory
       where you installed cppunit to the compiler search path
-      using "Tools|Options" menu in VC IDEA
+      using "Tools|Options" menu in VC IDE
 
  b) Under Unix: run configure && make && make install as usual
 
@@ -38,7 +38,7 @@ II. Writing tests with CppUnit
     // register in the unnamed registry so that these tests are run by default
     CPPUNIT_TEST_SUITE_REGISTRATION(MBConvTestCase);
 
-    // also include in it's own registry so that these tests can be run alone
+    // also include in its own registry so that these tests can be run alone
     CPPUNIT_TEST_SUITE_NAMED_REGISTRATION(MBConvTestCase, "MBConvTestCase");
 
     Read CppUnit documentation for more.
@@ -130,7 +130,7 @@ IV. Notes
     //CPPUNIT_TEST_SUITE_REGISTRATION(wxRegExTestCase);
     CPPUNIT_TEST_SUITE_NAMED_REGISTRATION(wxRegExTestCase, "fixme");
 
-    // also include in it's own registry so that these tests can be run alone
+    // also include in its own registry so that these tests can be run alone
     CPPUNIT_TEST_SUITE_NAMED_REGISTRATION(wxRegExTestCase, "wxRegExTestCase");
 
 4. Tests which take a long time to execute can be registered under "advanced"