X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/3e083d652da78616c08dad6ecb3ebd347390d3f4..7243eb6d3be736c27ac4c0c6158156a8e79b7c68:/docs/doxygen/overviews/customwidgets.h

diff --git a/docs/doxygen/overviews/customwidgets.h b/docs/doxygen/overviews/customwidgets.h
index efedece426..d427746e82 100644
--- a/docs/doxygen/overviews/customwidgets.h
+++ b/docs/doxygen/overviews/customwidgets.h
@@ -3,7 +3,7 @@
 // Purpose:     topic overview
 // Author:      wxWidgets team
 // RCS-ID:      $Id$
-// Licence:     wxWindows license
+// Licence:     wxWindows licence
 /////////////////////////////////////////////////////////////////////////////
 
 /**
@@ -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
@@ -135,7 +135,7 @@ The organization used by wxWidgets consists in:
 - declaring the real widget class inheriting from the Base version in
   platform-specific headers; see for example the wxWidgets' @c "wx/gtk/button.h" file.
 
-- separing the different implementations in different source files, putting
+- separating the different implementations in different source files, putting
   all common stuff in a separate source.
   See for example the wxWidgets' @c "src/common/btncmn.cpp", @c "src/gtk/button.cpp"
   and @c "src/msw/button.cpp" files.