From 0d8db24b1a43ed647e844e88261c531518bbbc96 Mon Sep 17 00:00:00 2001 From: Paul Schaub Date: Wed, 2 Aug 2023 16:02:01 +0200 Subject: [PATCH] Fix typo --- docs/source/pgpainless-sop/quickstart.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/pgpainless-sop/quickstart.md b/docs/source/pgpainless-sop/quickstart.md index 04417816..8b8281ac 100644 --- a/docs/source/pgpainless-sop/quickstart.md +++ b/docs/source/pgpainless-sop/quickstart.md @@ -120,10 +120,10 @@ OpenPGP keys can (but don't need to) be password protected. The `changeKeyPassword()` API can be used to add, change or remove password protection from OpenPGP keys. While the input to this operation can be keys with different per-subkey passwords, the output will use at most one password. -Using `oldKeyPassphrase()` multiple decryption passphrase candidates can be provided. +Via `oldKeyPassphrase()`, multiple decryption passphrase candidates can be provided. These are tried one after another to unlock protected subkeys. -In order to successfully change the passphrase of an OpenPGP key, the all subkeys needs to be decrypted. +In order to successfully change the passphrase of an OpenPGP key, all of its subkeys needs to be successfully decrypted. If one or more subkeys cannot be decrypted, the operation fails with a `KeyIsProtected` exception. The result is either fully encrypted for a single passphrase (passed via `newKeyPassphrase()`), or unprotected if the new key passphrase is omitted.