From a8060d305ba102e0ef5b99fd486b962865d5b4ad Mon Sep 17 00:00:00 2001
From: liudingming <liudingming@bytedance.com>
Date: Sat, 14 Aug 2021 02:10:15 +0800
Subject: [PATCH] Tweaks `ArgsNegateSubcommands`'s doc

---
 src/build/app/settings.rs | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/src/build/app/settings.rs b/src/build/app/settings.rs
index e8cbb9d823e..13b90ea833e 100644
--- a/src/build/app/settings.rs
+++ b/src/build/app/settings.rs
@@ -407,14 +407,16 @@ pub enum AppSettings {
     /// [`ErrorKind::UnknownArgument`]: crate::ErrorKind::UnknownArgument
     AllowExternalSubcommands,
 
-    /// Specifies that use of a valid argument negates [`subcommands`] being used after. By default
-    /// `clap` allows arguments between subcommands such as
-    /// `<cmd> [cmd_args] <cmd2> [cmd2_args] <cmd3> [cmd3_args]`. This setting disables that
-    /// functionality and says that arguments can only follow the *final* subcommand. For instance
-    /// using this setting makes only the following invocations possible:
-    ///
-    /// * `<cmd> <cmd2> <cmd3> [cmd3_args]`
-    /// * `<cmd> <cmd2> [cmd2_args]`
+    /// Specifies that use of a valid argument negates [`subcommands`] being
+    /// used after. By default `clap` allows arguments between subcommands such
+    /// as `<cmd> [cmd_args] <subcmd> [subcmd_args] <subsubcmd> [subsubcmd_args]`.
+    ///
+    /// This setting disables that functionality and says that arguments can
+    /// only follow the *final* subcommand. For instance using this setting
+    /// makes only the following invocations possible:
+    ///
+    /// * `<cmd> <subcmd> <subsubcmd> [subsubcmd_args]`
+    /// * `<cmd> <subcmd> [subcmd_args]`
     /// * `<cmd> [cmd_args]`
     ///
     /// # Examples