chore: remove redundant word in comment

Signed-off-by: whosehang <[email protected]>

Author: whosehang

crates/c-api/doxygen.conf.in

@@ -585,7 +585,7 @@ INTERNAL_DOCS          = NO
 # filesystem is case sensitive (i.e. it supports files in the same directory
 # whose names only differ in casing), the option must be set to YES to properly
 # deal with such files in case they appear in the input. For filesystems that
-# are not case sensitive the option should be be set to NO to properly deal with
+# are not case sensitive the option should be set to NO to properly deal with
 # output files written for symbols that only differ in casing, such as for two
 # classes, one named CLASS and the other named Class, and to also support
 # references to files without having to specify the exact matching casing. On

crates/fiber/src/stackswitch.rs

@@ -34,7 +34,7 @@ cfg_if::cfg_if! {
 }
 
 /// A helper module to get reeported above in each case that we actually have
-/// stack-switching routines available in in line asm. The fall-through case
+/// stack-switching routines available in line asm. The fall-through case
 /// though reexports the `unsupported` module instead.
 #[allow(
     dead_code,

crates/wasi-http/wit/deps/http/types.wit

@@ -170,7 +170,7 @@ interface types {
   /// A `fields` may be mutable or immutable. A `fields` created using the
   /// constructor, `from-list`, or `clone` will be mutable, but a `fields`
   /// resource given by other means (including, but not limited to,
-  /// `incoming-request.headers`, `outgoing-request.headers`) might be be
+  /// `incoming-request.headers`, `outgoing-request.headers`) might be
   /// immutable. In an immutable fields, the `set`, `append`, and `delete`
   /// operations will fail with `header-error.immutable`.
   @since(version = 0.2.0)

crates/wasmtime/src/runtime/store/async_.rs

@@ -344,7 +344,7 @@ impl StoreOpaque {
         // be ready for TLS to change while we're executing wasm code between
         // suspension points).
         //
-        // While somewhat onerous it shouldn't be too too hard (the TLS bit is
+        // While somewhat onerous it shouldn't be too hard (the TLS bit is
         // the hardest bit so far). This does mean, though, that no user should
         // ever have to worry about the `Send`-ness of Wasmtime. If rustc says
         // it's ok, then it's ok.