Documentation: the name of the system is 'Git', not 'git'

[thirdparty/git.git] / Documentation / git-credential-store.txt

diff --git a/Documentation/git-credential-store.txt b/Documentation/git-credential-store.txt
index b27c03c361111a01dbc5c2407c209e5f8530eec2..8481cae70ef067bafbee82c9c720795b09881024 100644 (file)
--- a/Documentation/git-credential-store.txt
+++ b/Documentation/git-credential-store.txt
@@ -20,7 +20,7 @@ security tradeoff, try linkgit:git-credential-cache[1], or find a helper
 that integrates with secure storage provided by your operating system.
 
 This command stores credentials indefinitely on disk for use by future
 that integrates with secure storage provided by your operating system.
 
 This command stores credentials indefinitely on disk for use by future

-git programs.
+Git programs.

 
 You probably don't want to invoke this command directly; it is meant to
 be used as a credential helper by other parts of git. See
 
 You probably don't want to invoke this command directly; it is meant to
 be used as a credential helper by other parts of git. See


@@ -63,11 +63,11 @@ stored on its own line as a URL like:
 https://user:pass@example.com
 ------------------------------
 
 https://user:pass@example.com
 ------------------------------
 

-When git needs authentication for a particular URL context,
+When Git needs authentication for a particular URL context,

 credential-store will consider that context a pattern to match against
 each entry in the credentials file.  If the protocol, hostname, and
 username (if we already have one) match, then the password is returned
 credential-store will consider that context a pattern to match against
 each entry in the credentials file.  If the protocol, hostname, and
 username (if we already have one) match, then the password is returned

-to git. See the discussion of configuration in linkgit:gitcredentials[7]
+to Git. See the discussion of configuration in linkgit:gitcredentials[7]

 for more information.
 
 GIT
 for more information.
 
 GIT