[PATCH] docs: submitting-patches: use git switch to create branches

[Weijie Yuan <kernel@wyuan.org>]

From: Weijie Yuan <wy@wyuan.org>

Git has been promoting "git switch" since git.git commit 328c6cb853d7
(doc: promote "git switch"), and the command is no longer experimental
as of Git 2.51.0.

Suggested-by: Nguyen Duc Thinh <ducthinh100812@gmail.com>
Signed-off-by: Weijie Yuan <wy@wyuan.org>
---
 Documentation/process/submitting-patches.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index 4c28a239e8cb..63a5550bd490 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -866,7 +866,7 @@ automatically include the base tree information in your submission by
 using the ``--base`` flag. The easiest and most convenient way to use
 this option is with topical branches::
 
-    $ git checkout -t -b my-topical-branch master
+    $ git switch -t -c my-topical-branch master
     Branch 'my-topical-branch' set up to track local branch 'master'.
     Switched to a new branch 'my-topical-branch'
 
@@ -882,7 +882,7 @@ notice that it will have the ``base-commit:`` trailer at the very
 bottom, which provides the reviewer and the CI tools enough information
 to properly perform ``git am`` without worrying about conflicts::
 
-    $ git checkout -b patch-review [base-commit-id]
+    $ git switch -c patch-review [base-commit-id]
     Switched to a new branch 'patch-review'
     $ git am patches.mbox
     Applying: First Commit
-- 
2.55.0.1055.g20c0e7c0fb.dirty