diff --git a/tools/cargo-hakari/README.md b/tools/cargo-hakari/README.md
index eb23293213c..6bc747f47f7 100644
--- a/tools/cargo-hakari/README.md
+++ b/tools/cargo-hakari/README.md
@@ -50,8 +50,8 @@ There are four steps you *must* take for `cargo hakari` to work properly.
 #### 1. Check in your `Cargo.lock`
 
 For hakari to work correctly, you *must* [add your `Cargo.lock` to version
-control](https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries)
-file, even if you don't have any binary crates. This is because patch version bumps in
+control](https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries),
+even if you don't have any binary crates. This is because patch version bumps in
 dependencies can add or remove features or even entire transitive dependencies.
 
 #### 2. Initialize the workspace-hack
diff --git a/tools/cargo-hakari/src/lib.rs b/tools/cargo-hakari/src/lib.rs
index 44d689c7d09..560d12cd113 100644
--- a/tools/cargo-hakari/src/lib.rs
+++ b/tools/cargo-hakari/src/lib.rs
@@ -49,8 +49,8 @@
 //! ### 1. Check in your `Cargo.lock`
 //!
 //! For hakari to work correctly, you *must* [add your `Cargo.lock` to version
-//! control](https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries)
-//! file, even if you don't have any binary crates. This is because patch version bumps in
+//! control](https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries),
+//! even if you don't have any binary crates. This is because patch version bumps in
 //! dependencies can add or remove features or even entire transitive dependencies.
 //!
 //! ### 2. Initialize the workspace-hack