aboutsummaryrefslogtreecommitdiffstats
path: root/doc/crypto/ASYNC_start_job.pod
diff options
context:
space:
mode:
authorFdaSilvaYY <fdasilvayy@gmail.com>2016-05-01 19:52:58 +0200
committerRich Salz <rsalz@openssl.org>2016-05-01 19:14:57 -0400
commit24c2cd3967ed23acc0bd31a3781c4525e2e42a2c (patch)
treeca10d9e7154f2bd7cf32216c6be51ad526cc7a0e /doc/crypto/ASYNC_start_job.pod
parente0f96357e4b77e452966312a0542ec9cb0eb87bd (diff)
downloadopenssl-24c2cd3967ed23acc0bd31a3781c4525e2e42a2c.tar.gz
Fix spelling in pod files
Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Rich Salz <rsalz@openssl.org>
Diffstat (limited to 'doc/crypto/ASYNC_start_job.pod')
-rw-r--r--doc/crypto/ASYNC_start_job.pod2
1 files changed, 1 insertions, 1 deletions
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