summaryrefslogtreecommitdiffstats
path: root/doc/crypto
diff options
context:
space:
mode:
authorAlex Gaynor <alex.gaynor@gmail.com>2016-03-19 12:28:58 -0400
committerRich Salz <rsalz@openssl.org>2016-03-19 20:23:22 -0400
commit35ed393e5e47d75f9496ed1464bca7fc82cd72d7 (patch)
tree5bf9a1ca3245418d518e1cbcab394c1bc585f9db /doc/crypto
parent34c2db9b562baffd30a6a2dda7d4247fadbf4acd (diff)
Fixed a bunch of typos in the docs
Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Rich Salz <rsalz@openssl.org>
Diffstat (limited to 'doc/crypto')
-rw-r--r--doc/crypto/ASN1_INTEGER_get_int64.pod2
-rw-r--r--doc/crypto/ASN1_OBJECT_new.pod2
-rw-r--r--doc/crypto/ASYNC_start_job.pod2
-rw-r--r--doc/crypto/BIO_ADDRINFO.pod2
4 files changed, 4 insertions, 4 deletions
diff --git a/doc/crypto/ASN1_INTEGER_get_int64.pod b/doc/crypto/ASN1_INTEGER_get_int64.pod
index 3259530d75..fb1076658e 100644
--- a/doc/crypto/ASN1_INTEGER_get_int64.pod
+++ b/doc/crypto/ASN1_INTEGER_get_int64.pod
@@ -106,7 +106,7 @@ B<ASN1_ENUMERATED> structure respectively or NULL if an error occurs. They will
only fail due to a memory allocation error.
ASN1_INTEGER_to_BN() and ASN1_ENUMERATED_to_BN() return a B<BIGNUM> structure
-of NULL if an error occurs. They can fail if the pased type is incorrect
+of NULL if an error occurs. They can fail if the passed type is incorrect
(due to programming error) or due to a memory allocation failure.
=head1 SEE ALSO
diff --git a/doc/crypto/ASN1_OBJECT_new.pod b/doc/crypto/ASN1_OBJECT_new.pod
index 486ccc91bb..cc9cf43cad 100644
--- a/doc/crypto/ASN1_OBJECT_new.pod
+++ b/doc/crypto/ASN1_OBJECT_new.pod
@@ -16,7 +16,7 @@ ASN1_OBJECT_new, ASN1_OBJECT_free - object allocation functions
The ASN1_OBJECT allocation routines, allocate and free an
ASN1_OBJECT structure, which represents an ASN1 OBJECT IDENTIFIER.
-ASN1_OBJECT_new() allocates and initializes a ASN1_OBJECT structure.
+ASN1_OBJECT_new() allocates and initializes an ASN1_OBJECT structure.
ASN1_OBJECT_free() frees up the B<ASN1_OBJECT> structure B<a>.
If B<a> is NULL, nothing is done.
diff --git a/doc/crypto/ASYNC_start_job.pod b/doc/crypto/ASYNC_start_job.pod
index c64af3d340..0e6507b195 100644
--- a/doc/crypto/ASYNC_start_job.pod
+++ b/doc/crypto/ASYNC_start_job.pod
@@ -135,7 +135,7 @@ application acquires a lock. It then calls some cryptographic function which
invokes ASYNC_pause_job(). This returns control back to the code that created
the ASYNC_JOB. If that code then attempts to acquire the same lock before
resuming the original job then a deadlock can occur. By calling
-ASYNC_block_pause() immediately after aquiring the lock and
+ASYNC_block_pause() immediately after acquiring the lock and
ASYNC_unblock_pause() immediately before releasing it then this situation cannot
occur.
diff --git a/doc/crypto/BIO_ADDRINFO.pod b/doc/crypto/BIO_ADDRINFO.pod
index 85652add9b..42a26e19fd 100644
--- a/doc/crypto/BIO_ADDRINFO.pod
+++ b/doc/crypto/BIO_ADDRINFO.pod
@@ -71,7 +71,7 @@ with the given one.
=head1 RETURN VALUES
-BIO_lookup() returns 1 on success and 0 when an error occured, and
+BIO_lookup() returns 1 on success and 0 when an error occurred, and
will leave an error indicaton on the OpenSSL error stack in that case.
All other functions described here return 0 or B<NULL> when the