diff --git a/configs/demo9s12ne64/README.txt b/configs/demo9s12ne64/README.txt
index 120aa8cd3d1..964338357ab 100644
--- a/configs/demo9s12ne64/README.txt
+++ b/configs/demo9s12ne64/README.txt
@@ -327,7 +327,7 @@ HCS12/DEMO9S12NEC64-specific Configuration Options
 
 	CONFIG_HCS12_NONBANKED - Indicates that the target systems does not
 	  support banking.  Only short calls are made; one fixed page is
-	  presented the the paging window.  Only 48Kb of FLASH is usable
+	  presented in the paging window.  Only 48Kb of FLASH is usable
 	  in this configuration: pages 3e, 3d, then 3f will appear as a
 	  contiguous address space in memory.
 
diff --git a/configs/ea3131/src/up_fillpage.c b/configs/ea3131/src/up_fillpage.c
index f8ad374b15d..eaed9a8a2c9 100644
--- a/configs/ea3131/src/up_fillpage.c
+++ b/configs/ea3131/src/up_fillpage.c
@@ -198,7 +198,7 @@ struct pg_source_s
 
   FAR struct mtd_dev_s *mtd;
 
-  /* This the the device geometry */
+  /* This the device geometry */
 
 #ifdef CONFIG_DEBUG
   FAR struct mtd_geometry_s geo;
diff --git a/configs/ea3152/src/up_fillpage.c b/configs/ea3152/src/up_fillpage.c
index ce0d5246b90..9f470ee320e 100644
--- a/configs/ea3152/src/up_fillpage.c
+++ b/configs/ea3152/src/up_fillpage.c
@@ -198,7 +198,7 @@ struct pg_source_s
 
   FAR struct mtd_dev_s *mtd;
 
-  /* This the the device geometry */
+  /* This the device geometry */
 
 #ifdef CONFIG_DEBUG
   FAR struct mtd_geometry_s geo;
diff --git a/configs/eagle100/README.txt b/configs/eagle100/README.txt
index ab55bfe2cce..eb7db47a1c7 100644
--- a/configs/eagle100/README.txt
+++ b/configs/eagle100/README.txt
@@ -84,7 +84,7 @@ CodeSourcery on Linux
 
   If you select the CodeSourcery toolchain, the make system will assume that you
   are running a Windows version of the toolchain.  If you are running under Linux,
-  the the make will probably fail.  The fix is to edit your Make.defs file and
+  the make will probably fail.  The fix is to edit your Make.defs file and
   use something like:
 
     CROSSDEV = arm-none-eabi-
diff --git a/configs/freedom-kl25z/README.txt b/configs/freedom-kl25z/README.txt
index d7eaff648d8..ca71f59f353 100644
--- a/configs/freedom-kl25z/README.txt
+++ b/configs/freedom-kl25z/README.txt
@@ -139,10 +139,10 @@ mbed
 
   1. Connect the KL25Z to the host PC using the USB connector labeled
      SDA.
-  2. A new file system will appear call MBED; open it with Windows
+  2. A new file system will appear called MBED; open it with Windows
      Explorer (assuming that you are using Windows).
   3. Drag and drop nuttx.bin into the MBED window.  This will load the
-     nuttx.bin binary into the the KL25Z.  the MBED window will close
+     nuttx.bin binary into the KL25Z.  The MBED window will close
      then re-open and the KL25Z will be running the new code.
 
   Using the Freescale SDA debugger is essentially the same.  That
