Fixed Device Mode not handling Set Feature and Clear Feature Chapter 9 requests that...

[pub/lufa.git] / LUFA / SchedulerOverview.txt

diff --git a/LUFA/SchedulerOverview.txt b/LUFA/SchedulerOverview.txt
index 0a4f492..5c031fe 100644 (file)
--- a/LUFA/SchedulerOverview.txt
+++ b/LUFA/SchedulerOverview.txt
@@ -15,7 +15,7 @@
  *  hogs the processor, preventing another from running before some sort of timeout is exceeded). Unlike normal RTOS\r
  *  tasks, each LUFA scheduler task is a regular function, and thus must be designed to be called, and designed to\r
  *  return to the calling scheduler function repeatedly. Data which must be preserved between task calls should be\r
  *  hogs the processor, preventing another from running before some sort of timeout is exceeded). Unlike normal RTOS\r
  *  tasks, each LUFA scheduler task is a regular function, and thus must be designed to be called, and designed to\r
  *  return to the calling scheduler function repeatedly. Data which must be preserved between task calls should be\r

- *  declared as global or (prefferably) as a static local variable inside the task.\r
+ *  declared as global or (preferably) as a static local variable inside the task.\r

  *\r
  *  The scheduler consists of a task list, listing all the tasks which can be executed by the scheduler. Once started,\r
  *  each task is then called one after another, unless the task is stopped by another running task or interrupt.\r
  *\r
  *  The scheduler consists of a task list, listing all the tasks which can be executed by the scheduler. Once started,\r
  *  each task is then called one after another, unless the task is stopped by another running task or interrupt.\r