Also fix spelling mistakes in the documentation files

Run the same codespell command on docs directory.

docs/doxygen/overviews/cmake.md

@@ -26,7 +26,7 @@ Using the CMake Command Line           {#cmake_cli}
 2. Change into the created folder
 3. Run `cmake -G "Unix Makefiles" path_to_wxWidgets_root`
 4. After that you can run `cmake --build .` to start the build process or
-   directly use your choosen build system.
+   directly use your chosen build system.
 
 Run `cmake --help` to see a list of available generators on your platform.
 These can than be specified using the -G command line option. On Windows it

docs/doxygen/overviews/customwidgets.h

@@ -12,7 +12,7 @@
 @tableofcontents
 
 Typically combining the existing @ref group_class_ctrl controls in wxDialogs
-and wxFrames is sufficient to fullfill any GUI design. Using the wxWidgets
+and wxFrames is sufficient to fulfill any GUI design. Using the wxWidgets
 standard controls makes your GUI looks native on all ports and is obviously
 easier and faster.
 

docs/doxygen/overviews/datetime.h

@@ -106,7 +106,7 @@ just @c wxDateTime::Now() + wxDateSpan::Month()).
 
 
 
-@section overview_datetime_arithmetics Date Arithmetics
+@section overview_datetime_arithmetics Date Arithmetic
 
 Many different operations may be performed with the dates, however not all of
 them make sense. For example, multiplying a date by a number is an invalid

docs/doxygen/overviews/printing.h

@@ -84,7 +84,7 @@ The scaling of the drawn image typically differs from the screen to the preview
 and printed images. This class provides a set of routines named
 FitThisSizeToXXX(), MapScreenSizeToXXX(), and GetLogicalXXXRect, which can be
 used to set the user scale and origin of the wxPrintout's DC so that your class
-can easily map your image to the printout withough getting into the details of
+can easily map your image to the printout without getting into the details of
 screen and printer PPI and scaling. See the printing sample for examples of how
 these routines are used.
 

docs/doxygen/overviews/richtextctrl.h

@@ -415,7 +415,7 @@ set the focus back to the top-level object.
 An event will be sent to the control when the focus changes.
 
 When the user clicks on the control, wxRichTextCtrl determines which container
-to set as the current object focus by calling the found container's overrided
+to set as the current object focus by calling the found container's overridden
 wxRichTextObject::AcceptsFocus function. For example, although a table is a
 container, it must not itself be the object focus because there is no text
 editing at the table level. Instead, a cell within the table must accept the

docs/doxygen/overviews/xrc_format.h

@@ -115,7 +115,7 @@ These come in two varieties:
     ("\<label\>Cancel\</label\>"), but they may use nested subelements too (e.g.
     @ref overview_xrcformat_type_font "font property"). A property can only be
     listed once in an object's definition.
- -# Child objects. Window childs, sizers, sizer items or notebook pages
+ -# Child objects. Window children, sizers, sizer items or notebook pages
     are all examples of child objects. They are represented using nested
     @c \<object\> elements and are can be repeated more than once. The specifics
     of which object classes are allowed as children are class-specific and
@@ -1819,7 +1819,7 @@ objects have the following properties:
 @endTable
 
 A wxRibbonPage may have children of any type derived from wxRibbonControl.
-Most commontly, wxRibbonPanel is used. As a special case, the @c panel
+Most commonly, wxRibbonPanel is used. As a special case, the @c panel
 pseudo-class may be used instead of @c wxRibbonPanel when used as wxRibbonPage
 children.