diff --git a/configs/lincoln60/src/up_buttons.c b/configs/lincoln60/src/up_buttons.c
index 76cb1f2d9e0..706d858f49c 100644
--- a/configs/lincoln60/src/up_buttons.c
+++ b/configs/lincoln60/src/up_buttons.c
@@ -211,7 +211,7 @@ xcpt_t up_irqbutton(int id, xcpt_t irqhandler)
         }
       else
         {
-          /* Disable then then detach the the old interrupt handler */
+          /* Disable then detach the old interrupt handler */
 
           up_disable_irq(irq);
           (void)irq_detach(irq);
diff --git a/configs/lpc4330-xplorer/src/up_buttons.c b/configs/lpc4330-xplorer/src/up_buttons.c
index 841f52b23f9..d99ee235617 100644
--- a/configs/lpc4330-xplorer/src/up_buttons.c
+++ b/configs/lpc4330-xplorer/src/up_buttons.c
@@ -210,7 +210,7 @@ xcpt_t up_irqbutton(int id, xcpt_t irqhandler)
         }
       else
         {
-          /* Disable then then detach the the old interrupt handler */
+          /* Disable then detach the old interrupt handler */
 
           up_disable_irq(irq);
           (void)irq_detach(irq);
diff --git a/configs/mikroe-stm32f4/README.txt b/configs/mikroe-stm32f4/README.txt
index 2fecf537c99..96ad31d5100 100644
--- a/configs/mikroe-stm32f4/README.txt
+++ b/configs/mikroe-stm32f4/README.txt
@@ -772,7 +772,7 @@ Where <subdir> is one of the following:
     In the normal case (just 'make'), make will attempt to build both user-
     and kernel-mode blobs more or less interleaved.  This actual works!
     However, for me it is very confusing so I prefer the above make command:
-    Make the user-space binaries first (pass1), then make the the kernel-space
+    Make the user-space binaries first (pass1), then make the kernel-space
     binaries (pass2)
 
     NOTES:
diff --git a/configs/mikroe-stm32f4/src/up_touchscreen.c b/configs/mikroe-stm32f4/src/up_touchscreen.c
index b1caf6cb637..095168c89e0 100644
--- a/configs/mikroe-stm32f4/src/up_touchscreen.c
+++ b/configs/mikroe-stm32f4/src/up_touchscreen.c
@@ -266,7 +266,7 @@ static int tc_poll(FAR struct file *filep, struct pollfd *fds, bool setup);
  * Private Data
  ****************************************************************************/
 
-/* This the the vtable that supports the character driver interface */
+/* This the vtable that supports the character driver interface */
 
 static const struct file_operations tc_fops =
 {
@@ -723,7 +723,7 @@ static int tc_waitsample(FAR struct tc_dev_s *priv,
         }
     }
 
-  /* Re-acquire the the semaphore that manages mutually exclusive access to
+  /* Re-acquire the semaphore that manages mutually exclusive access to
    * the device structure.  We may have to wait here.  But we have our sample.
    * Interrupts and pre-emption will be re-enabled while we wait.
    */
diff --git a/configs/mirtoo/README.txt b/configs/mirtoo/README.txt
index 5401411de64..d7589764a15 100644
--- a/configs/mirtoo/README.txt
+++ b/configs/mirtoo/README.txt
@@ -575,7 +575,7 @@ Analog Input
   19  PGED3/VREF+/CVREF+/AN0/C3INC/RPA0/CTED1/PMD7/RA0 AIN PGA117 Vout
   --- ------------------------------------------------ ----------------------------
 
-  The PGA117 driver can be enabled by setting the following the the nsh
+  The PGA117 driver can be enabled by setting the following the nsh
   configuration:
 
     CONFIG_ADC=y         : Enable support for analog input devices
diff --git a/configs/mirtoo/src/up_adc.c b/configs/mirtoo/src/up_adc.c
index 1f1fa2eb8ed..a35facbcec2 100644
--- a/configs/mirtoo/src/up_adc.c
+++ b/configs/mirtoo/src/up_adc.c
@@ -62,7 +62,7 @@
  * 19  PGED3/VREF+/CVREF+/AN0/C3INC/RPA0/CTED1/PMD7/RA0 AIN PGA117 Vout
   --- ------------------------------------------------ ----------------------------
  *
- * The PGA117 driver can be enabled by setting the following the the nsh
+ * The PGA117 driver can be enabled by setting the following the nsh
  * configuration:
  *
  *   CONFIG_ADC=y         : Enable support for analog input devices
diff --git a/configs/mirtoo/src/up_leds.c b/configs/mirtoo/src/up_leds.c
index 8eb719717d0..ff9fbc9dbe0 100644
--- a/configs/mirtoo/src/up_leds.c
+++ b/configs/mirtoo/src/up_leds.c
@@ -146,7 +146,7 @@ static const struct led_setting_s g_ledoffvalues[LED_NVALUES] =
   {LED_OFF, LED_NC,  0},
 };
 
