From 8fb0186f878f28727203d021a5a5ce21a9c06e82 Mon Sep 17 00:00:00 2001
From: RichardWGNR <171420035+RichardWGNR@users.noreply.github.com>
Date: Fri, 11 Apr 2025 00:36:00 +0500
Subject: [PATCH] Fix #4062

---
 embassy-stm32/src/can/fd/config.rs | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/embassy-stm32/src/can/fd/config.rs b/embassy-stm32/src/can/fd/config.rs
index 68161ca50..c6a66b469 100644
--- a/embassy-stm32/src/can/fd/config.rs
+++ b/embassy-stm32/src/can/fd/config.rs
@@ -328,11 +328,15 @@ pub struct FdCanConfig {
     ///
     /// Automatic retransmission is enabled by default.
     pub automatic_retransmit: bool,
-    /// Enabled or disables the pausing between transmissions
+    /// The transmit pause feature is intended for use in CAN systems where the CAN message
+    /// identifiers are permanently specified to specific values and cannot easily be changed.
     ///
-    /// This feature looses up burst transmissions coming from a single node and it protects against
-    /// "babbling idiot" scenarios where the application program erroneously requests too many
-    /// transmissions.
+    /// These message identifiers can have a higher CAN arbitration priority than other defined
+    /// messages, while in a specific application their relative arbitration priority must be inverse.
+    ///
+    /// This may lead to a case where one ECU sends a burst of CAN messages that cause
+    /// another ECU CAN messages to be delayed because that other messages have a lower
+    /// CAN arbitration priority.
     pub transmit_pause: bool,
     /// Enabled or disables the pausing between transmissions
     ///