all: Fix spelling mistakes based on codespell check.

Signed-off-by: Damien George <damien@micropython.org>

examples/embedding/README.md

@@ -23,7 +23,7 @@ To build the example project, based on `main.c`, use:
 
     $ make
 
-That will create an exacutable called `embed` which you can run:
+That will create an executable called `embed` which you can run:
 
     $ ./embed
 

examples/hwapi/README.md

@@ -5,7 +5,7 @@ which would work from a board to board, from a system to another systems.
 This is inherently a hard problem, because hardware is different from one
 board type to another, and even from examplar of board to another. For
 example, if your app requires an external LED, one user may connect it
-to one GPIO pin, while another user may find it much more convinient to
+to one GPIO pin, while another user may find it much more convenient to
 use another pin. This of course applies to relays, buzzers, sensors, etc.
 
 With complications above in mind, it's still possible to write portable

examples/hwapi/hwconfig_pyboard.py

@@ -1,6 +1,6 @@
 from machine import Pin, Signal
 
-# Red LED on pin LED_RED also kown as A13
+# Red LED on pin LED_RED also known as A13
 LED = Signal("LED_RED", Pin.OUT)
 
 # Green LED on pin LED_GREEN also known as A14

examples/natmod/features1/features1.c

@@ -88,7 +88,7 @@ mp_obj_t mpy_init(mp_obj_fun_bc_t *self, size_t n_args, size_t n_kw, mp_obj_t *a
     // This must be first, it sets up the globals dict and other things
     MP_DYNRUNTIME_INIT_ENTRY
 
-    // Messages can be printed as usualy
+    // Messages can be printed as usual
     mp_printf(&mp_plat_print, "initialising module self=%p\n", self);
 
     // Make the functions available in the module's namespace