-/* If CONFIG_ARCH_LEDS is not defined, the the user can control the LEDs in
+/* If CONFIG_ARCH_LEDS is not defined, then the user can control the LEDs in
  * any way.  The following array simply maps the PIC32MX_MIRTOO_LEDn
  * index values to the correct LED pin configuration.
  */
diff --git a/configs/ne64badge/README.txt b/configs/ne64badge/README.txt
index 788c6d746a0..fa57a563f7e 100644
--- a/configs/ne64badge/README.txt
+++ b/configs/ne64badge/README.txt
@@ -434,7 +434,7 @@ HCS12/NE64BADGE-specific Configuration Options
 
 	CONFIG_HCS12_NONBANKED - Indicates that the target systems does not
 	  support banking.  Only short calls are made; one fixed page is
-	  presented the the paging window.  Only 48Kb of FLASH is usable
+	  presented in the paging window.  Only 48Kb of FLASH is usable
 	  in this configuration: pages 3e, 3d, then 3f will appear as a
 	  contiguous address space in memory.
 
diff --git a/configs/olimex-lpc1766stk/src/up_buttons.c b/configs/olimex-lpc1766stk/src/up_buttons.c
index 6d47d2890eb..c50d9c8ae45 100644
--- a/configs/olimex-lpc1766stk/src/up_buttons.c
+++ b/configs/olimex-lpc1766stk/src/up_buttons.c
@@ -214,7 +214,7 @@ xcpt_t up_irqbutton(int id, xcpt_t irqhandler)
         }
       else
         {
-          /* Disable then then detach the the old interrupt handler */
+          /* Disable then detach the old interrupt handler */
 
           up_disable_irq(irq);
           (void)irq_detach(irq);
diff --git a/configs/olimex-lpc1766stk/src/up_ssp.c b/configs/olimex-lpc1766stk/src/up_ssp.c
index 76d56f73554..aa20e0d7951 100644
--- a/configs/olimex-lpc1766stk/src/up_ssp.c
+++ b/configs/olimex-lpc1766stk/src/up_ssp.c
@@ -163,7 +163,7 @@ static void ssp_cdirqsetup(int irq, xcpt_t irqhandler)
     }
   else
     {
-      /* Disable then then detach the the old interrupt handler */
+      /* Disable then detach the old interrupt handler */
 
       up_disable_irq(irq);
       (void)irq_detach(irq);
diff --git a/configs/open1788/README.txt b/configs/open1788/README.txt
index 1425db71899..1f12e432354 100644
--- a/configs/open1788/README.txt
+++ b/configs/open1788/README.txt
@@ -230,7 +230,7 @@ Using OpenOCD with the Olimex ARM-USB-OCD
         Open1788 board.
 
       /usr/local/share/openocd/scripts/target/lpc1788.cfg
-        This is the configuration file for the the LPC1788 target.
+        This is the configuration file for the LPC1788 target.
         It just sets up a few parameters then sources lpc17xx.cfg
 
       /usr/local/share/openocd/scripts/target/lpc17xx.cfg
@@ -373,7 +373,7 @@ CONFIGURATION
     In the normal case (just 'make'), make will attempt to build both user-
     and kernel-mode blobs more or less interleaved.  This actual works!
     However, for me it is very confusing so I prefer the above make command:
-    Make the user-space binaries first (pass1), then make the the kernel-space
+    Make the user-space binaries first (pass1), then make the kernel-space
     binaries (pass2)
 
     NOTES:
@@ -417,7 +417,7 @@ CONFIGURATION
          System.map        - Symbols in the kernel-space ELF file
 
        Loading these .elf files with OpenOCD is tricky.  It appears to me
-       that when nuttx_user.elf is loaded, it destroys the the nuttx image
+       that when nuttx_user.elf is loaded, it destroys the nuttx image
        in FLASH.  But loading the nuttx ELF does not harm the nuttx_user.elf
        in FLASH.  Conclusion:  Always load nuttx_user.elf before nuttx.
 
diff --git a/configs/open1788/src/lpc17_buttons.c b/configs/open1788/src/lpc17_buttons.c
index c820e01f5b2..e74fce1b73a 100644
--- a/configs/open1788/src/lpc17_buttons.c
+++ b/configs/open1788/src/lpc17_buttons.c
@@ -238,7 +238,7 @@ xcpt_t up_irqbutton(int id, xcpt_t irqhandler)
             }
           else
             {
-              /* Disable then then detach the the old interrupt handler */
+              /* Disable then detach the old interrupt handler */
 
               up_disable_irq(irq);
               (void)irq_detach(irq);
diff --git a/configs/pic32-starterkit/README.txt b/configs/pic32-starterkit/README.txt
index 1a42574c0c7..d295f587902 100644
--- a/configs/pic32-starterkit/README.txt
+++ b/configs/pic32-starterkit/README.txt
@@ -240,7 +240,7 @@ PIN CONFIGURATIONS                     SIGNAL NAME                ON-BOARD CONNE
 MEB Connector
 =============
 
-The following table summarizes how the pins brought the the MEB through the
+The following table summarizes how the pins brought the MEB through the
 J2 on the Ethernet Starter Kit are mapped.  This connect is J2 on the Ethernet
 Starter Kit and J3 on the MEB.
 
diff --git a/configs/pic32-starterkit/src/up_leds.c b/configs/pic32-starterkit/src/up_leds.c
index 14b924f3004..85460ae1588 100644
--- a/configs/pic32-starterkit/src/up_leds.c
+++ b/configs/pic32-starterkit/src/up_leds.c
@@ -153,7 +153,7 @@ static const struct led_setting_s g_ledoffvalues[LED_NVALUES] =
   {LED_OFF, LED_NC,  LED_NC,  LED_OFF},
 };
 
