diff --git a/crates/musli-zerocopy/src/buf/owned_buf.rs b/crates/musli-zerocopy/src/buf/owned_buf.rs index 7c5b0933d..c824b07ba 100644 --- a/crates/musli-zerocopy/src/buf/owned_buf.rs +++ b/crates/musli-zerocopy/src/buf/owned_buf.rs @@ -133,7 +133,7 @@ impl OwnedBuf { } } - /// Allocate a new buffer with the given `capacity`` and an alignment + /// Allocate a new buffer with the given `capacity` and an alignment /// matching that of `T`. /// /// The buffer must allocate for at least the given `capacity`, but might diff --git a/crates/musli-zerocopy/src/lib.rs b/crates/musli-zerocopy/src/lib.rs index 0d40cdf27..0ad724e4a 100644 --- a/crates/musli-zerocopy/src/lib.rs +++ b/crates/musli-zerocopy/src/lib.rs @@ -813,7 +813,7 @@ pub use musli_zerocopy_macros::Visit; /// /// ### `#[zero_copy(crate = )]` /// -/// Allows for specifying a custom path to the `musli_zerocopy`` crate +/// Allows for specifying a custom path to the `musli_zerocopy` crate /// (default). /// /// ``` diff --git a/crates/musli-zerocopy/src/traits.rs b/crates/musli-zerocopy/src/traits.rs index a810690f5..d6dcb6723 100644 --- a/crates/musli-zerocopy/src/traits.rs +++ b/crates/musli-zerocopy/src/traits.rs @@ -129,7 +129,7 @@ pub unsafe trait UnsizedZeroCopy: self::sealed::Sealed + Pointee { /// /// # Examples /// -/// Using `#[zero_copy(ignore)]`` on generic fields that implements +/// Using `#[zero_copy(ignore)]` on generic fields that implements /// [`ZeroSized`]: /// /// ``` diff --git a/crates/musli/src/dec2flt/mod.rs b/crates/musli/src/dec2flt/mod.rs index 12cebaff2..83887ebc8 100644 --- a/crates/musli/src/dec2flt/mod.rs +++ b/crates/musli/src/dec2flt/mod.rs @@ -34,7 +34,7 @@ //! a large-decimal representation, shifting the digits into range, calculating //! the upper significant bits and exactly round to the nearest representation. //! -//! Another aspect that needs attention is the ``RawFloat`` trait by which almost all functions +//! Another aspect that needs attention is the `RawFloat` trait by which almost all functions //! are parametrized. One might think that it's enough to parse to `f64` and cast the result to //! `f32`. Unfortunately this is not the world we live in, and this has nothing to do with using //! base two or half-to-even rounding.