diff --git a/cli/src/cli_util.rs b/cli/src/cli_util.rs
index b9b6e1278b..cbba0a0a6f 100644
--- a/cli/src/cli_util.rs
+++ b/cli/src/cli_util.rs
@@ -2936,7 +2936,7 @@ pub struct GlobalArgs {
     /// command. The working copy is also updated at the end of the command,
     /// if the command modified the working-copy commit (`@`). If you want
     /// to avoid snapshotting the working copy and instead see a possibly
-    /// stale working copy commit, you can use `--ignore-working-copy`.
+    /// stale working-copy commit, you can use `--ignore-working-copy`.
     /// This may be useful e.g. in a command prompt, especially if you have
     /// another process that commits the working copy.
     ///
diff --git a/cli/tests/cli-reference@.md.snap b/cli/tests/cli-reference@.md.snap
index 65f7a86caa..d57a9cdc89 100644
--- a/cli/tests/cli-reference@.md.snap
+++ b/cli/tests/cli-reference@.md.snap
@@ -168,7 +168,7 @@ To get started, see the tutorial at https://martinvonz.github.io/jj/latest/tutor
    By default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory.
 * `--ignore-working-copy` — Don't snapshot the working copy, and don't update it
 
-   By default, Jujutsu snapshots the working copy at the beginning of every command. The working copy is also updated at the end of the command, if the command modified the working-copy commit (`@`). If you want to avoid snapshotting the working copy and instead see a possibly stale working copy commit, you can use `--ignore-working-copy`. This may be useful e.g. in a command prompt, especially if you have another process that commits the working copy.
+   By default, Jujutsu snapshots the working copy at the beginning of every command. The working copy is also updated at the end of the command, if the command modified the working-copy commit (`@`). If you want to avoid snapshotting the working copy and instead see a possibly stale working-copy commit, you can use `--ignore-working-copy`. This may be useful e.g. in a command prompt, especially if you have another process that commits the working copy.
 
    Loading the repository at a specific operation with `--at-operation` implies `--ignore-working-copy`.
 * `--ignore-immutable` — Allow rewriting immutable commits