diff options
author | FdaSilvaYY <fdasilvayy@gmail.com> | 2016-05-01 19:52:58 +0200 |
---|---|---|
committer | Rich Salz <rsalz@openssl.org> | 2016-05-01 19:14:57 -0400 |
commit | 24c2cd3967ed23acc0bd31a3781c4525e2e42a2c (patch) | |
tree | ca10d9e7154f2bd7cf32216c6be51ad526cc7a0e /doc/crypto | |
parent | e0f96357e4b77e452966312a0542ec9cb0eb87bd (diff) |
Fix spelling in pod files
Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
Diffstat (limited to 'doc/crypto')
-rw-r--r-- | doc/crypto/ASYNC_WAIT_CTX_new.pod | 2 | ||||
-rw-r--r-- | doc/crypto/ASYNC_start_job.pod | 2 | ||||
-rw-r--r-- | doc/crypto/BIO_ADDRINFO.pod | 2 | ||||
-rw-r--r-- | doc/crypto/engine.pod | 4 |
4 files changed, 5 insertions, 5 deletions
diff --git a/doc/crypto/ASYNC_WAIT_CTX_new.pod b/doc/crypto/ASYNC_WAIT_CTX_new.pod index c4e4d0e38d..450ef6d136 100644 --- a/doc/crypto/ASYNC_WAIT_CTX_new.pod +++ b/doc/crypto/ASYNC_WAIT_CTX_new.pod @@ -53,7 +53,7 @@ ASYNC_WAIT_CTX_get_all_fds() with a NULL B<fd> value will return no file descriptors but will still populate B<*numfds>. Therefore application code is typically expected to call this function twice: once to get the number of fds, and then again when sufficient memory has been allocated. If only one -asynchronous engine is being used then noramlly this call will only ever return +asynchronous engine is being used then normally this call will only ever return one fd. If multiple asynchronous engines are being used then more could be returned. diff --git a/doc/crypto/ASYNC_start_job.pod b/doc/crypto/ASYNC_start_job.pod index 0e6507b195..5501f76cc8 100644 --- a/doc/crypto/ASYNC_start_job.pod +++ b/doc/crypto/ASYNC_start_job.pod @@ -111,7 +111,7 @@ for the B<job>. ASYNC_WAIT_CTXs can have a "wait" file descriptor associated with them. Applications can wait for the file descriptor to be ready for "read" using a system function call such as select or poll (being ready for "read" indicates that the job should be resumed). If no file descriptor is made -available then an application will have to priodically "poll" the job by +available then an application will have to periodically "poll" the job by attempting to restart it to see if it is ready to continue. An example of typical usage might be an async capable engine. User code would diff --git a/doc/crypto/BIO_ADDRINFO.pod b/doc/crypto/BIO_ADDRINFO.pod index 42a26e19fd..cca649ac77 100644 --- a/doc/crypto/BIO_ADDRINFO.pod +++ b/doc/crypto/BIO_ADDRINFO.pod @@ -72,7 +72,7 @@ with the given one. =head1 RETURN VALUES 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. +will leave an error indication on the OpenSSL error stack in that case. All other functions described here return 0 or B<NULL> when the information they should return isn't available. diff --git a/doc/crypto/engine.pod b/doc/crypto/engine.pod index 8d1b3dfc31..1e933ec3f7 100644 --- a/doc/crypto/engine.pod +++ b/doc/crypto/engine.pod @@ -444,7 +444,7 @@ boolean success or failure. ENGINE_free(e); return 0; } - pre_cmds += 2; + pre_cmds += 2; } if(!ENGINE_init(e)) { fprintf(stderr, "Failed initialisation\n"); @@ -461,7 +461,7 @@ boolean success or failure. ENGINE_finish(e); return 0; } - post_cmds += 2; + post_cmds += 2; } ENGINE_set_default(e, ENGINE_METHOD_ALL & ~ENGINE_METHOD_RAND); /* Success */ |