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 31739a04ef1ebf972d1bd4a2b544823e097aeea9..5f21577f9fcff6f0e0989daa983bdb122f7c0cf3 100644 (file)
--- 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.\r
  ******************************************************************************\r
  *\r
- * main_full() creates all the demo application tasks (including a set of tasks\r
- * that test the interrupt nesting behaviour) and a timer, then starts the\r
- * scheduler.  The web documentation provides more details of the standard demo\r
- * application tasks, which provide no particular functionality, but do provide\r
- * a good example of how to use the FreeRTOS API.\r
+ * main_full() creates a set of standard demo tasks (including a set of tasks\r
+ * that test the interrupt nesting behaviour), some application specific tasks,\r
+ * and a timer.  It then starts the scheduler.  The web documentation provides\r
+ * more details of the standard demo application tasks, which provide no\r
+ * particular functionality, but do provide a good example of how to use the\r
+ * FreeRTOS API.\r
  *\r
  * The interrupt nesting test tasks require that two timers are configured to\r
  * generate interrupts.  The interrupt service routines are defined in\r
@@ -92,7 +93,7 @@
  * without reporting any errors.  If the check timer callback discovers that a\r
  * task has either stalled, or reported an error, then it changes the period of\r
  * the check timer from the initial three seconds, to just 200ms.  The callback\r
- * function also toggles an LED each time it is called.  This provides a visual\r
+ * function also toggles the LED each time it is called.  This provides a visual\r
  * indication of the system status:  If the LED toggles every three seconds,\r
  * then no issues have been discovered.  If the LED toggles every 200ms, then\r
  * an issue has been discovered with at least one task.\r