aboutsummaryrefslogtreecommitdiff
path: root/doc/man3/OPENSSL_malloc.pod
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man3/OPENSSL_malloc.pod')
-rw-r--r--doc/man3/OPENSSL_malloc.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/man3/OPENSSL_malloc.pod b/doc/man3/OPENSSL_malloc.pod
index c60e038309a1..9834a8f13147 100644
--- a/doc/man3/OPENSSL_malloc.pod
+++ b/doc/man3/OPENSSL_malloc.pod
@@ -104,7 +104,7 @@ before ultimately calling OPENSSL_free().
OPENSSL_cleanse() fills B<ptr> of size B<len> with a string of 0's.
Use OPENSSL_cleanse() with care if the memory is a mapping of a file.
-If the storage controller uses write compression, then its possible
+If the storage controller uses write compression, then it's possible
that sensitive tail bytes will survive zeroization because the block of
zeros will be compressed. If the storage controller uses wear leveling,
then the old sensitive data will not be overwritten; rather, a block of