Run codespell -w against all files

and fix the wrong correction

.asf.yaml

@@ -2,9 +2,9 @@ github:
   description: "Apache NuttX is a mature, real-time embedded operating system (RTOS)"
   homepage: https://nuttx.apache.org/
   features:
-    # Enable issues managment
+    # Enable issues management
     issues: true
-    # Enable project for project managment boards
+    # Enable project for project management boards
     projects: true
   labels:
     - nuttx

Documentation/NuttX.html

@@ -3847,7 +3847,7 @@ <h2><a name="changelogs"><b>Release Notes and Change Logs</b>:</a></h2>
             Some initial files for the LPC17xx family were released in NuttX 5.6, but
           </li>
           <li>
-            The first functional release for the NXP LPC1768/Nucleus2G occured with NuttX 5.7 with
+            The first functional release for the NXP LPC1768/Nucleus2G occurred with NuttX 5.7 with
             Some additional enhancements through NuttX-5.9.
             Refer to the NuttX board <a href="https://bitbucket.org/patacongo/obsoleted/src/master/configs/nucleus2g/README.txt" target="_blank">README</a> file for further information.
           </li>
@@ -3866,7 +3866,7 @@ <h2><a name="changelogs"><b>Release Notes and Change Logs</b>:</a></h2>
       <p><b>Obsoleted</b>.
         Support for the Nucleus2G board was terminated on 2016-04-12.
         There has not been any activity with the commercial board in a few years and it no longer appears to be available from the 2g-eng.com website.
-        Since the board is commercial and no longer publically available, it no longer qualifies for inclusion in the open source repositories.
+        Since the board is commercial and no longer publicly available, it no longer qualifies for inclusion in the open source repositories.
         A snapshot of the code is still available in the <a href="https://bitbucket.org/patacongo/obsoleted/src/master/boards/nucleus2g">Obsoleted repository</a> and can easily be <i>reconstitued</i> if needed.
       </p>
       </li>
@@ -4078,7 +4078,7 @@ <h2><a name="changelogs"><b>Release Notes and Change Logs</b>:</a></h2>
   <td>
     <p>
       <a name="xmd45xx"><b>Infineon XMC45xx</b>.</a>
-      An initial but still incomplete port to the XMC4500 Relax board was released with NuttX-7.21 (although it wass not really ready for prime time).  Basic NSH functionality was a serial console was added by Alan Carvahlo de Assis in NuttX-7.23.  Alan also added an SPI driver in NuttX-7.25.
+      An initial but still incomplete port to the XMC4500 Relax board was released with NuttX-7.21 (although it was not really ready for prime time).  Basic NSH functionality was a serial console was added by Alan Carvahlo de Assis in NuttX-7.23.  Alan also added an SPI driver in NuttX-7.25.
     </p>
     <p>
       This initial porting effort uses the Infineon XMC4500 Relax v1 board as described on the manufacturer's <a href="http://www.infineon.com/cms/en/product/evaluation-boards/KIT_XMC45_RELAX_V1/productType.html?productType=db3a304437849205013813b23ac17763">website</a>.

Documentation/NuttXBinfmt.html

@@ -469,7 +469,7 @@ <h2>3.2 <a name="symtabdata">Symbol Table Data Structures</a></h2>
 struct symtab_s
 {
   FAR const char *sym_name;          /* A pointer to the symbol name string */
-  FAR const void *sym_value;         /* The value associated witht the string */
+  FAR const void *sym_value;         /* The value associated with the string */
 };
 </pre></ul>
 

Documentation/NuttXCCodingStandard.html

@@ -417,7 +417,7 @@ <h2><a name="comments">1.3 Comments</a></h2>
   </li>
   <li>
     Text following '.' or ':' begins with an upper-case character;
-    text folowing ',' or ';' begins with a lower-case character.
+    text following ',' or ';' begins with a lower-case character.
   </li>
 </ul>
 <p>
@@ -608,7 +608,7 @@ <h2><a name="comments">1.3 Comments</a></h2>
 <p>
   <b>Comments to the Right of Data Definitions</b>.
   Comments to the right of a declaration with an enumeration or structure, on the other hand, are encouraged, provided that the comments are short and do not exceed the maximum line width (usually 78 characters).
-  Columnar alignment of comments is very desireable (but often cannot be achieved without violating the line width).
+  Columnar alignment of comments is very desirable (but often cannot be achieved without violating the line width).
 </p>
 <center><table width="60%" border=1>
 <tr><td bgcolor="white">
@@ -696,7 +696,7 @@ <h2><a name="comments">1.3 Comments</a></h2>
 
 <p>
   <b>C Style Comments</b>.
