From 91ef2ec39450abb210c04becc582ecb46cbbf447 Mon Sep 17 00:00:00 2001
From: Nathan Hartman <hartman.nathan@gmail.com>
Date: Sun, 8 Sep 2019 15:59:14 -0600
Subject: [PATCH] Fix a few minor typos

---
 Documentation/NuttxUserGuide.html     |  4 ++--
 boards/arm/stm32/maple/Kconfig        |  2 +-
 graphics/vnc/server/vnc_fbdev.c       |  6 +++---
 include/nuttx/mutex.h                 | 12 ++++++------
 include/nuttx/semaphore.h             |  4 ++--
 include/nuttx/video/vnc.h             |  4 ++--
 libs/libc/semaphore/sem_init.c        |  4 ++--
 libs/libc/semaphore/sem_setprotocol.c |  4 ++--
 sched/semaphore/sem_setprotocol.c     |  4 ++--
 9 files changed, 22 insertions(+), 22 deletions(-)

diff --git a/Documentation/NuttxUserGuide.html b/Documentation/NuttxUserGuide.html
index 2b0167d0e7..dd4c3b64bf 100644
--- a/Documentation/NuttxUserGuide.html
+++ b/Documentation/NuttxUserGuide.html
@@ -3596,7 +3596,7 @@ interface of the same name.
 <p>
   <a name="lockingvssignaling"><b>Locking versus Signaling Semaphores</b></a>.
   Semaphores (and mutexes) may be used for many different purposes.
-  One typical use of for mutual exclusion and locking of resources:
+  One typical use is for mutual exclusion and locking of resources:
   In this usage, the thread that needs exclusive access to a resources takes the semaphore to get access to the resource.
   The same thread subsequently releases the seamphore count when it no longer needs exclusive access.
   Priority inheritance is intended just for this usage case.
@@ -3930,7 +3930,7 @@ interface of the same name.
 </p>
   The timeout will expire when the absolute time specified by <code>abstime</code> passes, as measured by the clock on which timeouts are based (that is, when the value of that clock equals or exceeds abstime), or if the absolute time specified by abstime has already been passed at the time of the call.
   This function attempts to lock the semaphore referenced by <code>sem</code>.
-  If the semaphore as already locked by another task, the calling task will not return until it either successfully acquires the lock or the call is interrupted by a signal.
+  If the semaphore is already locked by another task, the calling task will not return until it either successfully acquires the lock or the call is interrupted by a signal.
 <p>
 <b>Input Parameters:</b>
 <ul>
diff --git a/boards/arm/stm32/maple/Kconfig b/boards/arm/stm32/maple/Kconfig
index ba53be6c88..c91d290c1b 100644
--- a/boards/arm/stm32/maple/Kconfig
+++ b/boards/arm/stm32/maple/Kconfig
@@ -10,7 +10,7 @@ choice
 	default MAPLE_STANDARD if ARCH_CHIP_STM32F103RB
 	default MAPLE_MINI if ARCH_CHIP_STM32F103CB
 	---help---
-		Select the board hosting the architure.  You must first select the
+		Select the board hosting the architecture.  You must first select the
 		exact MCU part number, then the boards supporting that part will
 		be available for selection.  Use ARCH_BOARD_CUSTOM to create a new
 		board configuration.
diff --git a/graphics/vnc/server/vnc_fbdev.c b/graphics/vnc/server/vnc_fbdev.c
index 407b1f1592..2f9af0ef22 100644
--- a/graphics/vnc/server/vnc_fbdev.c
+++ b/graphics/vnc/server/vnc_fbdev.c
@@ -680,11 +680,11 @@ int up_fbinitialize(int display)
  *   nor can it call upward into NX.  So, some other logic.
  *
  *   vnc_fbinitialize() provides an optional, alternative initialization
- *   function.  It is optional becuase it need not be called.  If it is not
+ *   function.  It is optional because it need not be called.  If it is not
  *   called, however, keyboard/mouse inputs from the remote VNC client will
  *   be lost.  By calling vnc_fbinitialize(), you can provide callout
- *   functions that can be received by logic higher in the architure.  This
- *   higher level level callouts can then call nx_kbdin() or nx_mousein() on
+ *   functions that can be received by logic higher in the architecture.
+ *   These higher level callouts can then call nx_kbdin() or nx_mousein() on
  *   behalf of the VNC server.
  *
  * Input Parameters:
diff --git a/include/nuttx/mutex.h b/include/nuttx/mutex.h
index 7598983954..d5796200a1 100644
--- a/include/nuttx/mutex.h
+++ b/include/nuttx/mutex.h
@@ -75,10 +75,10 @@ extern "C"
  * Name: nxmutex_init
  *
  * Description:
- *   This function initializes the UNAMED mutex. Following a
+ *   This function initializes the UNNAMED mutex. Following a
  *   successful call to nxmutex_init(), the mutex may be used in subsequent
- *   calls to nxmutex_lock(), nxmutex_unlock(), and nxmutex_trylock().  The mutex
- *   remains usable until it is destroyed.
+ *   calls to nxmutex_lock(), nxmutex_unlock(), and nxmutex_trylock().  The
+ *   mutex remains usable until it is destroyed.
  *
  * Parameters:
  *   mutex - Semaphore to be initialized
@@ -99,10 +99,10 @@ static inline int nxmutex_init(FAR mutex_t *mutex)
  * Name: nxmutex_destroy
  *
  * Description:
