Merge branch 'en/fetch-negotiation-default-fix'

[thirdparty/git.git] / Documentation / config / gpg.txt

diff --git a/Documentation/config/gpg.txt b/Documentation/config/gpg.txt
index c9be554c73225f362ac300281bb3b1ddbc2dc88d..86892ada771e802830cd10d3e5ff95bc74355e9e 100644 (file)
--- a/Documentation/config/gpg.txt
+++ b/Documentation/config/gpg.txt
@@ -34,17 +34,17 @@ gpg.minTrustLevel::
 * `fully`
 * `ultimate`
 
-gpg.ssh.defaultKeyCommand:
+gpg.ssh.defaultKeyCommand::
        This command that will be run when user.signingkey is not set and a ssh
        signature is requested. On successful exit a valid ssh public key is
-       expected in the first line of its output. To automatically use the first
+       expected in the first line of its output. To automatically use the first
        available key from your ssh-agent set this to "ssh-add -L".
 
 gpg.ssh.allowedSignersFile::
        A file containing ssh public keys which you are willing to trust.
        The file consists of one or more lines of principals followed by an ssh
        public key.
-       e.g.: user1@example.com,user2@example.com ssh-rsa AAAAX1...
+       e.g.: `user1@example.com,user2@example.com ssh-rsa AAAAX1...`
        See ssh-keygen(1) "ALLOWED SIGNERS" for details.
        The principal is only used to identify the key and is available when
        verifying a signature.
@@ -66,7 +66,7 @@ This way only committers with an already valid key can add or change keys in the
 +
 Since OpensSSH 8.8 this file allows specifying a key lifetime using valid-after &
 valid-before options. Git will mark signatures as valid if the signing key was
-valid at the time of the signatures creation. This allows users to change a
+valid at the time of the signature's creation. This allows users to change a
 signing key without invalidating all previously made signatures.
 +
 Using a SSH CA key with the cert-authority option