Documentation: use lowercase for shallow and deep threading

Even when a sentence is started with 'shallow' or 'deep' use the
lowercase version to maintain consistency.

Signed-off-by: Stephen Boyd <bebarino@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

diff --git a/Documentation/config.txt b/Documentation/config.txt
index a9055c94ac95439700e61333785b34bdeae861ad..0c1224a01726263c15fcfb7448a5f5c75256e764 100644 (file)
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -745,11 +745,11 @@ format.pretty::
 
 format.thread::
        The default threading style for 'git-format-patch'.  Can be
 
 format.thread::
        The default threading style for 'git-format-patch'.  Can be

-       either a boolean value, `shallow` or `deep`.  'Shallow'
+       either a boolean value, `shallow` or `deep`.  `shallow`

        threading makes every mail a reply to the head of the series,
        where the head is chosen from the cover letter, the
        `\--in-reply-to`, and the first patch mail, in this order.
        threading makes every mail a reply to the head of the series,
        where the head is chosen from the cover letter, the
        `\--in-reply-to`, and the first patch mail, in this order.

-       'Deep' threading makes every mail a reply to the previous one.
+       `deep` threading makes every mail a reply to the previous one.

        A true boolean value is the same as `shallow`, and a false
        value disables threading.
 
        A true boolean value is the same as `shallow`, and a false
        value disables threading.
 

diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index 5eddca92c4b7200dbb01abb4b6203c77262fc997..4a43c64bb8b3d97809951f867b9ccff9380b08ba 100644 (file)
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -128,9 +128,9 @@ include::diff-options.txt[]
        the Message-Id header to reference.
 +
 The optional <style> argument can be either `shallow` or `deep`.
        the Message-Id header to reference.
 +
 The optional <style> argument can be either `shallow` or `deep`.

-'Shallow' threading makes every mail a reply to the head of the
+'shallow' threading makes every mail a reply to the head of the

 series, where the head is chosen from the cover letter, the
 series, where the head is chosen from the cover letter, the

-`\--in-reply-to`, and the first patch mail, in this order.  'Deep'
+`\--in-reply-to`, and the first patch mail, in this order.  'deep'

 threading makes every mail a reply to the previous one.  If not
 specified, defaults to the 'format.thread' configuration, or `shallow`
 if that is not set.
 threading makes every mail a reply to the previous one.  If not
 specified, defaults to the 'format.thread' configuration, or `shallow`
 if that is not set.