- *   This function initializes the UNAMED mutex. Following a
+ *   This function initializes the UNNAMED mutex. Following a
  *   successful call to nxmutex_init(), the mutex may be used in subsequent
- *   calls to nxmutex_lock(), nxmutex_unlock(), and nxmutex_trylock().  The mutex
- *   remains usable until it is destroyed.
+ *   calls to nxmutex_lock(), nxmutex_unlock(), and nxmutex_trylock().  The
+ *   mutex remains usable until it is destroyed.
  *
  * Parameters:
  *   mutex - Semaphore to be destroyed
diff --git a/include/nuttx/semaphore.h b/include/nuttx/semaphore.h
index b30a051472..598ff46088 100644
--- a/include/nuttx/semaphore.h
+++ b/include/nuttx/semaphore.h
@@ -144,7 +144,7 @@ extern "C"
  * Name: nxsem_init
  *
  * Description:
- *   This function initializes the UNAMED semaphore sem. Following a
+ *   This function initializes the UNNAMED semaphore sem. Following a
  *   successful call to nxsem_init(), the semaphore may be used in subsequent
  *   calls to nxsem_wait(), nxsem_post(), and nxsem_trywait().  The semaphore
  *   remains usable until it is destroyed.
@@ -451,7 +451,7 @@ int sem_getprotocol(FAR sem_t *sem, FAR int *protocol);
  * Description:
  *    Set semaphore protocol attribute.
  *
- *    One particularly important use of this furnction is when a semaphore
+ *    One particularly important use of this function is when a semaphore
  *    is used for inter-task communication like:
  *
  *      TASK A                 TASK B
diff --git a/include/nuttx/video/vnc.h b/include/nuttx/video/vnc.h
index d432b9e285..3d9fa0df63 100644
--- a/include/nuttx/video/vnc.h
+++ b/include/nuttx/video/vnc.h
@@ -104,8 +104,8 @@ extern "C"
  *   function.  It is optional becuase it need not be called.  If it is not
  *   called, however, keyboard/mouse inputs from the remote VNC client will
  *   be lost.  By calling vnc_fbinitialize(), you can provide callout
- *   functions that can be received by logic higher in the architure.  This
- *   higher level level callouts can then call nx_kbdin() or nx_mousein() on
+ *   functions that can be received by logic higher in the architecture.
+ *   These higher level callouts can then call nx_kbdin() or nx_mousein() on
  *   behalf of the VNC server.
  *
  *   See also vnc_default_fbinitialize() below.
diff --git a/libs/libc/semaphore/sem_init.c b/libs/libc/semaphore/sem_init.c
index 902fee0abd..786f1f7bce 100644
--- a/libs/libc/semaphore/sem_init.c
+++ b/libs/libc/semaphore/sem_init.c
@@ -54,7 +54,7 @@
  * Name: nxsem_init
  *
  * Description:
- *   This function initializes the UNAMED semaphore sem. Following a
+ *   This function initializes the UNNAMED semaphore sem. Following a
  *   successful call to nxsem_init(), the semaphore may be used in subsequent
  *   calls to nxsem_wait(), nxsem_post(), and nxsem_trywait().  The semaphore
  *   remains usable until it is destroyed.
@@ -110,7 +110,7 @@ int nxsem_init(FAR sem_t *sem, int pshared, unsigned int value)
  * Name: sem_init
  *
  * Description:
- *   This function initializes the UNAMED semaphore sem. Following a
+ *   This function initializes the UNNAMED semaphore sem. Following a
  *   successful call to sem_init(), the semaphore may be used in subsequent
  *   calls to sem_wait(), sem_post(), and sem_trywait().  The semaphore
  *   remains usable until it is destroyed.
diff --git a/libs/libc/semaphore/sem_setprotocol.c b/libs/libc/semaphore/sem_setprotocol.c
index c391e56469..2347a1bb8d 100644
--- a/libs/libc/semaphore/sem_setprotocol.c
+++ b/libs/libc/semaphore/sem_setprotocol.c
@@ -56,7 +56,7 @@
  * Description:
  *    Set semaphore protocol attribute.
  *
- *    One particularly important use of this furnction is when a semaphore
+ *    One particularly important use of this function is when a semaphore
  *    is used for inter-task communication like:
  *
  *      TASK A                 TASK B
@@ -114,7 +114,7 @@ int nxsem_setprotocol(FAR sem_t *sem, int protocol)
  * Description:
  *    Set semaphore protocol attribute.
  *
- *    One particularly important use of this furnction is when a semaphore
+ *    One particularly important use of this function is when a semaphore
  *    is used for inter-task communication like:
  *
  *      TASK A                 TASK B
diff --git a/sched/semaphore/sem_setprotocol.c b/sched/semaphore/sem_setprotocol.c
index b8991bb1de..fdfb7f3bc1 100644
--- a/sched/semaphore/sem_setprotocol.c
+++ b/sched/semaphore/sem_setprotocol.c
@@ -58,7 +58,7 @@
  * Description:
  *    Set semaphore protocol attribute.
  *
- *    One particularly important use of this furnction is when a semaphore
+ *    One particularly important use of this function is when a semaphore
  *    is used for inter-task communication like:
  *
  *      TASK A                 TASK B
@@ -129,7 +129,7 @@ int nxsem_setprotocol(FAR sem_t *sem, int protocol)
  * Description:
  *    Set semaphore protocol attribute.
  *
- *    One particularly important use of this furnction is when a semaphore
+ *    One particularly important use of this function is when a semaphore
  *    is used for inter-task communication like:
  *
  *      TASK A                 TASK B