diff --git a/crates/cli/src/bin/wasm-bindgen-test-runner/headless.rs b/crates/cli/src/bin/wasm-bindgen-test-runner/headless.rs
index c001344c602..f111902f73f 100644
--- a/crates/cli/src/bin/wasm-bindgen-test-runner/headless.rs
+++ b/crates/cli/src/bin/wasm-bindgen-test-runner/headless.rs
@@ -343,7 +343,7 @@ enum Method<'a> {
 }
 
 // Below here is a bunch of details of the WebDriver protocol implementation.
-// I'm not too too familiar with them myself, but these seem to work! I mostly
+// I'm not too familiar with them myself, but these seem to work! I mostly
 // copied the `webdriver-client` crate when writing the below bindings.
 
 impl Client {
diff --git a/crates/web-sys/webidls/enabled/Navigator.webidl b/crates/web-sys/webidls/enabled/Navigator.webidl
index 61c5b019e2e..e06c383b848 100644
--- a/crates/web-sys/webidls/enabled/Navigator.webidl
+++ b/crates/web-sys/webidls/enabled/Navigator.webidl
@@ -106,7 +106,7 @@ partial interface Navigator {
   readonly attribute Permissions permissions;
 };
 
-// Things that definitely need to be in the spec and and are not for some
+// Things that definitely need to be in the spec and are not for some
 // reason.  See https://www.w3.org/Bugs/Public/show_bug.cgi?id=22406
 partial interface Navigator {
   [Throws]
diff --git a/examples/raytrace-parallel/src/pool.rs b/examples/raytrace-parallel/src/pool.rs
index 37ef4518c00..7c7118d771c 100644
--- a/examples/raytrace-parallel/src/pool.rs
+++ b/examples/raytrace-parallel/src/pool.rs
@@ -67,7 +67,7 @@ impl WorkerPool {
     /// message is sent to it.
     fn spawn(&self) -> Result<Worker, JsValue> {
         console_log!("spawning new worker");
-        // TODO: what do do about `./worker.js`:
+        // TODO: what to do about `./worker.js`:
         //
         // * the path is only known by the bundler. How can we, as a
         //   library, know what's going on?