Merge pull request #29 from neitsmarr/main

Update ThreadX RTOS documentation

rtos-docs/filex/chapter3.md

@@ -183,7 +183,7 @@ FileX supports both 8.3 and Windows Long File Name (LFN) name formats. In additi
 
 - **Directory Time**
 
-    The two-byte *directory time* field contains the hours, minutes, and seconds of the last change to the specified directory entry. Bits 15 through 11 contain the hours, bits 10 though 5 contain the minutes, and bits 4 though 0 contain the half seconds. Actual seconds are divided by two before being written into this field.
+    The two-byte *directory time* field contains the hours, minutes, and seconds of the last change to the specified directory entry. Bits 15 through 11 contain the hours, bits 10 through 5 contain the minutes, and bits 4 through 0 contain the half seconds. Actual seconds are divided by two before being written into this field.
 
 - **Directory Date**
 
@@ -399,11 +399,11 @@ By default, the system date and time are set to the last release date of FileX.
 
 ### System Date
 
-The FileX system date is maintained in the global ***_fx_system_date*** variable. Bits 15 through 9 contain the year offset from 1980, bits 8 through 5 contain the month offset, and bits 4 through 0 contain the day. |
+The FileX system date is maintained in the global ***_fx_system_date*** variable. Bits 15 through 9 contain the year offset from 1980, bits 8 through 5 contain the month offset, and bits 4 through 0 contain the day.
 
 ### System Time
 
-The FileX system time is maintained in the global ***_fx_system_time*** variable. Bits 15 through 11 contain the hours, bits 10 though 5 contain the minutes, and bits 4 though 0 contain the half seconds.
+The FileX system time is maintained in the global ***_fx_system_time*** variable. Bits 15 through 11 contain the hours, bits 10 through 5 contain the minutes, and bits 4 through 0 contain the half seconds.
 
 ### Periodic Time Update
 

rtos-docs/threadx/chapter2.md

@@ -160,9 +160,9 @@ For other Eclipse ThreadX products (FileX, NetX Duo, GUIX, USBX, etc.), ThreadX
 
 ### Detailed Configuration Options
 
-**TX_BYTE_POOL_ENABLE_PERFORMANCE_INFO**
+**TX_BLOCK_POOL_ENABLE_PERFORMANCE_INFO**
 
-When defined, this option enables the gathering of performance information on byte pools. By default, this option is not defined.
+When defined, this option enables the gathering of performance information on block pools. By default, this option is not defined.
 
 **TX_BYTE_POOL_ENABLE_PERFORMANCE_INFO**
 

rtos-docs/threadx/chapter3.md

@@ -710,7 +710,7 @@ The characteristics of each event flags group are found in its control block. It
 
 Event group control blocks can be located anywhere in memory, but it is most common to make the control block a global structure by defining it outside the scope of any function.
 
-### Memory Block Pools
+## Memory Block Pools
 
 Allocating memory in a fast and deterministic manner is always a challenge in real-time applications. With this in mind, ThreadX provides the ability to create and manage multiple pools of fixed-size memory blocks.
 

rtos-docs/threadx/chapter4.md

@@ -1379,7 +1379,7 @@ valid. */
 - tx_event_flags_set
 - tx_event_flags_set_notify
 
-### tx_event_flags_performance_info_get
+## tx_event_flags_performance_info_get
 
 Get event flags group performance information