From 0af20bdcfb54a648d4b0c907565171a46afd1457 Mon Sep 17 00:00:00 2001
From: Ingela Anderton Andin
Date: Thu, 30 Apr 2015 09:47:45 +0200
Subject: ssl: Align with application naming rules
ssl SSL
crypto Crypto
stdlib STDLIB
kernel Kernel
public_key Public Key
---
lib/ssl/doc/src/ssl_protocol.xml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
(limited to 'lib/ssl/doc/src/ssl_protocol.xml')
diff --git a/lib/ssl/doc/src/ssl_protocol.xml b/lib/ssl/doc/src/ssl_protocol.xml
index 20f53c98e1..cc49515066 100644
--- a/lib/ssl/doc/src/ssl_protocol.xml
+++ b/lib/ssl/doc/src/ssl_protocol.xml
@@ -32,19 +32,19 @@
ssl_protocol.xml
- The Erlang ssl application implements the SSL/TLS protocol
+
The Erlang SSL application implements the SSL/TLS protocol
for the currently supported versions, see the
ssl(3) manual page.
- By default ssl is run over the TCP/IP protocol even
+
By default SSL/TLS is run over the TCP/IP protocol even
though you can plug in any other reliable transport protocol
with the same Application Programming Interface (API) as the
- gen_tcp module in kernel.
+ gen_tcp module in Kernel.
If a client and a server wants to use an upgrade mechanism, such as
defined by RFC 2817, to upgrade a regular TCP/IP connection to an SSL
- connection, this is supported by the Erlang ssl API. This can be
+ connection, this is supported by the Erlang SSL application API. This can be
useful for, for example, supporting HTTP and HTTPS on the same port and
implementing virtual hosting.
@@ -143,7 +143,7 @@
connections. Sessions are used to avoid the expensive negotiation
of new security parameters for each connection."
- Session data is by default kept by the ssl application in a
+
Session data is by default kept by the SSL application in a
memory storage, hence session data is lost at application
restart or takeover. Users can define their own callback module
to handle session data storage if persistent data storage is
--
cgit v1.2.3