doc: Improve context for thread identity in scheduling

Enhance the description around reschedule points to provide more context about the current thread's identity. This update clarifies that changing the identity of the current thread involves switching the CPU's execution from one thread to another. Signed-off-by: Arrel Neumiller <[email protected]> doc: Improve context for thread identity in scheduling Enhance the description around reschedule points to provide more context about the current thread's identity. This update clarifies that changing the identity of the current thread involves switching the CPU's execution from one thread to another. Signed-off-by: Arrel Neumiller <[email protected]>
zephyrproject-rtos · Feb 26, 2025 · a55fad4 · a55fad4
1 parent 8081008
commit a55fad4
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/doc/kernel/services/scheduling/index.rst b/doc/kernel/services/scheduling/index.rst
@@ -13,8 +13,10 @@ The scheduler determines which thread is allowed to execute
 at any point in time; this thread is known as the **current thread**.
 
 There are various points in time when the scheduler is given an
-opportunity to change the identity of the current thread.  These points
-are called **reschedule points**. Some potential reschedule points are:
+opportunity to change the identity of the current thread, meaning
+when the scheduler switches the CPU's execution from one thread
+to another. These points are called **reschedule points**.
+Some potential reschedule points are:
 
 - transition of a thread from running state to a suspended or waiting
   state, for example by :c:func:`k_sem_take` or :c:func:`k_sleep`.