-/* If CONFIG_ARCH_LEDS is not defined, the the user can control the LEDs in
+/* If CONFIG_ARCH_LEDS is not defined, then the user can control the LEDs in
  * any way.  The following array simply maps the PIC32MX_STARTERKIT_LEDn
  * index values to the correct LED pin configuration.
  */
diff --git a/configs/pic32mx7mmb/README.txt b/configs/pic32mx7mmb/README.txt
index f64eee77b21..358b55e825b 100644
--- a/configs/pic32mx7mmb/README.txt
+++ b/configs/pic32mx7mmb/README.txt
@@ -670,7 +670,7 @@ Where <subdir> is one of the following:
     NOTE: The SD card should *not* be mounted under NSH *and* exported
     by the mass storage device!!! That can result in corruption of the
     SD card format.  This is the sequence of commands that you should
-    used to work the the SD card safely:
+    use to work with the SD card safely:
 
       mount -t vfat /dev/mmcsd0 /mnt/sdcard : Mount the SD card initially
       ...
diff --git a/configs/pic32mx7mmb/src/up_leds.c b/configs/pic32mx7mmb/src/up_leds.c
index 18793528041..57356551841 100644
--- a/configs/pic32mx7mmb/src/up_leds.c
+++ b/configs/pic32mx7mmb/src/up_leds.c
@@ -156,7 +156,7 @@ static const struct led_setting_s g_ledoffvalues[LED_NVALUES] =
   {LED_OFF, LED_NC,  LED_NC,  LED_OFF},
 };
 
-/* If CONFIG_ARCH_LEDS is not defined, the the user can control the LEDs in
+/* If CONFIG_ARCH_LEDS is not defined, then the user can control the LEDs in
  * any way.  The following array simply maps the PIC32MX_PIC32MX7MMB_LEDn
  * index values to the correct LED pin configuration.
  */
diff --git a/configs/pic32mx7mmb/src/up_spi.c b/configs/pic32mx7mmb/src/up_spi.c
index c3e90729ab0..b5676a0acd5 100644
--- a/configs/pic32mx7mmb/src/up_spi.c
+++ b/configs/pic32mx7mmb/src/up_spi.c
@@ -171,7 +171,7 @@ uint8_t pic32mx_spi1status(FAR struct spi_dev_s *dev, enum spi_dev_e devid)
         {
           ret = SPI_STATUS_PRESENT;
 
-          /* A high value indicates the the card is write protected. */
+          /* A high value indicates that the card is write protected. */
 
           if (pic32mx_gpioread(GPIO_SD_WP))
             {
diff --git a/configs/pic32mx7mmb/src/up_touchscreen.c b/configs/pic32mx7mmb/src/up_touchscreen.c
index c8fe53507a1..7babc619471 100644
--- a/configs/pic32mx7mmb/src/up_touchscreen.c
+++ b/configs/pic32mx7mmb/src/up_touchscreen.c
@@ -249,7 +249,7 @@ static int tc_poll(FAR struct file *filep, struct pollfd *fds, bool setup);
  * Private Data
  ****************************************************************************/
 
-/* This the the vtable that supports the character driver interface */
+/* This the vtable that supports the character driver interface */
 
 static const struct file_operations tc_fops =
 {
@@ -610,7 +610,7 @@ static int tc_waitsample(FAR struct tc_dev_s *priv,
         }
     }
 
-  /* Re-acquire the the semaphore that manages mutually exclusive access to
+  /* Re-acquire the semaphore that manages mutually exclusive access to
    * the device structure.  We may have to wait here.  But we have our sample.
    * Interrupts and pre-emption will be re-enabled while we wait.
    */
diff --git a/configs/sam3u-ek/README.txt b/configs/sam3u-ek/README.txt
index b178f06821f..3096599328e 100644
--- a/configs/sam3u-ek/README.txt
+++ b/configs/sam3u-ek/README.txt
@@ -516,7 +516,7 @@ Configurations
     In the normal case (just 'make'), make will attempt to build both user-
     and kernel-mode blobs more or less interleaved.  This actual works!
     However, for me it is very confusing so I prefer the above make command:
-    Make the user-space binaries first (pass1), then make the the kernel-space
+    Make the user-space binaries first (pass1), then make the kernel-space
     binaries (pass2)
 
     NOTES:
diff --git a/configs/sama5d3x-ek/README.txt b/configs/sama5d3x-ek/README.txt
index 6d76fa25c73..50b69e54105 100644
--- a/configs/sama5d3x-ek/README.txt
+++ b/configs/sama5d3x-ek/README.txt
@@ -401,7 +401,7 @@ Creating and Using NORBOOT
        (gdb) mon go                   # And jump into NOR flash
 
       The norboot program can also be configured to jump directly into
-      NOR FLASH with out requiring the the final halt and go, but since I
+      NOR FLASH without requiring the final halt and go, but since I
       have been debugging the early boot sequence, the above sequence has
       been most convenient for me.
 
@@ -489,7 +489,7 @@ Serial Consoles
     PB28 RXD1       PIO_USART1_RXD
     PB26 CTS1       PIO_USART1_CTS
 
-    NOTE: Debug TX and RX pins also go the the ADM3312EARU, but I am
+    NOTE: Debug TX and RX pins also go to the ADM3312EARU, but I am
     uncertain of the functionality.
 
     -------------------------------
diff --git a/configs/stm32f4discovery/README.txt b/configs/stm32f4discovery/README.txt
index 35e78e06799..2fda6cb661a 100644
--- a/configs/stm32f4discovery/README.txt
+++ b/configs/stm32f4discovery/README.txt
@@ -1134,7 +1134,7 @@ Where <subdir> is one of the following:
     In the normal case (just 'make'), make will attempt to build both user-
     and kernel-mode blobs more or less interleaved.  This actual works!
     However, for me it is very confusing so I prefer the above make command:
-    Make the user-space binaries first (pass1), then make the the kernel-space
+    Make the user-space binaries first (pass1), then make the kernel-space
     binaries (pass2)
 
     NOTES:
diff --git a/configs/stm32f4discovery/elf/setenv.sh b/configs/stm32f4discovery/elf/setenv.sh
index 8a1fdf06e0a..4e3e74b8491 100755
--- a/configs/stm32f4discovery/elf/setenv.sh
+++ b/configs/stm32f4discovery/elf/setenv.sh
@@ -69,7 +69,7 @@ export TOOLCHAIN_BIN="/cygdrive/c/Program Files (x86)/CodeSourcery/Sourcery G++
 # toolchain.
 #export TOOLCHAIN_BIN="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"
 
-# This the the Cygwin path to the location where I built genromfs.  If you use
+# This the Cygwin path to the location where I built genromfs.  If you use
 # the buildroot toolchain, then genromfs can probably be found in TOOLCHAIN_DIR
 export GENROMFS_PATH="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"
 
diff --git a/configs/stm32f4discovery/posix_spawn/setenv.sh b/configs/stm32f4discovery/posix_spawn/setenv.sh
index c06a15c9c9f..a3daa27b98e 100755
--- a/configs/stm32f4discovery/posix_spawn/setenv.sh
+++ b/configs/stm32f4discovery/posix_spawn/setenv.sh
@@ -69,7 +69,7 @@ export TOOLCHAIN_BIN="/cygdrive/c/Program Files (x86)/CodeSourcery/Sourcery G++
 # toolchain.
 #export TOOLCHAIN_BIN="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"
 
-# This the the Cygwin path to the location where I built genromfs.  If you use
+# This the Cygwin path to the location where I built genromfs.  If you use
 # the buildroot toolchain, then genromfs can probably be found in TOOLCHAIN_DIR
 export GENROMFS_PATH="${WD}/../misc/buildroot/build_arm_nofpu/staging_dir/bin"
 
diff --git a/configs/sure-pic32mx/src/pic32mx_spi.c b/configs/sure-pic32mx/src/pic32mx_spi.c
index 40871648fd9..ca41dd793e7 100644
--- a/configs/sure-pic32mx/src/pic32mx_spi.c
+++ b/configs/sure-pic32mx/src/pic32mx_spi.c
@@ -238,7 +238,7 @@ uint8_t pic32mx_spi2status(FAR struct spi_dev_s *dev, enum spi_dev_e devid)
         {
           ret = SPI_STATUS_PRESENT;
 
-          /* It seems that a high value indicates the the card is write
+          /* It seems that a high value indicates the card is write
            * protected.
            */
 
diff --git a/configs/ubw32/src/up_leds.c b/configs/ubw32/src/up_leds.c
index dbbffdff511..0fb6fa14a5a 100644
--- a/configs/ubw32/src/up_leds.c
+++ b/configs/ubw32/src/up_leds.c
@@ -153,7 +153,7 @@ static const struct led_setting_s g_ledoffvalues[LED_NVALUES] =
   {LED_OFF, LED_NC,  LED_NC,  LED_OFF},
 };
 
-/* If CONFIG_ARCH_LEDS is not defined, the the user can control the LEDs in
+/* If CONFIG_ARCH_LEDS is not defined, then the user can control the LEDs in
  * any way.  The following array simply maps the PIC32MX_UBW32_LEDn
  * index values to the correct LED pin configuration.
  */