Fix spelling issues.

[freertos] / FreeRTOS / Source / portable / MSVC-MingW / port.c

diff --git a/FreeRTOS/Source/portable/MSVC-MingW/port.c b/FreeRTOS/Source/portable/MSVC-MingW/port.c
index 3c685b925ba6849ace36b70a015bc5456dae4ac7..ec2341748b8539e909cabb25ec0c1c69153941b2 100644 (file)
--- a/FreeRTOS/Source/portable/MSVC-MingW/port.c
+++ b/FreeRTOS/Source/portable/MSVC-MingW/port.c
@@ -95,7 +95,7 @@ typedef struct
        /* Handle of the thread that executes the task. */\r
        void *pvThread;\r
 \r
-       /* Event used to makes sure the thread does not execute past a yield point\r
+       /* Event used to make sure the thread does not execute past a yield point\r
        between the call to SuspendThread() to suspend the thread and the\r
        asynchronous SuspendThread() operation actually being performed. */\r
        void *pvYieldEvent;\r
@@ -394,7 +394,7 @@ CONTEXT xContext;
                xInsideInterrupt = pdFALSE;\r
                WaitForMultipleObjects( sizeof( pvObjectList ) / sizeof( void * ), pvObjectList, TRUE, INFINITE );\r
 \r
-               /* Cannot be in a critical section to get here.  Tasks that exist a\r
+               /* Cannot be in a critical section to get here.  Tasks that exit a\r
                critical section will block on a yield mutex to wait for an interrupt to\r
                process if an interrupt was set pending while the task was inside the\r
                critical section.  xInsideInterrupt prevents interrupts that contain\r
@@ -456,12 +456,11 @@ CONTEXT xContext;
 \r
                                /* Ensure the thread is actually suspended by performing a\r
                                synchronous operation that can only complete when the thread is\r
-                               actually suspended.  The below code asks for dummy register\r
-                               data.  Experimentation shows that these two lines don't appear\r
+                               actually suspended.  The code below asks for dummy register\r
+                               data. Experimentation shows that these two lines don't appear\r
                                to do anything now, but according to\r
                                https://devblogs.microsoft.com/oldnewthing/20150205-00/?p=44743\r
-                               they do - so as they do not harm (slight run-time hit) they have\r
-                               been left it. */\r
+                               they do - so as they do not harm (slight run-time hit). */\r
                                xContext.ContextFlags = CONTEXT_INTEGER;\r
                                ( void ) GetThreadContext( pxThreadState->pvThread, &xContext );\r
 \r
@@ -599,7 +598,7 @@ ThreadState_t *pxThreadState = ( ThreadState_t *) *( ( size_t * ) pxCurrentTCB )
                ReleaseMutex( pvInterruptEventMutex );\r
                if( ulCriticalNesting == portNO_CRITICAL_NESTING )\r
                {\r
-                       /* An interrupt was pended so ensure to block to alow it to\r
+                       /* An interrupt was pended so ensure to block to allow it to\r
                        execute.  In most cases the (simulated) interrupt will have\r
                        executed before the next line is reached - so this is just to make\r
                        sure. */\r
@@ -669,7 +668,7 @@ int32_t lMutexNeedsReleasing, lWaitForYield = pdFALSE;
                                pvInterruptEventMutex is released as it waits on both\r
                                pvInterruptEventMutex and pvInterruptEvent.\r
                                pvInterruptEvent is only set when the simulated\r
-                               interrupt is pendeded if the interrupt is pended\r
+                               interrupt is pended if the interrupt is pended\r
                                from outside a critical section - hence it is set\r
                                here. */\r
                                SetEvent( pvInterruptEvent );\r