diff --git a/src/doc/man/cargo-yank.md b/src/doc/man/cargo-yank.md
index b4d549c489b..e8c28b7176f 100644
--- a/src/doc/man/cargo-yank.md
+++ b/src/doc/man/cargo-yank.md
@@ -51,7 +51,7 @@ requirements, following a given release being yanked:
 ### When to yank
 
 Crates should only be yanked in exceptional circumstances, for example, an
-accidental publish, an unintentional SemVer breakages, or a significantly
+accidental publish, unintentional SemVer breakages, or a significantly
 broken and unusable crate. In the case of security vulnerabilities, [RustSec]
 is typically a less disruptive mechanism to inform users and encourage them
 to upgrade, and avoids the possibility of significant downstream disruption
diff --git a/src/doc/man/generated_txt/cargo-yank.txt b/src/doc/man/generated_txt/cargo-yank.txt
index c4c63700931..0be726fae1c 100644
--- a/src/doc/man/generated_txt/cargo-yank.txt
+++ b/src/doc/man/generated_txt/cargo-yank.txt
@@ -55,7 +55,7 @@ DESCRIPTION
 
    When to yank
        Crates should only be yanked in exceptional circumstances, for example,
-       an accidental publish, an unintentional SemVer breakages, or a
+       an accidental publish, unintentional SemVer breakages, or a
        significantly broken and unusable crate. In the case of security
        vulnerabilities, RustSec <https://rustsec.org/> is typically a less
        disruptive mechanism to inform users and encourage them to upgrade, and
diff --git a/src/doc/src/commands/cargo-yank.md b/src/doc/src/commands/cargo-yank.md
index f975704d235..18de0843c82 100644
--- a/src/doc/src/commands/cargo-yank.md
+++ b/src/doc/src/commands/cargo-yank.md
@@ -51,7 +51,7 @@ requirements, following a given release being yanked:
 ### When to yank
 
 Crates should only be yanked in exceptional circumstances, for example, an
-accidental publish, an unintentional SemVer breakages, or a significantly
+accidental publish, unintentional SemVer breakages, or a significantly
 broken and unusable crate. In the case of security vulnerabilities, [RustSec]
 is typically a less disruptive mechanism to inform users and encourage them
 to upgrade, and avoids the possibility of significant downstream disruption
diff --git a/src/etc/man/cargo-yank.1 b/src/etc/man/cargo-yank.1
index 44dafed6fbb..a5b2d7dd5f1 100644
--- a/src/etc/man/cargo-yank.1
+++ b/src/etc/man/cargo-yank.1
@@ -82,7 +82,7 @@ T}
 .sp
 .SS "When to yank"
 Crates should only be yanked in exceptional circumstances, for example, an
-accidental publish, an unintentional SemVer breakages, or a significantly
+accidental publish, unintentional SemVer breakages, or a significantly
 broken and unusable crate. In the case of security vulnerabilities, \fIRustSec\fR <https://rustsec.org/>
 is typically a less disruptive mechanism to inform users and encourage them
 to upgrade, and avoids the possibility of significant downstream disruption