From d3054fb663a6a3a4689e52c10bb3094c39a3bce8 Mon Sep 17 00:00:00 2001 From: Benjamin Kaduk Date: Tue, 15 Dec 2015 16:23:51 -0600 Subject: [PATCH] GH768: Minor grammar nits in CRYPTO_get_ex_new_index.pod Signed-off-by: Rich Salz Reviewed-by: Kurt Roeckx --- doc/crypto/CRYPTO_get_ex_new_index.pod | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/crypto/CRYPTO_get_ex_new_index.pod b/doc/crypto/CRYPTO_get_ex_new_index.pod index 1720a8f5f4..e87d1a3ded 100644 --- a/doc/crypto/CRYPTO_get_ex_new_index.pod +++ b/doc/crypto/CRYPTO_get_ex_new_index.pod @@ -85,7 +85,7 @@ B parameter should be an already-created index value. When setting exdata, the pointer specified with a particular index is saved, and returned on a subsequent "get" call. If the application is going to release the data, it must make sure to set a B value at the index, -to avoid likely double-free crash. +to avoid likely double-free crashes. The function B is used to free all exdata attached to a structure. The appropriate type-specific routine must be used. @@ -124,9 +124,10 @@ for B and B objects. The B and B parameters are pointers to the destination and source B structures, respectively. The B parameter is a pointer to the source exdata. When the dup_func() returns, the value in B is copied to the -destination ex_data. If the pointer contained in B is not modified, -then both B and B will point to the same data. The B, -B and B parameters are as described for the other two callbacks. +destination ex_data. If the pointer contained in B is not modified +by the dup_func(), then both B and B will point to the same data. +The B, B and B parameters are as described for the other +two callbacks. =head1 RETURN VALUES -- GitLab