[httpd-site] branch main updated: Axe broken link in dev/verification.md.

[yl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ylavic pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/httpd-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 55c4d3e  Axe broken link in dev/verification.md.
     new 77b58b1  Merge pull request #6 from ylavic/evil32
55c4d3e is described below

commit 55c4d3ee7cb1ab986fab531e2b6bc80eccf10318
Author: ylavic <yl...@gmail.com>
AuthorDate: Fri Dec 17 16:27:27 2021 +0100

    Axe broken link in dev/verification.md.
---
 content/dev/verification.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/content/dev/verification.md b/content/dev/verification.md
index 94c01cc..29ae23b 100644
--- a/content/dev/verification.md
+++ b/content/dev/verification.md
@@ -49,10 +49,9 @@ In this example, you have now received two public keys for entities known
 as 'Jim Jagielski &lt;jim@apache.org&gt;' However, you have no way of
 verifying whether these keys were created by the person known as Jim
 Jagielski whose email address is claimed.  In fact, one of them is
-an imposter: see <https://evil32.org/> for the story
-(and this could change again at any time).  This doesn't mean that PGP
-is broken, just that you need to look at the full 40-character key
-fingerprint rather than the vulnerable 8-character ID.
+an imposter.  This doesn't mean that PGP is broken, just that you need to
+look at the full 40-character key fingerprint rather than the vulnerable
+8-character ID.
 
 Anyway, let's try to verify the release signature again: