[celix-site] 02/02: Update release documentation to explain that KEYS only need to be uploaded to the release area

[rl...@apache.org]

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

rlenferink pushed a commit to branch improve-release-steps
in repository https://gitbox.apache.org/repos/asf/celix-site.git

commit 5fa6e85c8ce32487d0c791271a25d974cebb5718
Author: Roy Lenferink <le...@gmail.com>
AuthorDate: Sun Jul 17 19:58:57 2022 +0200

    Update release documentation to explain that KEYS only need to be uploaded to the release area
---
 source/contributing/releasing.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/source/contributing/releasing.md b/source/contributing/releasing.md
index 04cb9ed..9394e1c 100644
--- a/source/contributing/releasing.md
+++ b/source/contributing/releasing.md
@@ -26,11 +26,11 @@ provided on that site and its references.
 
 The generated key can be uploaded to the [MIT PGP Public Key Server](https://pgp.mit.edu/).
 
-Next, the public key signature must be added to the KEYS file. Again, read the [Signing Releases page](https://www.apache.org/dev/release-signing.html#keys-policy) 
-for more information. This updated file needs to be uploaded to GIT, be sure to upload it to:
+Next, the public key signature must be added to the [Celix KEYS file](https://downloads.apache.org/celix/KEYS).
+Again, read the [Signing Releases page](https://www.apache.org/dev/release-signing.html#keys-policy) for more
+information. This updated file needs to be uploaded to SVN at the following location:
 
-* [Apache Celix release development area KEYS](https://dist.apache.org/repos/dist/dev/celix/KEYS)
-* [Apache Celix release distribution area KEYS](https://downloads.apache.org/celix/KEYS)
+* [Apache Celix release distribution area KEYS](https://dist.apache.org/repos/dist/release/celix/KEYS)
 
 ## Create release branch
 
@@ -115,8 +115,8 @@ licenses may need to be mentioned in the NOTICE file.
 
 ## Create, sign and publish artifacts
 
-Since Celix only releases source artifacts, creating the artifact is simple and straightforward
-First verify that all changes are committed to the release branch and the branch is pushed to github
+Since Celix only releases source artifacts, creating the artifact is simple and straightforward.
+First verify that all changes are committed to the release branch and the branch is pushed to GitHub.
 
 ```bash
 # Create symbolic link so the archive has a directory with version information