Update content/authentication/managing-commit-signature-verification/…

…checking-for-existing-gpg-keys.md

Co-authored-by: Ben Ahmady <[email protected]>

content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md

@@ -29,7 +29,7 @@ shortTitle: Existing GPG keys
       $ gpg --armor --export 3AA5C34371567BD2
       # Prints the GPG public key, in ASCII armor format
       ```
-> If you encounter "No valid identities found in this GPG data" error, it may be because the public key you exported is too large or contains useless information, please add GPG option `--export-options export-minimal` to export again, e.g.: `$ gpg --armor --export-options export-minimal --export 3AA5C34371567BD2`
+        Consider exporting your keys with the option `--export-options export-minimal`, which can prevent misreading keys that contain deprecated fields.
 
       You can then [add your GPG key to your GitHub account](/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account).