diff --git a/ch02.md b/ch02.md index 0ee9e77..8190d41 100644 --- a/ch02.md +++ b/ch02.md @@ -440,7 +440,7 @@ procedure to create a new project: | event\_groups.c | FreeRTOS/Source | | stream\_buffer.c | FreeRTOS/Source | | All C and assembler files | FreeRTOS/Source/portable/\[compiler\]/\[architecture\] | -| *heap\_n.c* | *FreeRTOS/Source/portable/MemMang, where n is either 1, 2, 3, 4 or 5* | +| heap\_n.c | FreeRTOS/Source/portable/MemMang, where n is either 1, 2, 3, 4 or 5 | *Table 1 FreeRTOS source files to include in the project* * * * diff --git a/ch03.md b/ch03.md index c6e774d..b4262e6 100644 --- a/ch03.md +++ b/ch03.md @@ -833,7 +833,7 @@ These functions will be explained in the appropriate chapters in this book. ### 3.4.2 Static Internal Kernel Memory -When you enable the static memory allocator, the idle task and the timer task (if enabled) will use static memory supplied +When the static memory allocator is enabled, the idle task and the timer task (if enabled) will use static memory supplied by user functions. These user functions are: - `vApplicationGetTimerTaskMemory` diff --git a/ch05.md b/ch05.md index 3c51d27..62af52f 100644 --- a/ch05.md +++ b/ch05.md @@ -631,7 +631,7 @@ It is common in FreeRTOS designs for a task to receive data from more than one source. The receiving task needs to know where the data came from to determine what to do with it. An easy design pattern to achieve that uses a single queue to transfer structures that contain both the -data value and data source, as demonstrated in Figure 34. +data value and data source, as demonstrated in Figure 5.4. @@ -640,7 +640,7 @@ data value and data source, as demonstrated in Figure 34. *Figure 5.4 An example scenario where structures are sent on a queue* * * * -Referring to Figure 34: +Referring to Figure 5.4: - The created queue holds structures of type `Data_t`. The structure allows both a data value and an enumerated type indicating what the