Rename force-warns to force-warn

1 files changed, 3 insertions, 3 deletions

diff --git a/src/doc/unstable-book/src/compiler-flags/force-warns.md b/src/doc/unstable-book/src/compiler-flags/force-warn.md
index 0a205be096c..052de0f379e 100644
--- a/src/doc/unstable-book/src/compiler-flags/force-warns.md
+++ b/src/doc/unstable-book/src/compiler-flags/force-warn.md
@@ -1,10 +1,10 @@
-# `force-warns`
+# `force-warn`
 
 The tracking issue for this feature is: [#85512](https://github.com/rust-lang/rust/issues/85512).
 
 ------------------------
 
-This feature allows you to cause any lint to produce a warning even if the lint has a different level by default or another level is set somewhere else. For instance, the `force-warns` option can be used to make a lint (e.g., `dead_code`) produce a warning even if that lint is allowed in code with `#![allow(dead_code)]`.
+This feature allows you to cause any lint to produce a warning even if the lint has a different level by default or another level is set somewhere else. For instance, the `force-warn` option can be used to make a lint (e.g., `dead_code`) produce a warning even if that lint is allowed in code with `#![allow(dead_code)]`.
 
 ## Example
 
@@ -18,4 +18,4 @@ fn dead_function() {}
 fn main() {}
 ```
 
-We can force a warning to be produced by providing `--force-warns dead_code` to rustc.
+We can force a warning to be produced by providing `--force-warn dead_code` to rustc.