From ba016ff49023569201f1fe08cf301f80cdb2a7d6 Mon Sep 17 00:00:00 2001
From: PSJ <51746608+thispsj@users.noreply.github.com>
Date: Mon, 19 Jul 2021 19:34:11 +0530
Subject: [PATCH 1/3] Remove outdated note.

Fixes github#8227
---
 .../telling-git-about-your-signing-key.md                  | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index e98925e0b8..ac13277fd9 100644
--- a/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -70,13 +70,6 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 
 {% endwindows %}
 
-{% linux %}
-
-{% note %}
-
-**Note:** X.509 keys are not supported on Linux. You can configure gpgsm to provide encryption and signing services, however, this is not currently supported by {% data variables.product.product_name %}. For more information, see the [gpgsm](https://www.gnupg.org/documentation/manuals/gnupg/Invoking-GPGSM.html) topic in the GnuPG documentation.
-
-{% endnote %}
 
 ## Telling Git about your GPG key
 

From 7065bcb0f7848f08cb77b190e2c0388283d2fa9d Mon Sep 17 00:00:00 2001
From: PSJ <51746608+thispsj@users.noreply.github.com>
Date: Mon, 19 Jul 2021 19:56:54 +0530
Subject: [PATCH 2/3] Fix things

---
 .../telling-git-about-your-signing-key.md                       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index ac13277fd9..f9dddedfad 100644
--- a/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -70,7 +70,7 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 
 {% endwindows %}
 
-
+{% linux %}
 ## Telling Git about your GPG key
 
 If you're using a GPG key that matches your committer identity and your verified email address associated with your {% data variables.product.product_name %} account, then you can begin signing commits and signing tags.

From 4261a9b1fb7b2a8bb39d8d12e3a829d644940bd9 Mon Sep 17 00:00:00 2001
From: PSJ <51746608+thispsj@users.noreply.github.com>
Date: Mon, 19 Jul 2021 21:14:41 +0530
Subject: [PATCH 3/3] Added a line to fix markdown

---
 .../telling-git-about-your-signing-key.md                        | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index f9dddedfad..1679ba4f2e 100644
--- a/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -71,6 +71,7 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 {% endwindows %}
 
 {% linux %}
+
 ## Telling Git about your GPG key
 
 If you're using a GPG key that matches your committer identity and your verified email address associated with your {% data variables.product.product_name %} account, then you can begin signing commits and signing tags.