From 6fc111ccb6650a67f014977b2e7ebc2fb5b16790 Mon Sep 17 00:00:00 2001
From: Sadie Powell
Date: Sat, 29 Oct 2022 15:44:01 +0100
Subject: Rename session registration to connection to avoid a semantic
 conflict.

We previously referred to both session registration and user registration
as "registration" which is confusing for users who aren't familiar with
how IRC works.
---
 src/modules/m_starttls.cpp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'src/modules/m_starttls.cpp')

diff --git a/src/modules/m_starttls.cpp b/src/modules/m_starttls.cpp
index c95b7b4f5..905e8f6e3 100644
--- a/src/modules/m_starttls.cpp
+++ b/src/modules/m_starttls.cpp
@@ -55,7 +55,7 @@ public:
 
 		if (user->IsFullyConnected())
 		{
-			user->WriteNumeric(ERR_STARTTLS, "STARTTLS is not permitted after client registration is complete");
+			user->WriteNumeric(ERR_STARTTLS, "STARTTLS is not permitted once you are fully connected");
 			return CmdResult::FAILURE;
 		}
 
@@ -70,7 +70,7 @@ public:
 		 * otherwise we'll be sending this line inside the TLS session - which
 		 * won't start its handshake until the client gets this line. Currently,
 		 * we assume the write will not block here; this is usually safe, as
-		 * STARTTLS is sent very early on in the registration phase, where the
+		 * STARTTLS is sent very early on in the connection phase, where the
 		 * user hasn't built up much sendq. Handling a blocked write here would
 		 * be very annoying.
 		 */
-- 
cgit v1.3.1-10-gc9f91