Fix a few minor typos

This commit is contained in:
Nathan Hartman
2019-09-08 15:59:14 -06:00
committed by Gregory Nutt
parent f9327b6b06
commit 91ef2ec394
9 changed files with 22 additions and 22 deletions
+6 -6
View File
@@ -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
+2 -2
View File
@@ -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
+2 -2
View File
@@ -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.