docs: Fix a few typos

timgates42 · timgates42 · commit 92efd28f15e4 · 2021-08-31T06:16:46.000+10:00
There are small typos in:
- Ports/ARM-Cortex-M/ARMv6-M/os_cpu_c.c
- Ports/ARM-Cortex-M/ARMv7-M/os_cpu_c.c
- Ports/M14K/CodeSourcery/os_cpu_c.c
- Ports/Template/os_cpu.h
- Source/os_stat.c
- TLS/CCES/os_tls.c
- TLS/IAR/os_tls.c
- TLS/NewLib/os_tls.c
- Template/bsp_os_dt.c

Fixes:
- Should read `function` rather than `fucntion`.
- Should read `environments` rather than `enviroments`.
- Should read `alignment` rather than `aligment`.
- Should read `successful` rather than `successfu`.
- Should read `occurred` rather than `occured`.
- Should read `function` rather than `funtion`.
- Should read `assembly` rather than `assemply`.
- Should read `accidentally` rather than `accidently`.
diff --git a/Ports/ARM-Cortex-M/ARMv6-M/os_cpu_c.c b/Ports/ARM-Cortex-M/ARMv6-M/os_cpu_c.c
@@ -279,16 +279,16 @@ void  OSTaskReturnHook (OS_TCB  *p_tcb)
 *                       prior to ARMV7 and to the A, R and M architecture profiles thereafter. Special considerations
 *                       associated with ARMV7M are discussed in section 2.3.3"
 *
-*                     (1) Even if the SP 8-byte aligment is not a requirement for the ARMv7M profile, the stack is aligned
-*                         to 8-byte boundaries to support legacy execution enviroments.
+*                     (1) Even if the SP 8-byte alignment is not a requirement for the ARMv7M profile, the stack is aligned
+*                         to 8-byte boundaries to support legacy execution environments.
 *
 *                 (c) Section 5.2.1.2 from the Procedure Call Standard for the ARM
 *                     architecture states :  "The stack must also conform to the following
 *                     constraint at a public interface:
 *
 *                     (1) SP mod 8 = 0. The stack must be double-word aligned"
 *
-*                 (d) From the ARM Technical Support Knowledge Base. 8 Byte stack aligment.
+*                 (d) From the ARM Technical Support Knowledge Base. 8 Byte stack alignment.
 *
 *                     "8 byte stack alignment is a requirement of the ARM Architecture Procedure
 *                      Call Standard [AAPCS]. This specifies that functions must maintain an 8 byte
diff --git a/Ports/ARM-Cortex-M/ARMv7-M/os_cpu_c.c b/Ports/ARM-Cortex-M/ARMv7-M/os_cpu_c.c
@@ -404,16 +404,16 @@ void  OSTaskReturnHook (OS_TCB  *p_tcb)
 *                       prior to ARMV7 and to the A, R and M architecture profiles thereafter. Special considerations
 *                       associated with ARMV7M are discussed in section 2.3.3"
 *
-*                     (1) Even if the SP 8-byte aligment is not a requirement for the ARMv7M profile, the stack is aligned
-*                         to 8-byte boundaries to support legacy execution enviroments.
+*                     (1) Even if the SP 8-byte alignment is not a requirement for the ARMv7M profile, the stack is aligned
+*                         to 8-byte boundaries to support legacy execution environments.
 *
 *                 (c) Section 5.2.1.2 from the Procedure Call Standard for the ARM
 *                     architecture states :  "The stack must also conform to the following
 *                     constraint at a public interface:
 *
 *                     (1) SP mod 8 = 0. The stack must be double-word aligned"
 *
-*                 (d) From the ARM Technical Support Knowledge Base. 8 Byte stack aligment.
+*                 (d) From the ARM Technical Support Knowledge Base. 8 Byte stack alignment.
 *
 *                     "8 byte stack alignment is a requirement of the ARM Architecture Procedure
 *                      Call Standard [AAPCS]. This specifies that functions must maintain an 8 byte
