From c1de66e1d7b8458aca2979e20884c3c378b04a4d Mon Sep 17 00:00:00 2001
From: Paul Schaub <vanitasvitae@fsfe.org>
Date: Tue, 2 Aug 2022 16:53:01 +0200
Subject: [PATCH] Fix javadoc lying about only encrypting to single subkeys

Fixes #305
---
 .../pgpainless/encryption_signing/EncryptionOptions.java    | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pgpainless-core/src/main/java/org/pgpainless/encryption_signing/EncryptionOptions.java b/pgpainless-core/src/main/java/org/pgpainless/encryption_signing/EncryptionOptions.java
index 99059c0a..2a75ee4e 100644
--- a/pgpainless-core/src/main/java/org/pgpainless/encryption_signing/EncryptionOptions.java
+++ b/pgpainless-core/src/main/java/org/pgpainless/encryption_signing/EncryptionOptions.java
@@ -48,11 +48,11 @@ import org.pgpainless.util.Passphrase;
  * This will cause PGPainless to use the provided algorithm for message encryption, instead of negotiating an algorithm
  * by inspecting the provided recipient keys.
  *
- * By default, PGPainless will only encrypt to a single encryption capable subkey per recipient key.
- * This behavior can be changed, e.g. by calling
+ * By default, PGPainless will encrypt to all suitable, encryption capable subkeys on each recipient's certificate.
+ * This behavior can be changed per recipient, e.g. by calling
  * <pre>
  * {@code
- * opt.addRecipient(aliceKey, EncryptionOptions.encryptToAllCapableSubkeys());
+ * opt.addRecipient(aliceKey, EncryptionOptions.encryptToFirstSubkey());
  * }
  * </pre>
  * when adding the recipient key.