chore: fix some minor issues in comments

inout/src/reserved.rs

@@ -95,7 +95,7 @@ impl<T> InOutBufReserved<'_, '_, T> {
     }
 
     /// Split buffer into `InOutBuf` with input length and mutable slice pointing to
-    /// the reamining reserved suffix.
+    /// the remaining reserved suffix.
     pub fn split_reserved(&mut self) -> (InOutBuf<'_, '_, T>, &mut [T]) {
         let in_len = self.get_in_len();
         let out_len = self.get_out_len();

opaque-debug/src/lib.rs

@@ -20,7 +20,7 @@
 //! assert_eq!(format!("{:?}", val), "CryptoStuff { ... }")
 //! ```
 //!
-//! The macro also support generic paramters:
+//! The macro also support generic parameters:
 //! ```
 //! pub struct GenericCryptoStuff<K> {
 //!     key: K,

zeroize/src/lib.rs

@@ -400,7 +400,7 @@ where
             // Ensures self is None and that the value was dropped. Without the take, the drop
             // of the (zeroized) value isn't called, which might lead to a leak or other
             // unexpected behavior. For example, if this were Option<Vec<T>>, the above call to
-            // zeroize would not free the allocated memory, but the the `take` call will.
+            // zeroize would not free the allocated memory, but the `take` call will.
             self.take();
         }
 
@@ -617,7 +617,7 @@ impl Zeroize for CString {
     }
 }
 
-/// `Zeroizing` is a a wrapper for any `Z: Zeroize` type which implements a
+/// `Zeroizing` is a wrapper for any `Z: Zeroize` type which implements a
 /// `Drop` handler which zeroizes dropped values.
 #[derive(Debug, Default, Eq, PartialEq)]
 pub struct Zeroizing<Z: Zeroize>(Z);