diff --git a/Ports/M14K/CodeSourcery/os_cpu_c.c b/Ports/M14K/CodeSourcery/os_cpu_c.c
@@ -146,7 +146,7 @@ void  OSTaskDelHook (OS_TCB *ptcb)
 *
 * Description: This function is called when a task returns without being properly deleted.
 *
-* Arguments  : ptcb   is a pointer to the task control block of the task that was accidently returned.
+* Arguments  : ptcb   is a pointer to the task control block of the task that was accidentally returned.
 *
 * Note(s)    : 1) Interrupts are disabled during this call.
 *********************************************************************************************************
diff --git a/Ports/Template/os_cpu.h b/Ports/Template/os_cpu.h
@@ -49,7 +49,7 @@ extern  "C" {
 *
 * Note(s): OS_TASK_SW()  invokes the task level context switch.
 *
-*          (1) On some processors, this corresponds to a call to OSCtxSw() which is an assemply language
+*          (1) On some processors, this corresponds to a call to OSCtxSw() which is an assembly language
 *              function that performs the context switch.
 *
 *          (2) On some processors, you need to simulate an interrupt using a 'sowfate interrupt' or a
diff --git a/Source/os_stat.c b/Source/os_stat.c
@@ -179,7 +179,7 @@ void  OSStatReset (OS_ERR  *p_err)
 *
 * Argument(s): p_err      is a pointer to a variable that will contain an error code returned by this function.
 *
-*                             OS_ERR_NONE              The call was successfu
+*                             OS_ERR_NONE              The call was successful
 *                             OS_ERR_OS_NOT_RUNNING    If uC/OS-III is not running yet
 *
 * Returns    : none
diff --git a/TLS/CCES/os_tls.c b/TLS/CCES/os_tls.c
@@ -180,7 +180,7 @@ OS_TLS  OS_TLS_GetValue (OS_TCB     *p_tcb,
 *                                                      OS_TLS_ID   id,
 *                                                      OS_TLS      value);
 *
-*                          you can specify a NULL pointer if you don't want to have a fucntion associated with a TLS
+*                          you can specify a NULL pointer if you don't want to have a function associated with a TLS
 *                          register.  A NULL pointer (i.e. no function associated with a TLS register) is the default
 *                          value placed in OS_TLS_DestructPtrTbl[].
 *
diff --git a/TLS/IAR/os_tls.c b/TLS/IAR/os_tls.c
@@ -225,7 +225,7 @@ OS_TLS  OS_TLS_GetValue (OS_TCB     *p_tcb,
 *                                                      OS_TLS_ID   id,
 *                                                      OS_TLS      value);
 *
-*                          you can specify a NULL pointer if you don't want to have a fucntion associated with a TLS
+*                          you can specify a NULL pointer if you don't want to have a function associated with a TLS
 *                          register.  A NULL pointer (i.e. no function associated with a TLS register) is the default
 *                          value placed in OS_TLS_DestructPtrTbl[].
 *
@@ -508,7 +508,7 @@ static  void  OS_TLS_LockCreate (void  **p_lock)
                   (CPU_CHAR *) 0,
                   (OS_ERR   *)&err);
 
