diff --git a/Documentation/NuttX.html b/Documentation/NuttX.html
index 69d7d4c2539..2daf9c73945 100644
--- a/Documentation/NuttX.html
+++ b/Documentation/NuttX.html
@@ -81,7 +81,7 @@
   <td>
     <a href="#TODO">Bugs, Issues, <i>Things-To-Do</i></a>.<br>
     Software is never finished nor ever tested well enough.
-    (Do you want to help devlop NuttX?  If so, send me an email).
+    (Do you want to help develop NuttX?  If so, send me an email).
   </td>
 </tr>
 <tr>
@@ -183,7 +183,7 @@
       The primary governing standards are POSIX and ANSI standards.
       Additional standard APIs from Unix and other common RTOS's are
       adopted for functionality not available under these standards
-      or for functionaly that is not appropriate for the deeply-embedded
+      or for functionality that is not appropriate for the deeply-embedded
       RTOS (such as <code>fork()</code>).
     </p>
     <p>
@@ -460,7 +460,7 @@
   from the <a href="http://sourceforge.net/project/showfiles.php?group_id=189573">SourceForge</a>
   website.
   The change log associated with the release is available <a href="#currentrelease">here</a>.
-  Unreleased changes after this release are avalable in CVS.
+  Unreleased changes after this release are available in CVS.
   These unreleased changes are listed <a href="#pendingchanges">here</a>.
 </p>
 <p>
@@ -484,7 +484,7 @@
 </ul>
 <p>
   The Pascal add-on it integrated but has so far been tested very little;
-  it is certainly at an early, pre-alpha release leve.
+  it is certainly at an early, pre-alpha release level.
   The baseline functionality of NuttX (including recently added network)
   functionality continues to mature and remains at post-beta or production level.
   Extensive testing has been done for the ARM architecture using the GCC
@@ -525,7 +525,7 @@
   <td>
     <p>
       A user-mode port of NuttX to the x86 Linux platform is available.
-      The purpose of this port is primarily to support OS feature developement.
+      The purpose of this port is primarily to support OS feature development.
     </p>
     <p>
       <b>STATUS:</b>
@@ -628,7 +628,7 @@
       <b>Zilog z16f Microncontroller</b>.
       This port use the Zilog z16f2800100zcog development kit and the Zilog
       ZDS-II Windows command line tools.
-      The development envirnoment is Cygwin under WinXP.
+      The development environment is Cygwin under WinXP.
     </p>
     <p>
       <b>STATUS:</b>
@@ -655,7 +655,7 @@
     </p>
     <p>
      <b>STATUS:</b>
-      This port is complete and stable to the extent that it can be teste
+      This port is complete and stable to the extent that it can be tested
       using an instruction set simulator.
     </p>
    </td>
@@ -782,8 +782,8 @@ Linux or Cygwin.</blockquote>
     </p>
     <ul>
       <li>
-        <b>Pathes</b>.
-        Full pathes for the native toolchain must follow Windows standards.
+        <b>Paths</b>.
+        Full paths for the native toolchain must follow Windows standards.
         For example, the path <code>/home/my\ name/nuttx/include</code> my have to be
         converted to something like <code>'C:\cygwin\home\my name\nuttx\include'</code>
         to be usable by the toolchain.