From: richardbarry <richardbarry@1d2547de-c912-0410-9cb9-b8ca96c0e9e2>
Date: Sun, 22 Jan 2012 21:26:47 +0000 (+0000)
Subject: Update comments in main-full.c of CM0 demo.
X-Git-Tag: V7.1.1~71
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=6dee05a7b75a78adad93a7b873d9a88795a02b13;p=freertos

Update comments in main-full.c of CM0 demo.

git-svn-id: https://svn.code.sf.net/p/freertos/code/trunk@1675 1d2547de-c912-0410-9cb9-b8ca96c0e9e2
---

diff --git a/Demo/CORTEX_M0_LPC1114_LPCXpresso/RTOSDemo/Source/main-full.c b/Demo/CORTEX_M0_LPC1114_LPCXpresso/RTOSDemo/Source/main-full.c
index 31739a04e..5f21577f9 100644
--- a/Demo/CORTEX_M0_LPC1114_LPCXpresso/RTOSDemo/Source/main-full.c
+++ b/Demo/CORTEX_M0_LPC1114_LPCXpresso/RTOSDemo/Source/main-full.c
@@ -63,11 +63,12 @@
  * required to configure the hardware, are defined in main.c.
  ******************************************************************************
  *
- * main_full() creates all the demo application tasks (including a set of tasks
- * that test the interrupt nesting behaviour) and a timer, then starts the
- * scheduler.  The web documentation provides more details of the standard demo
- * application tasks, which provide no particular functionality, but do provide
- * a good example of how to use the FreeRTOS API.
+ * main_full() creates a set of standard demo tasks (including a set of tasks
+ * that test the interrupt nesting behaviour), some application specific tasks,
+ * and a timer.  It then starts the scheduler.  The web documentation provides
+ * more details of the standard demo application tasks, which provide no
+ * particular functionality, but do provide a good example of how to use the
+ * FreeRTOS API.
  *
  * The interrupt nesting test tasks require that two timers are configured to
  * generate interrupts.  The interrupt service routines are defined in
@@ -92,7 +93,7 @@
  * without reporting any errors.  If the check timer callback discovers that a
  * task has either stalled, or reported an error, then it changes the period of
  * the check timer from the initial three seconds, to just 200ms.  The callback
- * function also toggles an LED each time it is called.  This provides a visual
+ * function also toggles the LED each time it is called.  This provides a visual
  * indication of the system status:  If the LED toggles every three seconds,
  * then no issues have been discovered.  If the LED toggles every 200ms, then
  * an issue has been discovered with at least one task.