Update src/ipc/readme.md

Grammar: “Routing incoming platform interrupts into the Zephyr or SOF thread domains schedule” reads incorrectly ("schedule" is a noun/verb mismatch).

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Liam Girdwood <lgirdwood@gmail.com>

Author: lgirdwood

src/ipc/readme.md

@@ -7,7 +7,7 @@ This directory contains the common foundation for all Inter-Processor Communicat
 The Core IPC layer is completely agnostic to the specific structure or content of the messages (whether they are IPC3 stream commands or IPC4 pipeline messages). Its primary responsibilities are:
 
 1. **Message State Management**: Tracking if a message is being processed, queued, or completed.
-2. **Interrupt Bridging**: Routing incoming platform interrupts into the Zephyr or SOF thread domains schedule.
+2. **Interrupt Bridging**: Routing incoming platform interrupts into the Zephyr or SOF thread-domain scheduler.
 3. **Queueing**: Safe traversal and delayed processing capabilities via `k_work` items or SOF scheduler tasks.
 4. **Platform Acknowledgment**: Signaling the hardware mailbox layers to confirm receipt or signal completion out entirely.