-  C99/C11/C++ style comments (beginning wih <code>//</code>) should not be used with NuttX.
+  C99/C11/C++ style comments (beginning with <code>//</code>) should not be used with NuttX.
   NuttX generally follows C89 and all code outside of architecture specific directories must be compatible with C89.
 </p>
 <center><table width="60%" border=1>
@@ -803,7 +803,7 @@ <h2>1.4 <a name="braces">Braces</a></h2>
   </li>
   <li>
     <b>Compound Statements</b>.
-    Within this document, an opening left brace followed by a sequence of statments, and ending with a closing right brace is refered to as a <i>compound statement</i>.
+    Within this document, an opening left brace followed by a sequence of statments, and ending with a closing right brace is referred to as a <i>compound statement</i>.
   </li>
   <li>
     <b>Nested Compound Statements</b>.
@@ -1047,7 +1047,7 @@ <h2>1.5 <a name="indentation">Indentation</b></h2>
   C pre-processor statements should always be indented in this way in the <code>Pre-processor Definitions</code> <a href="#cfilestructure">section</a> of each file.
   C pre-processor statements may be indented in the <code>Public/Private Data</code> and <code>Public/Private Functions</code> sections of the file.
   However, often the indentation of C pre-processor statements conflicts with the indentation of the C code and makes the code more difficult to read.
-  In such cases, indentation of C pre-processor statements should be ommitted in those sections (only).
+  In such cases, indentation of C pre-processor statements should be omitted in those sections (only).
 </p>
 
 <center><table width="60%" border=1>
@@ -1133,7 +1133,7 @@ <h2>1.6 <a name="parentheses"></a>Parentheses</a></h2>
     Otherwise, there should be no space before the left parentheses
   </li>
   <li>
-    <b>No space betwen function name and argument list</b>.
+    <b>No space between function name and argument list</b>.
     There should be no space between a function name and an argument list.
   </li>
   <li>
@@ -1455,7 +1455,7 @@ <h2>2.5 <a name="structures">Structures</a></h2>
         First for structures that are defined within another union or structure (discouraged).  In those cases, the structure name should always be omitted.
       </li>
       <li>
-        Second for structures as the type of a local variable.  In this case, again, the structure name should always be ommitted.
+        Second for structures as the type of a local variable.  In this case, again, the structure name should always be omitted.
       </li>
     </ol>
   </li>
@@ -2570,7 +2570,7 @@ <h2>4.6 <a name="while"><code>while</code> Statement</a></h2>
   </li>
   <li>
     <b>Followed by a single blank line</b>.
-    The final right brace that closes the <code>while &lt;condition&gt;</code> statment must be followed by a single blank line.
+    The final right brace that closes the <code>while &lt;condition&gt;</code> statement must be followed by a single blank line.
   </li>
   <li>
     <b>Exception</b>.
@@ -2692,7 +2692,7 @@ <h2>4.8 <a name="goto">Use of <code>goto</code></a></h2>
   <li>
     <b>Error Exit Labels</b>.
     The error exit label is normally called <code>errout</code>.
-    Multiple error labels are often to required to <i>unwind</i> to recover resources committe in logic prior to the error to otherwise <i>undo</i> preceding operations.
+    Multiple error labels are often to required to <i>unwind</i> to recover resources committed in logic prior to the error to otherwise <i>undo</i> preceding operations.
     Naming for these other labels would be some like <code>errout_with_allocation</code>, <code>errout_with_openfile</code>, etc.
   </li>
   <li>

Documentation/NuttxPortingGuide.html

@@ -2296,7 +2296,7 @@ <h2><a name="boardimports">4.3 APIs Exported by Board-Specific Logic to NuttX</a
   There are many interfaces exported from board- to architecture-specific logic.
   But there are only a few exported from board-specific logic to common NuttX logic.
   Those few of those related to initialization will be discussed in this paragraph.
-  There are others, like those used by <a href="#boardctl"><code>boardctl()</code></a> that will be dicussed in other paragraphs.
+  There are others, like those used by <a href="#boardctl"><code>boardctl()</code></a> that will be discussed in other paragraphs.
 </p>
 <p>
   All of the board-specific interfaces used by the NuttX OS logic are for controlled board initialization.
@@ -2339,7 +2339,7 @@ <h3><a name="boardlateinit">4.3.2 board_late_initialize()</a></h3>
   This additional initialization phase may be used, for example, to initialize more complex, board-specific device drivers.
 </p>
 <p>
-  Waiting for events, use of I2C, SPI, etc are permissable in the context of board_late_initialize().
+  Waiting for events, use of I2C, SPI, etc are permissible in the context of board_late_initialize().
   That is because <code>board_late_initialize()</code> will run on a temporary, internal kernel thread.
 </p>
 

Documentation/NuttxUserGuide.html

@@ -860,7 +860,7 @@ <H3><a name="exec">2.1.12 exec</a></H3>
 <p>
   This non-standard interface is included as a official NuttX API only because it is needed in certain build modes: <code>exec()</code> is probably the only want to load programs in the PROTECTED mode.  Other file execution APIs rely on a symbol table provided by the OS.  In the PROTECTED build mode, the OS cannot provide any meaningful symbolic information for execution of code in the user-space blob so that is the <code>exec()</code> function is really needed in that build case
 </p>
-  The interface is available in the FLAT build mode although it is not really necessary in that case.  It is currently used by some example code under the <code>apps/</code> that that generate their own symbol tables for linking test programs.  So althought it is not necessary, it can still be useful.
+  The interface is available in the FLAT build mode although it is not really necessary in that case.  It is currently used by some example code under the <code>apps/</code> that that generate their own symbol tables for linking test programs.  So although it is not necessary, it can still be useful.
 </p>
 <p>
   The interface would be completely useless and will not be supported in the KERNEL build mode where the contrary is true:  An application process cannot provide any meaning symbolic information for use in linking a different process.