Consolidate buffer dumping; fix all occurrences of 'the the'

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@1951 42af7a65-404d-4744-a932-0658087f49c3

4 files changed, 7 insertions, 7 deletions

diff --git a/nuttx/Documentation/NXGraphicsSubsystem.html b/nuttx/Documentation/NXGraphicsSubsystem.html
index 6374c3ca7..6d4597acf 100644
--- a/nuttx/Documentation/NXGraphicsSubsystem.html
+++ b/nuttx/Documentation/NXGraphicsSubsystem.html
@@ -1652,7 +1652,7 @@ int nx_bitmap(NXWINDOW hwnd, FAR const struct nxgl_rect_s *dest,
       or <a href="#nxrequestbkgd"><code>nx_requestbkgd()</code></a> that specifies the
       window that will receive the bitmap image.
     <dt><code>dest</code>
-    <dd> Describes the rectangular on the display that will receive the the bit map.
+    <dd> Describes the rectangular on the display that will receive the bit map.
     <dt><code>src</code>
     <dd>The start of the source image.  This is an array source images of size
       <code>CONFIG_NX_NPLANES</code> (probably 1).
diff --git a/nuttx/Documentation/NuttShell.html b/nuttx/Documentation/NuttShell.html
index 788e9ab00..4cc4c4125 100644
--- a/nuttx/Documentation/NuttShell.html
+++ b/nuttx/Documentation/NuttShell.html
@@ -1348,7 +1348,7 @@ mount -t &lt;fstype&gt; &lt;block-device&gt; <code>&lt;dir-path&gt;</code>
   </li>
 </ol>
 <p>
-  After the the volume has been mounted in the NuttX
+  After the volume has been mounted in the NuttX
   <a href="NuttxUserGuide.html#FileSystemOverview"><i>pseudo</i> filesystem</a>,
   it may be access in the same way as other objects in thefile system.
 </p>
@@ -2108,7 +2108,7 @@ nsh>
   <tr>
     <td valign="top"><b><code>CONFIG_EXAMPLES_NSH_DHCPC</code></b></td>
     <td>
-      Obtain the the IP address via DHCP.
+      Obtain the IP address via DHCP.
     </td>
   </tr>
   <tr>
diff --git a/nuttx/Documentation/NuttX.html b/nuttx/Documentation/NuttX.html
index fdde2880e..27873d291 100644
--- a/nuttx/Documentation/NuttX.html
+++ b/nuttx/Documentation/NuttX.html
@@ -1214,7 +1214,7 @@ m68k, m68hc11, m68hc12, and SuperH ports.</blockquote>
   <td>
     <p>
       This is a tougher environment.
-      In this case, the Windows native toolchain is unaware of the the
+      In this case, the Windows native toolchain is unaware of the
       Cygwin <i>sandbox</i> and, instead, operates in the native Windows environment.
       The primary difficulties with this are:
     </p>
diff --git a/nuttx/Documentation/NuttxUserGuide.html b/nuttx/Documentation/NuttxUserGuide.html
index 6a8ee1847..3fc63d6ad 100644
--- a/nuttx/Documentation/NuttxUserGuide.html
+++ b/nuttx/Documentation/NuttxUserGuide.html
@@ -170,7 +170,7 @@ paragraphs.
 </p>
 </p>
   If CONFIG_DEV_CONSOLE is defined, the first three file descriptors (corresponding
-  to stdin, stdout, stderr) will be duplicated for the the new task.
+  to stdin, stdout, stderr) will be duplicated for the new task.
   Since these file descriptors are duplicated, the child task can free close
   them or manipulate them in any way without effecting the parent task.
   File-related operations (open, close, etc.) within a task will have no effect
@@ -2430,7 +2430,7 @@ VxWorks provides the following comparable interface:
 </pre>
 <p>
   <b>Description:</b> 
-   This function returns the time remaining before the the specified watchdog expires.
+   This function returns the time remaining before the specified watchdog expires.
 </p>
 <p>
   <b>Input Parameters:</b>
@@ -4490,7 +4490,7 @@ per-thread basis and persist for the life of the calling
 thread.
 <p>
 Upon key creation, the value <I>NULL</I> will be associated with
-the the new key in all active threads.  Upon thread
+the new key in all active threads.  Upon thread
 creation, the value <I>NULL</I> will be associated with all
 defined keys in the new thread.
 <p>