//!
//! * Not defeating the library's anti-alias protections.
//! In particular: holding a suitable singleton ([`NoAliasSingleton`])
-//! which each `Ptr` belogns to
+//! which each `Ptr` belongs to
//! (even though there is nothing in the API
//! eg, lifetimes, to link them).
//!
///
/// Ensuring that `Ptr`s are freed at the right time is up to the caller,
/// But aliasing, and other Rust unsafe footguns,
-/// is (largely) handled by the library.
+/// are (largely) handled by the library.
/// See the [module-level documentation](crate).
pub struct Ptr<T: ?Sized> {
/// # SAFETY
PhantomData<&'a NoAliasSingleton>,
);
-/// `&mut` [`NoAliasSingleton`], but a zero-sized
+/// `&mut` [`NoAliasSingleton`], but zero-sized
///
/// See [`TokenRef`]
#[derive(Debug)]