Merge branch 'aqualls-signing-commits' into 'master'

CTRT revision of GPG signing page See merge request gitlab-org/gitlab!82541

Merge branch 'aqualls-signing-commits' into 'master'
CTRT revision of GPG signing page See merge request gitlab-org/gitlab!82541
4be7b092 · Kati Paizee · 0b53f192 · 891c8a72 · 0b53f192 · 4be7b092
Commit 4be7b092 authored Mar 14, 2022 by Kati Paizee
3 changed files
--- a/doc/user/project/repository/gpg_signed_commits/img/profile_settings_gpg_keys_paste_pub.png
+++ b/doc/user/project/repository/gpg_signed_commits/img/profile_settings_gpg_keys_paste_pub.png
--- a/doc/user/project/repository/gpg_signed_commits/index.md
+++ b/doc/user/project/repository/gpg_signed_commits/index.md
--- a/doc/user/project/repository/x509_signed_commits/index.md
+++ b/doc/user/project/repository/x509_signed_commits/index.md
@@ -20,7 +20,7 @@ The main difference is the way GitLab determines whether or not the developer's
  (A trust store is a repository of trusted security certificates.) Combined with
  any required intermediate certificates in the signature, the developer's certificate
  can be chained back to a trusted root certificate.
- For GPG, developers [add their GPG key](../gpg_signed_commits/index.md#adding-a-gpg-key-to-your-account)
+- For GPG, developers [add their GPG key](../gpg_signed_commits/index.md#add-a-gpg-key-to-your-account)
  to their account.
 GitLab uses its own certificate store and therefore defines the