Fix-more-typos-using-codespell

Committing nearly all changes done by 'codespell_check.sh -w'

Signed-off-by: Simon Goldschmidt <goldsimon@gmx.de>

doc/ZeroCopyRx.c

@@ -13,7 +13,7 @@ void my_pbuf_free_custom(void* p)
   my_custom_pbuf_t* my_puf = (my_custom_pbuf_t*)p;
 
   // invalidate data cache here - lwIP and/or application may have written into buffer!
-  // (invalidate is faster than flushing, and noone needs the correct data in the buffer)
+  // (invalidate is faster than flushing, and no one needs the correct data in the buffer)
   invalidate_cpu_cache(p->payload, p->tot_len);
 
   SYS_ARCH_PROTECT(old_level);

doc/doxygen/main_page.h

@@ -147,7 +147,7 @@
  * -------------
  * In mainloop mode, only @ref callbackstyle_api can be used.
  * The user has two possibilities to ensure there is only one
- * exection context at a time in lwIP:
+ * execution context at a time in lwIP:
  *
  * 1) Deliver RX ethernet packets directly in interrupt context to lwIP
  *    by calling netif->input directly in interrupt. This implies all lwIP
@@ -181,7 +181,7 @@
  *    it is safe to call any @ref callbackstyle_api from there.
  *
  * 2) Use @ref LWIP_TCPIP_CORE_LOCKING. All @ref callbackstyle_api
- *    functions can be called when lwIP core lock is aquired, see
+ *    functions can be called when lwIP core lock is acquired, see
  *    @ref LOCK_TCPIP_CORE() and @ref UNLOCK_TCPIP_CORE().
  *    These macros cannot be used in an interrupt context!
  *    Note the OS must correctly handle priority inversion for this.
@@ -258,7 +258,7 @@
  */
 
 /**
- * @page sys_init System initalization
+ * @page sys_init System initialization
 A truly complete and generic sequence for initializing the lwIP stack
 cannot be given because it depends on additional initializations for
 your runtime environment (e.g. timers).
@@ -343,7 +343,7 @@ Call these functions in the order of appearance:
  * - sockets.h
  * - sys.h
  *
- * Additionaly, memory (de-)allocation functions may be
+ * Additionally, memory (de-)allocation functions may be
  * called from multiple threads (not ISR!) with NO_SYS=0
  * since they are protected by @ref SYS_LIGHTWEIGHT_PROT and/or
  * semaphores.

doc/mqtt_client.txt

@@ -150,7 +150,7 @@ void example_publish(mqtt_client_t *client, void *arg)
   }
 }
 
-/* Called when publish is complete either with sucess or failure */
+/* Called when publish is complete either with success or failure */
 static void mqtt_pub_request_cb(void *arg, err_t result)
 {
   if(result != ERR_OK) {

doc/ppp.txt

@@ -404,7 +404,7 @@ really know what you are doing, your move ;-)
 
 
 /*
- * Fonction to call for received data
+ * Function to call for received data
  *
  * ppp, PPP control block
  * buffer, input buffer