diff --git a/external/contribute/ssh-key-generation/ssh-key-generation.md b/external/contribute/ssh-key-generation/ssh-key-generation.md
index 3d76964207c2976b5c217177c9198ea7148d6b42..084d53f5a1c5dd489f6018963c6723c6b4572cd8 100644
--- a/external/contribute/ssh-key-generation/ssh-key-generation.md
+++ b/external/contribute/ssh-key-generation/ssh-key-generation.md
@@ -15,7 +15,7 @@ Key-based authentication allows GitLab users to identify their device once on th
 
 SSH uses a public and a private key:
 - The public key must be registered in GitLab, where it "identifies" your device.
-- The private key must stay secret and preferably you should only keep it on a single device. The private key is the only key that can be used to authenticate your identity against the public key uploaded to GitLab -- if it becomes public, anyone could impersonate your identity and thus use your GitLab account. **Make sure you do not upload the private key anywhere by accident, not even to GitLab.**
+- The private key must stay secret and preferably you should only keep it on a single device. The private key is the only key that can be used to authenticate your identity against the public key uploaded to GitLab -- if it becomes public, anyone can impersonate your identity and thus use your GitLab account. **Make sure you do NOT upload the private key anywhere by accident, not even to GitLab.**
 
 # Prerequisites