Fix typo

Author: frostyplanet

README.md

@@ -21,10 +21,10 @@ Implemented with lockless in mind, low level is based on crossbeam-channel.
 
 Crossfire v1.0 has been released and used in production since 2022.12. Heavily tested on X86_64 and ARM.
 
-v2.0 has refactored the codebase and API at 2025.6. By removing generic types of ChanelShare object in sender and receiver,
+V2.0 has refactored the codebase and API at 2025.6. By removing generic types of ChanelShared object in sender and receiver,
 it's easier to remember and code.
 
-v2.0.x branch will remain in maintenance mode. Further optimization might be in v2.x_beta
+V2.0.x branch will remain in maintenance mode. Further optimization might be in v2.x_beta
 version until long run tests prove to be stable.
 
 ## Performance
@@ -113,7 +113,7 @@ While using MAsyncTx or MAsyncRx, there's memory overhead to pass along small si
 for pending async producer or consumer. Because we aim to be lockless,
 when the sending/receiving futures are cancelled (like tokio::time::timeout()),
 might trigger immediate cleanup if non-conflict conditions are met.
-Otherwise will rely on lazy cleanup. (waker will be consumed by actural message send and recv).
+Otherwise will rely on lazy cleanup. (waker will be consumed by actual message send and recv).
 
 Never the less, for close notification without sending anything,
 I suggest that use `tokio::sync::oneshot` instead.

src/lib.rs

@@ -10,10 +10,10 @@
 //!
 //! Crossfire v1.0 has been released and used in production since 2022.12. Heavily tested on X86_64 and ARM.
 //!
-//! v2.0 has refactored the codebase and API at 2025.6. By removing generic types of ChanelShare object in sender and receiver,
+//! V2.0 has refactored the codebase and API at 2025.6. By removing generic types of ChannelShared object in sender and receiver,
 //! it's easier to remember and code.
 //!
-//! v2.0.x branch will remain in maintenance mode. Future optimization might be in v2.x_beta
+//! V2.0.x branch will remain in maintenance mode. Future optimization might be in v2.x_beta
 //! version until long run tests prove to be stable.
 //!
 //! ## Performance
@@ -95,7 +95,7 @@
 //! for pending async producer or consumer. Because we aim to be lockless,
 //! when the sending/receiving futures are cancelled (like tokio::time::timeout()),
 //! might trigger immediate cleanup if non-conflict conditions are met.
-//! Otherwise will rely on lazy cleanup. (waker will be consumed by actural message send and recv).
+//! Otherwise will rely on lazy cleanup. (waker will be consumed by actual message send and recv).
 //!
 //! Never the less, for close notification without sending anything,
 //! I suggest that use `tokio::sync::oneshot` instead.

src/mpmc.rs

@@ -5,7 +5,7 @@ use crate::m_tx::*;
 
 /// Initiate a unbounded channel.
 ///
-/// Altough sender type is MTx, will never block.
+/// Although sender type is MTx, will never block.
 pub fn unbounded_async<T: Unpin>() -> (MTx<T>, MAsyncRx<T>) {
     let (tx, rx) = crossbeam::channel::unbounded();
 

src/mpsc.rs

@@ -5,7 +5,7 @@ use crate::rx::*;
 
 /// Initiate a unbounded channel.
 ///
-/// Altough sender type is MTx, will never block.
+/// Although sender type is MTx, will never block.
 pub fn unbounded_async<T: Unpin>() -> (MTx<T>, AsyncRx<T>) {
     let (tx, rx) = crossbeam::channel::unbounded();
     let send_wakers = SendWakersBlocking::new();

src/rx.rs

@@ -257,7 +257,7 @@ impl<T> AsyncRx<T> {
     }
 }
 
-/// A fixed-sized future object contructed by [AsyncRx::make_recv_future()]
+/// A fixed-sized future object constructed by [AsyncRx::make_recv_future()]
 pub struct ReceiveFuture<'a, T> {
     rx: &'a AsyncRx<T>,
     waker: Option<LockedWaker>,
@@ -268,7 +268,7 @@ impl<T> Drop for ReceiveFuture<'_, T> {
         if let Some(waker) = self.waker.take() {
             // Cancelling the future, poll is not ready
             if waker.abandon() {
-                // We are waked, but giving up to recv, should notify another receiver for safty
+                // We are waked, but giving up to recv, should notify another receiver for safety
                 self.rx.shared.on_send();
             } else {
                 self.rx.shared.clear_recv_wakers(waker.get_seq());

src/stream.rs

@@ -4,7 +4,7 @@ use futures::stream;
 use std::pin::Pin;
 use std::task::*;
 
-/// Contructed by [AsyncRx::into_stream()](crate::AsyncRx::into_stream())
+/// Constructed by [AsyncRx::into_stream()](crate::AsyncRx::into_stream())
 ///
 /// Implemented futures::stream::Stream;
 pub struct AsyncStream<T>

src/tx.rs

@@ -244,7 +244,7 @@ impl<T> AsyncTx<T> {
     }
 }
 
-/// A fixed-sized future object construted by [AsyncTx::make_send_future()]
+/// A fixed-sized future object constructed by [AsyncTx::make_send_future()]
 pub struct SendFuture<'a, T: Unpin> {
     tx: &'a AsyncTx<T>,
     item: Option<T>,
@@ -256,7 +256,7 @@ impl<T: Unpin> Drop for SendFuture<'_, T> {
         if let Some(waker) = self.waker.take() {
             // Cancelling the future, poll is not ready
             if waker.abandon() {
-                // We are waked, but give up sending, should notify another sender for safty
+                // We are waked, but give up sending, should notify another sender for safety
                 self.tx.shared.on_recv();
             } else {
                 self.tx.shared.clear_send_wakers(waker.get_seq());