doc/git-branch: fix awkward wording for "-c"
The description for "-c" is hard to parse. I think the big issue is lack of commas, but I've also reordered the words to keep the main focus point of "instead of renaming, copy" together. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jeff King committed
Feb 3, 2021 at 16:07 UTC
27dc071b9a11e953ea7d73bfdf6103940d039215
1 file changed
+2
-2
Documentation/git-branch.txt
+2
-2
@@ -78,8 +78,8 @@ renaming. If <newbranch> exists, -M must be used to force the rename
78
to happen.
79
80
The `-c` and `-C` options have the exact same semantics as `-m` and
81
-`-M`, except instead of the branch being renamed it along with its
82
-config and reflog will be copied to a new name.
81
+`-M`, except instead of the branch being renamed, it will be copied to a
82
+new name, along with its config and reflog.
83
84
With a `-d` or `-D` option, `<branchname>` will be deleted. You may
85
specify more than one branch for deletion. If the branch currently