master 100a2ab2460: ; * lisp/vc/vc-git.el (vc-git-print-log-follow): Doc fix.

[Eli Zaretskii]

branch: master
commit 100a2ab24605b973172b39d0b21adcdcd9907ba9
Author: Eli Zaretskii <eliz@gnu.org>
Commit: Eli Zaretskii <eliz@gnu.org>

    ; * lisp/vc/vc-git.el (vc-git-print-log-follow): Doc fix.
---
 lisp/vc/vc-git.el | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/lisp/vc/vc-git.el b/lisp/vc/vc-git.el
index f6e8e1b7042..24469f04f7c 100644
--- a/lisp/vc/vc-git.el
+++ b/lisp/vc/vc-git.el
@@ -1429,15 +1429,16 @@ This prompts for a branch to merge from."
 ;; Long explanation here:
 ;; 
https://stackoverflow.com/questions/46487476/git-log-follow-graph-skips-commits
 (defcustom vc-git-print-log-follow nil
-  "If true, use the flag `--follow' when producing single file logs.
+  "If non-nil, use the flag `--follow' when producing single file logs.
 
-It will make the printed log automatically follow the renames.
-The downsides is that the log produced this way may omit
-certain (merge) commits, and that `log-view-diff' fails on
-commits that used the previous name, in that log buffer.
+A non-nil value will make the printed log automatically follow
+the file renames.  The downsides is that the log produced this
+way may omit certain (merge) commits, and that `log-view-diff'
+fails on commits that used the previous name, in that log buffer.
 
 When this variable is nil, and the log ends with a rename, we
-print a button below that shows the log for the previous name."
+show a button below that which allows to show the log for the
+file name before the rename."
   :type 'boolean
   :version "26.1")