diff --git a/security/split-gpg.md b/security/split-gpg.md
index 5497551b..64543730 100644
--- a/security/split-gpg.md
+++ b/security/split-gpg.md
@@ -79,7 +79,7 @@ The Split GPG client will fail to sign or encrypt if the private key in the
 GnuPG backend is protected by a passphrase, it will give a *"Inappropriate ioctl 
 for device"* error. Avoid setting passphrases for the private keys in the GPG 
 backend domain, it won't provide extra security anyway, as explained before. 
-Unfortunately you can set empty passphrases no matter what `pinentry-*` package 
+Unfortunately you can't set empty passphrases no matter what `pinentry-*` package 
 you are using.  If you are generating a new key pair, or if you have a private 
 key that already has a passphrase and use 
 `gpg2 --edit-key {key_id}`, then `passwd`, then pinentry won't allow setting an