aboutsummaryrefslogtreecommitdiff
path: root/embassy-sync
diff options
context:
space:
mode:
authorStefan Gehr <[email protected]>2024-02-03 14:56:31 +0100
committerStefan Gehr <[email protected]>2024-02-03 14:56:31 +0100
commitb9d0069671b33107e35af6bdaa662e9c7be8e3f9 (patch)
treeb6c4d3d407a1cf4eb05985d20915ba6a07db8182 /embassy-sync
parent88e7e1ceb9882a25548ecd8f69c8be5ba26ca6a3 (diff)
correct spelling of the word "receive"
Diffstat (limited to 'embassy-sync')
-rw-r--r--embassy-sync/src/priority_channel.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/embassy-sync/src/priority_channel.rs b/embassy-sync/src/priority_channel.rs
index bd75c0135..e77678c24 100644
--- a/embassy-sync/src/priority_channel.rs
+++ b/embassy-sync/src/priority_channel.rs
@@ -325,7 +325,7 @@ where
325/// 325///
326/// Sent data may be reordered based on their priorty within the channel. 326/// Sent data may be reordered based on their priorty within the channel.
327/// For example, in a [`Max`](heapless::binary_heap::Max) [`PriorityChannel`] 327/// For example, in a [`Max`](heapless::binary_heap::Max) [`PriorityChannel`]
328/// containing `u32`'s, data sent in the following order `[1, 2, 3]` will be recieved as `[3, 2, 1]`. 328/// containing `u32`'s, data sent in the following order `[1, 2, 3]` will be received as `[3, 2, 1]`.
329pub struct PriorityChannel<M, T, K, const N: usize> 329pub struct PriorityChannel<M, T, K, const N: usize>
330where 330where
331 T: Ord, 331 T: Ord,