Comments typos fixed.

include/kiway.h

@@ -56,7 +56,7 @@ CMake target must be defined to build either. Whether that is a separate build
 or not is not the important thing. Simply having a single CMake target has
 advantages. (Each builder person will have his/her own intentions relative to
 use of python or not.) Once a DSO is python capable, it can be driven by any
-number of python program tops, including demo-ing (automaton) and testing
+number of python program tops, including demo-ing (automation) and testing
 separately.</li>
 
 

include/tool/tool_manager.h

@@ -52,7 +52,7 @@ public:
     ~TOOL_MANAGER();
 
     /**
-     * Generates an unique ID from for a tool with given name.
+     * Generates a unique ID from for a tool with given name.
      */
     static TOOL_ID MakeToolId( const std::string& aToolName );
 

pcbnew/edit_pcb_text.cpp

@@ -25,7 +25,7 @@
 
 /**
  * @file edit_pcb_text.cpp
- * @brief Editimg of text on copper and technical layers (TEXTE_PCB class)
+ * @brief Editing of text on copper and technical layers (TEXTE_PCB class)
  */
 
 #include <fctsys.h>