-    if (err != OS_ERR_NONE) {                                     /* If the mutex create funtion fail?                */
+    if (err != OS_ERR_NONE) {                                     /* If the mutex create function fail?                */
         CPU_CRITICAL_ENTER();
                                                                   /* Return the OS_TLS_LOCK in front of the list      */
         p_tls_lock->NextPtr    = OS_TLS_LockPoolListPtr;
diff --git a/TLS/NewLib/os_tls.c b/TLS/NewLib/os_tls.c
@@ -209,7 +209,7 @@ OS_TLS  OS_TLS_GetValue (OS_TCB     *p_tcb,
 *                                                      OS_TLS_ID   id,
 *                                                      OS_TLS      value);
 *
-*                          you can specify a NULL pointer if you don't want to have a fucntion associated with a TLS
+*                          you can specify a NULL pointer if you don't want to have a function associated with a TLS
 *                          register.  A NULL pointer (i.e. no function associated with a TLS register) is the default
 *                          value placed in OS_TLS_DestructPtrTbl[].
 *
diff --git a/Template/bsp_os_dt.c b/Template/bsp_os_dt.c
@@ -188,7 +188,7 @@ OS_TICK  OS_DynTickGet (void)
     tmrcnt = /* $$$$ */;                                        /* Read current timer count.                            */
 
     if (/* $$$$ */) {                                           /* Check timer interrupt flag.                          */
-        return (TickDelta);                                     /* Counter Overflow has occured.                        */
+        return (TickDelta);                                     /* Counter Overflow has occurred.                        */
     }
 
     tmrcnt = TIMER_TO_OSTICK(tmrcnt);                           /* Otherwise, the value we read is valid.               */

Original file line number	Diff line number	Diff line change
`@@ -279,16 +279,16 @@ void OSTaskReturnHook (OS_TCB *p_tcb)`
`279`	`279`	`* prior to ARMV7 and to the A, R and M architecture profiles thereafter. Special considerations`
`280`	`280`	`* associated with ARMV7M are discussed in section 2.3.3"`
`281`	`281`	`*`
`282`		`-* (1) Even if the SP 8-byte aligment is not a requirement for the ARMv7M profile, the stack is aligned`
`283`		`-* to 8-byte boundaries to support legacy execution enviroments.`
	`282`	`+* (1) Even if the SP 8-byte alignment is not a requirement for the ARMv7M profile, the stack is aligned`
	`283`	`+* to 8-byte boundaries to support legacy execution environments.`
`284`	`284`	`*`
`285`	`285`	`* (c) Section 5.2.1.2 from the Procedure Call Standard for the ARM`
`286`	`286`	`* architecture states : "The stack must also conform to the following`
`287`	`287`	`* constraint at a public interface:`
`288`	`288`	`*`
`289`	`289`	`* (1) SP mod 8 = 0. The stack must be double-word aligned"`
`290`	`290`	`*`
`291`		`-* (d) From the ARM Technical Support Knowledge Base. 8 Byte stack aligment.`
	`291`	`+* (d) From the ARM Technical Support Knowledge Base. 8 Byte stack alignment.`
`292`	`292`	`*`
`293`	`293`	`* "8 byte stack alignment is a requirement of the ARM Architecture Procedure`
`294`	`294`	`* Call Standard [AAPCS]. This specifies that functions must maintain an 8 byte`
Original file line number	Diff line number	Diff line change
`@@ -404,16 +404,16 @@ void OSTaskReturnHook (OS_TCB *p_tcb)`
`404`	`404`	`* prior to ARMV7 and to the A, R and M architecture profiles thereafter. Special considerations`
`405`	`405`	`* associated with ARMV7M are discussed in section 2.3.3"`
`406`	`406`	`*`
`407`		`-* (1) Even if the SP 8-byte aligment is not a requirement for the ARMv7M profile, the stack is aligned`
`408`		`-* to 8-byte boundaries to support legacy execution enviroments.`
	`407`	`+* (1) Even if the SP 8-byte alignment is not a requirement for the ARMv7M profile, the stack is aligned`
	`408`	`+* to 8-byte boundaries to support legacy execution environments.`
`409`	`409`	`*`
`410`	`410`	`* (c) Section 5.2.1.2 from the Procedure Call Standard for the ARM`
`411`	`411`	`* architecture states : "The stack must also conform to the following`
`412`	`412`	`* constraint at a public interface:`
`413`	`413`	`*`
`414`	`414`	`* (1) SP mod 8 = 0. The stack must be double-word aligned"`
`415`	`415`	`*`
`416`		`-* (d) From the ARM Technical Support Knowledge Base. 8 Byte stack aligment.`
	`416`	`+* (d) From the ARM Technical Support Knowledge Base. 8 Byte stack alignment.`
`417`	`417`	`*`
`418`	`418`	`* "8 byte stack alignment is a requirement of the ARM Architecture Procedure`
`419`	`419`	`* Call Standard [AAPCS]. This specifies that functions must maintain an 8 byte`
Original file line number	Diff line number	Diff line change
`@@ -146,7 +146,7 @@ void OSTaskDelHook (OS_TCB *ptcb)`
`146`	`146`	`*`
`147`	`147`	`* Description: This function is called when a task returns without being properly deleted.`
`148`	`148`	`*`
`149`		`-* Arguments : ptcb is a pointer to the task control block of the task that was accidently returned.`
	`149`	`+* Arguments : ptcb is a pointer to the task control block of the task that was accidentally returned.`
`150`	`150`	`*`
`151`	`151`	`* Note(s) : 1) Interrupts are disabled during this call.`
`152`	`152`	`*********************************************************************************************************`
Original file line number	Diff line number	Diff line change
`@@ -49,7 +49,7 @@ extern "C" {`
`49`	`49`	`*`
`50`	`50`	`* Note(s): OS_TASK_SW() invokes the task level context switch.`
`51`	`51`	`*`
`52`		`-* (1) On some processors, this corresponds to a call to OSCtxSw() which is an assemply language`
	`52`	`+* (1) On some processors, this corresponds to a call to OSCtxSw() which is an assembly language`
`53`	`53`	`* function that performs the context switch.`
`54`	`54`	`*`
`55`	`55`	`* (2) On some processors, you need to simulate an interrupt using a 'sowfate interrupt' or a`
Original file line number	Diff line number	Diff line change
`@@ -179,7 +179,7 @@ void OSStatReset (OS_ERR *p_err)`
`179`	`179`	`*`
`180`	`180`	`* Argument(s): p_err is a pointer to a variable that will contain an error code returned by this function.`
`181`	`181`	`*`
`182`		`-* OS_ERR_NONE The call was successfu`
	`182`	`+* OS_ERR_NONE The call was successful`
`183`	`183`	`* OS_ERR_OS_NOT_RUNNING If uC/OS-III is not running yet`
`184`	`184`	`*`
`185`	`185`	`* Returns : none`
Original file line number	Diff line number	Diff line change
`@@ -180,7 +180,7 @@ OS_TLS OS_TLS_GetValue (OS_TCB *p_tcb,`
`180`	`180`	`* OS_TLS_ID id,`
`181`	`181`	`* OS_TLS value);`
`182`	`182`	`*`
`183`		`-* you can specify a NULL pointer if you don't want to have a fucntion associated with a TLS`
	`183`	`+* you can specify a NULL pointer if you don't want to have a function associated with a TLS`
`184`	`184`	`* register. A NULL pointer (i.e. no function associated with a TLS register) is the default`
`185`	`185`	`* value placed in OS_TLS_DestructPtrTbl[].`
`186`	`186`	`*`
Original file line number	Diff line number	Diff line change
`@@ -209,7 +209,7 @@ OS_TLS OS_TLS_GetValue (OS_TCB *p_tcb,`
`209`	`209`	`* OS_TLS_ID id,`
`210`	`210`	`* OS_TLS value);`
`211`	`211`	`*`
`212`		`-* you can specify a NULL pointer if you don't want to have a fucntion associated with a TLS`
	`212`	`+* you can specify a NULL pointer if you don't want to have a function associated with a TLS`
`213`	`213`	`* register. A NULL pointer (i.e. no function associated with a TLS register) is the default`
`214`	`214`	`* value placed in OS_TLS_DestructPtrTbl[].`
`215`	`215`	`*`
Original file line number	Diff line number	Diff line change
`@@ -188,7 +188,7 @@ OS_TICK OS_DynTickGet (void)`
`188`	`188`	`tmrcnt = /* $$$$ /; / Read current timer count. */`
`189`	`189`
`190`	`190`	`if (/* $$$$ /) { / Check timer interrupt flag. */`
`191`		`- return (TickDelta); /* Counter Overflow has occured. */`
	`191`	`+ return (TickDelta); /* Counter Overflow has occurred. */`
`192`	`192`	`}`
`193`	`193`
`194`	`194`	`tmrcnt = TIMER_TO_OSTICK(tmrcnt); /* Otherwise, the value we read is valid. */`