From 806075f78c6fe317b7b91d3cba4d9c70a495761e Mon Sep 17 00:00:00 2001
From: "Dr. David von Oheimb" <dev@ddvo.net>
Date: Tue, 19 Dec 2023 16:27:25 +0100
Subject: [PATCH] fixup! X509_dup.pod: add caveat that extra data is not copied
 and hints, e.g., to use X509_up_ref() instead

---
 doc/man3/X509_dup.pod | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/man3/X509_dup.pod b/doc/man3/X509_dup.pod
index 107a0b237cafc..6f3819f8cd45e 100644
--- a/doc/man3/X509_dup.pod
+++ b/doc/man3/X509_dup.pod
@@ -364,10 +364,11 @@ may contain extra data besides the ASN.1 structure.
 For instance, an B<X509> object usually is augmented
 by cached information on X.509v3 extensions, etc.
 Such extra data is not copied.
-If it needs to be retained, maybe better use B<I<TYPE>_up_ref>().
+If it needs to be retained, it may be better to use B<I<TYPE>_up_ref>().
 For the case of B<X509> objects, an alternative to using L<X509_up_ref(3)>
-is to still call, e.g., I<copied_cert = X509_dup(cert)>, yet followed by
-I<X509_check_purpose(copied_cert, -1, 0)>, which re-builds the cached data.
+is to still call B<I<TYPE>_dup>(), e.g., I<copied_cert = X509_dup(cert)>,
+followed by I<X509_check_purpose(copied_cert, -1, 0)>,
+which re-builds the cached data.
 
 B<I<TYPE>_free>() releases the object and all pointers and sub-objects
 within it.