From 60c7e0ab76fc13b874432911bf7939ef921d69e3 Mon Sep 17 00:00:00 2001 From: Florian Schmaus Date: Wed, 29 May 2019 11:49:16 +0200 Subject: [PATCH] Fix typo in XmppNioTcpConnection: s/Therfore/Therefore/ --- .../java/org/jivesoftware/smack/tcp/XmppNioTcpConnection.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/smack-tcp/src/main/java/org/jivesoftware/smack/tcp/XmppNioTcpConnection.java b/smack-tcp/src/main/java/org/jivesoftware/smack/tcp/XmppNioTcpConnection.java index 31b8f35a8..8cc7287df 100644 --- a/smack-tcp/src/main/java/org/jivesoftware/smack/tcp/XmppNioTcpConnection.java +++ b/smack-tcp/src/main/java/org/jivesoftware/smack/tcp/XmppNioTcpConnection.java @@ -1116,7 +1116,7 @@ public class XmppNioTcpConnection extends AbstractXmppNioConnection { // remote hostname information, in which case peerHost needs to be specified." that A should be used. TLS // session resumption may would need or at least benefit from B. Variant A would also be required if the // String is used for certificate verification. And it appears at least likely that TLS session resumption - // would not be hurt by using variant A. Therfore we currently use variant A. + // would not be hurt by using variant A. Therefore we currently use variant A. engine = smackTlsContext.sslContext.createSSLEngine(config.getXMPPServiceDomain().toString(), remoteAddress.getPort()); engine.setUseClientMode(true);