aboutsummaryrefslogtreecommitdiffstats
path: root/doc/ssl
diff options
context:
space:
mode:
authorBodo Möller <bodo@openssl.org>2000-09-16 16:00:38 +0000
committerBodo Möller <bodo@openssl.org>2000-09-16 16:00:38 +0000
commitacb5b34328e0e65095f7924f58c78a146e3d8a93 (patch)
treec7bb2aebcf15f26fa6e24eab646a3e309d34704d /doc/ssl
parentc1629c9ea2c650b4b54a489ea5c181320dc9f1fd (diff)
downloadopenssl-acb5b34328e0e65095f7924f58c78a146e3d8a93.tar.gz
Change spelling back to "behaviour" and "flavour" instead of the
American variants.
Diffstat (limited to 'doc/ssl')
-rw-r--r--doc/ssl/SSL_accept.pod2
-rw-r--r--doc/ssl/SSL_connect.pod2
-rw-r--r--doc/ssl/SSL_read.pod2
-rw-r--r--doc/ssl/SSL_set_bio.pod4
-rw-r--r--doc/ssl/SSL_set_fd.pod4
-rw-r--r--doc/ssl/SSL_shutdown.pod2
-rw-r--r--doc/ssl/SSL_write.pod2
7 files changed, 9 insertions, 9 deletions
diff --git a/doc/ssl/SSL_accept.pod b/doc/ssl/SSL_accept.pod
index 303cf24680..fc6a57b5da 100644
--- a/doc/ssl/SSL_accept.pod
+++ b/doc/ssl/SSL_accept.pod
@@ -14,7 +14,7 @@ SSL_accept - wait for a TLS/SSL client to initiate a TLS/SSL handshake
SSL_accept() waits for a TLS/SSL client to initiate the TLS/SSL handshake.
The communication channel must already have been set and assigned to the
-B<ssl> by setting an underlying B<BIO>. The behavior of SSL_accept() depends
+B<ssl> by setting an underlying B<BIO>. The behaviour of SSL_accept() depends
on the underlying BIO.
If the underlying BIO is B<blocking>, SSL_accept() will only return once the
diff --git a/doc/ssl/SSL_connect.pod b/doc/ssl/SSL_connect.pod
index a5027717cf..92aa20e079 100644
--- a/doc/ssl/SSL_connect.pod
+++ b/doc/ssl/SSL_connect.pod
@@ -14,7 +14,7 @@ SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server
SSL_connect() initiates the TLS handshake with a server. The communication
channel must already have been set and assigned to the B<ssl> by setting an
-underlying B<BIO>. The behavior of SSL_connect() depends on the underlying
+underlying B<BIO>. The behaviour of SSL_connect() depends on the underlying
BIO.
If the underlying BIO is B<blocking>, SSL_connect() will only return once the
diff --git a/doc/ssl/SSL_read.pod b/doc/ssl/SSL_read.pod
index a1fc0fb356..3b082a7c90 100644
--- a/doc/ssl/SSL_read.pod
+++ b/doc/ssl/SSL_read.pod
@@ -16,7 +16,7 @@ SSL_read() tries to read B<num> bytes from the specified B<ssl> into the
buffer B<buf>. If necessary, SSL_read() will negotiate a TLS/SSL session, if
not already explicitly performed by SSL_connect() or SSL_accept(). If the
peer requests a re-negotiation, it will be performed transparently during
-the SSL_read() operation. The behavior of SSL_read() depends on the
+the SSL_read() operation. The behaviour of SSL_read() depends on the
underlying BIO.
If the underlying BIO is B<blocking>, SSL_read() will only return, once the
diff --git a/doc/ssl/SSL_set_bio.pod b/doc/ssl/SSL_set_bio.pod
index 296aa6d7e2..67c9756d3f 100644
--- a/doc/ssl/SSL_set_bio.pod
+++ b/doc/ssl/SSL_set_bio.pod
@@ -15,8 +15,8 @@ SSL_set_bio - connect the SSL object with a BIO
SSL_set_bio() connects the BIOs B<rbio> and B<wbio> for the read and write
operations of the TLS/SSL (encrypted) side of B<ssl>.
-The SSL engine inherits the behavior of B<rbio> and B<wbio>, respectively.
-If a BIO is non-blocking, the B<ssl> will also have non-blocking behavior.
+The SSL engine inherits the behaviour of B<rbio> and B<wbio>, respectively.
+If a BIO is non-blocking, the B<ssl> will also have non-blocking behaviour.
If there was already a BIO connected to B<ssl>, BIO_free() will be called
(for both the reading and writing side, if different).
diff --git a/doc/ssl/SSL_set_fd.pod b/doc/ssl/SSL_set_fd.pod
index f6d9b7a1dc..70291128fc 100644
--- a/doc/ssl/SSL_set_fd.pod
+++ b/doc/ssl/SSL_set_fd.pod
@@ -20,8 +20,8 @@ socket file descriptor of a network connection.
When performing the operation, a B<socket BIO> is automatically created to
interface between the B<ssl> and B<fd>. The BIO and hence the SSL engine
-inherit the behavior of B<fd>. If B<fd> is non-blocking, the B<ssl> will
-also have non-blocking behavior.
+inherit the behaviour of B<fd>. If B<fd> is non-blocking, the B<ssl> will
+also have non-blocking behaviour.
If there was already a BIO connected to B<ssl>, BIO_free() will be called
(for both the reading and writing side, if different).
diff --git a/doc/ssl/SSL_shutdown.pod b/doc/ssl/SSL_shutdown.pod
index f287aad9ce..20e273bd4d 100644
--- a/doc/ssl/SSL_shutdown.pod
+++ b/doc/ssl/SSL_shutdown.pod
@@ -13,7 +13,7 @@ SSL_shutdown - shut down a TLS/SSL connection
=head1 DESCRIPTION
SSL_shutdown() shuts down an active TLS/SSL connection. It sends the shutdown
-alert to the peer. The behavior of SSL_shutdown() depends on the underlying
+alert to the peer. The behaviour of SSL_shutdown() depends on the underlying
BIO.
If the underlying BIO is B<blocking>, SSL_shutdown() will only return once the
diff --git a/doc/ssl/SSL_write.pod b/doc/ssl/SSL_write.pod
index 4db85473d9..b086258e82 100644
--- a/doc/ssl/SSL_write.pod
+++ b/doc/ssl/SSL_write.pod
@@ -16,7 +16,7 @@ SSL_write() writes B<num> bytes from the buffer B<buf> into the specified
B<ssl>. If necessary, SSL_write() will negotiate a TLS/SSL session, if
not already explicitly performed by SSL_connect() or SSL_accept(). If the
peer requests a re-negotiation, it will be performed transparently during
-the SSL_write() operation. The behavior of SSL_write() depends on the
+the SSL_write() operation. The behaviour of SSL_write() depends on the
underlying BIO.
If the underlying BIO is B<blocking>, SSL_write() will only return, once the