[sling-site] branch master updated: Fix broken link

[bd...@apache.org]

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

bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new eafb5ae  Fix broken link
eafb5ae is described below

commit eafb5ae6a2faf48f8ffd255638de1c34902dea6c
Author: Bertrand Delacretaz <bd...@apache.org>
AuthorDate: Tue Aug 31 12:39:25 2021 +0200

    Fix broken link
---
 src/main/jbake/content/documentation/development/release-management.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md
index 5f1d4a4..bde9b88 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -402,7 +402,7 @@ Assuming you are using a \*nix system with a working OpenSSH, GnuPG, and bash yo
 
     When gpg asks for e-mail linked the key you *MUST USE* the &lt;committer&gt;@apache.org one. When gpg asks for comment linked the key you *SHOULD USE* "CODE SIGNING KEY"
 
-1. It's also good to upload your key to a public key server, see the [https://infra.apache.org/release-signing.html](ASF release signing page) for more info.
+1. It's also good to upload your key to a public key server, see the [ASF Infrastructure Release Signing](https://infra.apache.org/release-signing.html) page for more info.
 
 1. Add the key to [https://people.apache.org/keys/group/sling.asc](https://people.apache.org/keys/group/sling.asc)