diff --git a/Documentation/NfsHowto.html b/Documentation/NfsHowto.html
index ec90bbb9260..9de0ee679fd 100644
--- a/Documentation/NfsHowto.html
+++ b/Documentation/NfsHowto.html
@@ -118,7 +118,7 @@ int mount(const char *source, const char *target, const char *filesystemtype, un
    <code>mount()</code> attaches the filesystem specified by the <code>source</code> block device name into the root file system at the path specified by <code>target</code>.
 </p>
 <p>
-  <b>Input Paramters</b>:
+  <b>Input Parameters</b>:
   <ul>
     <li><code>source</code>.  A null-terminated string providing the fill path to a block driver in the NuttX pseudo-file system.
     <li><code>target</code>.  The location in the NuttX pseudo-file system where the volume will be mounted.
@@ -132,7 +132,7 @@ int mount(const char *source, const char *target, const char *filesystemtype, un
   Zero is returned on success; -1 is returned on an error and <code>errno</code> is set appropriately:
   <ul>
     <li><code>EACCES</code>.
-      A component of a path was not searchable or mounting a read-onlyfilesystem was attempted without giving the <code>MS_RDONLY</code> flag.
+      A component of a path was not searchable or mounting a read-only filesystem was attempted without giving the <code>MS_RDONLY</code> flag.
     </li>
     <li><code>EBUSY</code>.
       <code>source</code> is already  mounted.
@@ -315,7 +315,7 @@ This is a test
 directory machine1(option11,option12)
 </pre></ul>
 <p>
-  So for our example we export <coce>/export</code> to the client 10.0.0.2 add the entry:
+  So for our example we export <code>/export</code> to the client 10.0.0.2 add the entry:
 </p>
 <ul><pre>
 /export 10.0.0.2(rw)
diff --git a/Documentation/acronyms.txt b/Documentation/acronyms.txt
index 56033796f2a..20448d79075 100644
--- a/Documentation/acronyms.txt
+++ b/Documentation/acronyms.txt
@@ -91,7 +91,7 @@ RTC    Real Time Clock
 RTCC   Real Time Clock/Calendar
 RTOS   Real Time Operating System
 SAIC   Secure Advanced Interrupt Controller (Atmel SAM)
-SCI    Serial Communications Inteface
+SCI    Serial Communications Interface
 SD     Secure Digital (flash memory)
 SDHC   Secure Digital High Capacity (flash memory),
        Secure Digital Host Controller (hardware)
@@ -99,7 +99,7 @@ SDIO   Secure Digital I/O
 SDRAM  Synchronous Dynamic Random Access Memory
 SLCD   Segment Liquid Crystal Display
 SMC    Static Memory Controller (hardware)
-SPI    Serial Periperhal Interface
+SPI    Serial Peripheral Interface
 SPRNG  Scalable Parallel Random Number Generator
 SRAM   Static RAM
 SYSLOG System Log
@@ -117,5 +117,5 @@ WAN    Wide Area Network (networking)
 WLAN   Wireless Local Area Network (networking)
 WPAN   Wireless Personal Area Network (networking)
 WDT    Watchdog Timer (hardware)
-XIP    eExecute In Place
+XIP    eXecute In Place
 XDMAC  Extended DMA Controller (Atmel)
diff --git a/arch/sim/src/up_initialize.c b/arch/sim/src/up_initialize.c
index 7ec962b9b99..2621e43e7a5 100644
--- a/arch/sim/src/up_initialize.c
+++ b/arch/sim/src/up_initialize.c
@@ -235,7 +235,7 @@ void up_initialize(void)
 #endif
 
 #if defined(USE_DEVCONSOLE)
-  /* Start the sumulated UART device */
+  /* Start the simulated UART device */
 
   simuart_start();
 
diff --git a/configs/dk-tm4c129x/src/tm4c_boot.c b/configs/dk-tm4c129x/src/tm4c_boot.c
index be8a5d69a6a..95f0012bf8a 100644
--- a/configs/dk-tm4c129x/src/tm4c_boot.c
+++ b/configs/dk-tm4c129x/src/tm4c_boot.c
@@ -99,7 +99,7 @@ void tiva_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/flipnclick-pic32mz/src/pic32mz_boot.c b/configs/flipnclick-pic32mz/src/pic32mz_boot.c
index 514ea7186b6..f920dc05d27 100644
--- a/configs/flipnclick-pic32mz/src/pic32mz_boot.c
+++ b/configs/flipnclick-pic32mz/src/pic32mz_boot.c
@@ -87,7 +87,7 @@ void pic32mz_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/nucleo-f410rb/src/stm32_boot.c b/configs/nucleo-f410rb/src/stm32_boot.c
index b1a5d53f9da..901e7a62e1d 100644
--- a/configs/nucleo-f410rb/src/stm32_boot.c
+++ b/configs/nucleo-f410rb/src/stm32_boot.c
@@ -92,7 +92,7 @@ void stm32_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/nucleo-f446re/src/stm32_boot.c b/configs/nucleo-f446re/src/stm32_boot.c
index d39b37c8aad..043d650dc6e 100644
--- a/configs/nucleo-f446re/src/stm32_boot.c
+++ b/configs/nucleo-f446re/src/stm32_boot.c
@@ -100,7 +100,7 @@ void stm32_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will
- *   be called immediately after up_intiialize() is called and just before
+ *   be called immediately after up_initialize() is called and just before
  *   the initial application is started.  This additional initialization
  *   phase may be used, for example, to initialize board-specific device
  *   drivers.
diff --git a/configs/nucleo-l432kc/src/stm32_boot.c b/configs/nucleo-l432kc/src/stm32_boot.c
index f3e7b8596c5..c8b42ba14b3 100644
--- a/configs/nucleo-l432kc/src/stm32_boot.c
+++ b/configs/nucleo-l432kc/src/stm32_boot.c
@@ -107,7 +107,7 @@ void stm32l4_board_initialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/nucleo-l476rg/src/stm32_boot.c b/configs/nucleo-l476rg/src/stm32_boot.c
index 1b2054bcf39..d6e86753667 100644
--- a/configs/nucleo-l476rg/src/stm32_boot.c
+++ b/configs/nucleo-l476rg/src/stm32_boot.c
@@ -98,7 +98,7 @@ void stm32l4_board_initialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/olimex-stm32-p207/src/stm32_boot.c b/configs/olimex-stm32-p207/src/stm32_boot.c
index 29fbb26a57d..6d77c370dc6 100644
--- a/configs/olimex-stm32-p207/src/stm32_boot.c
+++ b/configs/olimex-stm32-p207/src/stm32_boot.c
@@ -96,7 +96,7 @@ void stm32_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/olimexino-stm32/src/stm32_boot.c b/configs/olimexino-stm32/src/stm32_boot.c
index a0d04cfbf73..418cf4fe8da 100644
--- a/configs/olimexino-stm32/src/stm32_boot.c
+++ b/configs/olimexino-stm32/src/stm32_boot.c
@@ -121,7 +121,7 @@ void stm32_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/pcduino-a10/src/a1x_boot.c b/configs/pcduino-a10/src/a1x_boot.c
index 0cc78220ea2..3658d4a5e51 100644
--- a/configs/pcduino-a10/src/a1x_boot.c
+++ b/configs/pcduino-a10/src/a1x_boot.c
@@ -81,7 +81,7 @@ void a1x_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/pic32mz-starterkit/src/pic32mz_boot.c b/configs/pic32mz-starterkit/src/pic32mz_boot.c
index 90b9a781732..406dd039979 100644
--- a/configs/pic32mz-starterkit/src/pic32mz_boot.c
+++ b/configs/pic32mz-starterkit/src/pic32mz_boot.c
@@ -95,7 +95,7 @@ void pic32mz_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/sam4e-ek/src/sam_boot.c b/configs/sam4e-ek/src/sam_boot.c
index 816b5f1221a..18aeb8f7517 100644
--- a/configs/sam4e-ek/src/sam_boot.c
+++ b/configs/sam4e-ek/src/sam_boot.c
@@ -133,7 +133,7 @@ void sam_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/sama5d2-xult/src/sam_boot.c b/configs/sama5d2-xult/src/sam_boot.c
index f6958ace8b9..954ca065d58 100644
--- a/configs/sama5d2-xult/src/sam_boot.c
+++ b/configs/sama5d2-xult/src/sam_boot.c
@@ -83,7 +83,7 @@ void sam_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/sama5d3-xplained/src/sam_boot.c b/configs/sama5d3-xplained/src/sam_boot.c
index f3dc140245a..0d3fb8b2b8e 100644
--- a/configs/sama5d3-xplained/src/sam_boot.c
+++ b/configs/sama5d3-xplained/src/sam_boot.c
@@ -138,7 +138,7 @@ void sam_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/sama5d3x-ek/src/sam_boot.c b/configs/sama5d3x-ek/src/sam_boot.c
index 8415d92db94..19074ebeede 100644
--- a/configs/sama5d3x-ek/src/sam_boot.c
+++ b/configs/sama5d3x-ek/src/sam_boot.c
@@ -138,7 +138,7 @@ void sam_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/sama5d4-ek/src/sam_boot.c b/configs/sama5d4-ek/src/sam_boot.c
index 0eb87513427..e2416b44b1d 100644
--- a/configs/sama5d4-ek/src/sam_boot.c
+++ b/configs/sama5d4-ek/src/sam_boot.c
@@ -139,7 +139,7 @@ void sam_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/sim/src/sim_boot.c b/configs/sim/src/sim_boot.c
index f71ac505df3..7cc7fe0fa28 100644
--- a/configs/sim/src/sim_boot.c
+++ b/configs/sim/src/sim_boot.c
@@ -53,7 +53,7 @@
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/stm32f411e-disco/src/stm32_boot.c b/configs/stm32f411e-disco/src/stm32_boot.c
index ec5bae002be..fb69bc6f7d0 100644
--- a/configs/stm32f411e-disco/src/stm32_boot.c
+++ b/configs/stm32f411e-disco/src/stm32_boot.c
@@ -97,7 +97,7 @@ void stm32_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/stm32f429i-disco/src/stm32_boot.c b/configs/stm32f429i-disco/src/stm32_boot.c
index fa45f776757..102883f54e4 100644
--- a/configs/stm32f429i-disco/src/stm32_boot.c
+++ b/configs/stm32f429i-disco/src/stm32_boot.c
@@ -114,7 +114,7 @@ void stm32_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/stm32l476-mdk/src/stm32_boot.c b/configs/stm32l476-mdk/src/stm32_boot.c
index e70cf26ce9b..652423d9497 100644
--- a/configs/stm32l476-mdk/src/stm32_boot.c
+++ b/configs/stm32l476-mdk/src/stm32_boot.c
@@ -89,7 +89,7 @@ void stm32l4_board_initialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/stm32l476vg-disco/src/stm32_boot.c b/configs/stm32l476vg-disco/src/stm32_boot.c
index e9a5f99258d..956342e434e 100644
--- a/configs/stm32l476vg-disco/src/stm32_boot.c
+++ b/configs/stm32l476vg-disco/src/stm32_boot.c
@@ -98,7 +98,7 @@ void stm32l4_board_initialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/stm32l4r9ai-disco/src/stm32_boot.c b/configs/stm32l4r9ai-disco/src/stm32_boot.c
index 125a8c68bd1..6983e96c75a 100644
--- a/configs/stm32l4r9ai-disco/src/stm32_boot.c
+++ b/configs/stm32l4r9ai-disco/src/stm32_boot.c
@@ -94,7 +94,7 @@ void stm32l4_board_initialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/tm4c123g-launchpad/src/tm4c_boot.c b/configs/tm4c123g-launchpad/src/tm4c_boot.c
index 7b15170a15f..b9396ac3579 100644
--- a/configs/tm4c123g-launchpad/src/tm4c_boot.c
+++ b/configs/tm4c123g-launchpad/src/tm4c_boot.c
@@ -99,7 +99,7 @@ void tiva_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/configs/tm4c1294-launchpad/src/tm4c_boot.c b/configs/tm4c1294-launchpad/src/tm4c_boot.c
index 34f7d0e42ee..777352f27b0 100644
--- a/configs/tm4c1294-launchpad/src/tm4c_boot.c
+++ b/configs/tm4c1294-launchpad/src/tm4c_boot.c
@@ -99,7 +99,7 @@ void tiva_boardinitialize(void)
  *   If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional
  *   initialization call will be performed in the boot-up sequence to a
  *   function called board_late_initialize().  board_late_initialize() will be
- *   called immediately after up_intiialize() is called and just before the
+ *   called immediately after up_initialize() is called and just before the
  *   initial application is started.  This additional initialization phase
  *   may be used, for example, to initialize board-specific device drivers.
  *
diff --git a/sched/sched/sched_cpuload.c b/sched/sched/sched_cpuload.c
index a11986c3c1c..dfc356bb87f 100644
--- a/sched/sched/sched_cpuload.c
+++ b/sched/sched/sched_cpuload.c
@@ -52,6 +52,7 @@
 /****************************************************************************
  * Pre-processor Definitions
  ****************************************************************************/
+
 /* Are we using the system timer, or an external clock?  Get the rate
  * of the sampling in ticks per second for the selected timer.
  */
@@ -66,7 +67,7 @@
 #endif
 
 /* When g_cpuload_total exceeds the following time constant, the load and
- * the counds will be scaled back by two.  In the CONFIG_SMP, g_cpuload_total
+ * the counts will be scaled back by two.  In the CONFIG_SMP, g_cpuload_total
  * will be incremented multiple times per tick.
  */