Remove old names for things now the v3 docs are gone.

sadiepowell · sadiepowell · commit b54c8de3ae24 · 2026-03-19T13:02:47.000Z
diff --git a/docs/4/change-log-dev.md b/docs/4/change-log-dev.md
@@ -104,13 +104,13 @@ This page lists changes which have happened between development releases. For th
 
 - Added `<options:maskinlist>` to allow saving the full user mask of a list mode setter.
 
-- Added `<sslinfo:welcomemessage>` to control sending the SSL connection information message to connecting users.
+- Added `<sslinfo:welcomemessage>` to control sending the TLS connection information message to connecting users.
 
-- Added a zero-parameter version of `/SSLINFO` to view your own SSL certificate information.
+- Added a zero-parameter version of `/SSLINFO` to view your own TLS certificate information.
 
-- Added checks to help users migrate from v2-style SSL config.
+- Added checks to help users migrate from v2-style TLS config.
 
-- Added support for multiple SSL fingerprints to allow migrating between hash algorithms.
+- Added support for multiple TLS fingerprints to allow migrating between hash algorithms.
 
 - Added the `$address` variable to the alias module.
 
diff --git a/docs/faq.md b/docs/faq.md
@@ -59,11 +59,11 @@ Server operators do not automatically get channel privileges by default. You can
 
 - Giving yourself channel operator status using [the samode module](/4/modules/samode).
 
-### Why does my server tell me "An unexpected TLS packet was received" or "error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c" when I try to connect using SSL/TLS?
+### Why does my server tell me "An unexpected TLS packet was received" or "error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c" when I try to connect using TLS?
 
-You are trying to connect using TLS (SSL) but your server is not configured to listen for TLS (SSL) connections.
+You are trying to connect using TLS but your server is not configured to listen for TLS connections.
 
-Check that you have a TLS (SSL) module loaded and that your bind tag has the name of a TLS (SSL) profile in `<bind:ssl>`.
+Check that you have a TLS module loaded and that your bind tag has the name of a TLS profile in `<bind:ssl>`.
 
 If you're using v3.7.0 or newer you can also use the `inspircd-testssl` script to help diagnose this issue.
 
diff --git a/docs/server/messages/capab.yml b/docs/server/messages/capab.yml
@@ -38,7 +38,7 @@ extra: |-
   CHANMAX          | 64                   | [**1205**] The maximum number of channels a user can normally join.
   EXTBANS          | ABCDEFabcdef         | [**1205**] The extended bans that exist on the remote server.
   GLOBOPS          | 1                    | [**1205**] Whether the server supports the GLOBOPS extension.
-  IDENTMAX         | 10                   | [**1205**] The maximum length of a username (ident).
+  IDENTMAX         | 10                   | [**1205**] The maximum length of a username.
   MAXAWAY          | 200                  | The maximum length of an away message.
   MAXCHANNEL       | 64                   | [**1206+**] The maximum number of channels a user can normally join.
   MAXHOST          | 64                   | The maximum length of a hostname.
@@ -49,7 +49,7 @@ extra: |-
   MAXQUIT          | 255                  | The maximum length of a quit message.
   MAXREAL          | 128                  | The maximum length of a real name.
   MAXTOPIC         | 307                  | The maximum length of a channel topic.
-  MAXUSER          | 10                   | [**1206+**] The maximum length of a username (ident).
+  MAXUSER          | 10                   | [**1206+**] The maximum length of a username.
   NICKMAX          | 30                   | [**1205**] The maximum length of a nickname.
 
   If provided the extban-type field can be set to one of the following values:
diff --git a/docs/server/messages/fmode.yml b/docs/server/messages/fmode.yml
@@ -9,7 +9,7 @@ syntax:
   text:
   - <channel> <ts> <modes> [<mode-parameters>]+
 description: |-
-  Changes the username (ident) of the source user to the specified value.
+  Changes the username of the source user to the specified value.
 example:
 - description: |-
     Sets channel modes `n` (noextmsg) and `l` (limit) on #chan
diff --git a/docs/server/messages/fname.yml b/docs/server/messages/fname.yml
@@ -2,13 +2,13 @@ name: FNAME
 source: uid
 syntax:
   fields:
-    realname: The new real name (gecos) of the source user.
+    realname: The new real name of the source user.
   text:
   - <realname>
 description: |-
-  Changes the real name (gecos) of the source user to the specified value.
+  Changes the real name of the source user to the specified value.
 example:
 - description: |-
-    Changes the real name (gecos) of 36DAAAAAA to "Wibble Wobble"
+    Changes the real name of 36DAAAAAA to "Wibble Wobble"
   text: |-
     :36DAAAAAA FNAME :Wibble Wobble
diff --git a/docs/server/messages/ftopic.yml b/docs/server/messages/ftopic.yml
@@ -10,7 +10,7 @@ syntax:
   text:
   - <channel> <channel-ts> <topic-ts> [<setter>] :<new-topic>
 description: |-
-  Changes the username (ident) of the source user to the specified value.
+  Changes the username of the source user to the specified value.
 example:
 - description: |-
     User 36DAAAAAA changing the topic of #chan
diff --git a/docs/server/messages/nick.yml b/docs/server/messages/nick.yml
@@ -7,7 +7,7 @@ syntax:
   text:
   - <nick> <ts>
 description: |-
-  Changes the username (ident) of the source user to the specified value.
+  Changes the username of the source user to the specified value.
 example:
 - description: |-
     Changes the nickname of 36DAAAAAA to Sadie
diff --git a/docs/tutorials/enable-tls.md b/docs/tutorials/enable-tls.md
@@ -1,15 +1,15 @@
 ---
-title: How to enable TLS (SSL) on your IRC network
+title: How to enable TLS on your IRC network
 ---
 
 !!! note ""
     This page is a work in progress. If you find any part of it to be unclear [please open an issue](https://github.com/inspircd/docs/issues/new).
 
-## How to enable TLS (SSL) on your IRC network
+## How to enable TLS on your IRC network
 
-### Building a TLS (SSL) module
+### Building a TLS module
 
-If you are building from source you will need to enable a TLS (SSL) module. Your current options are:
+If you are building from source you will need to enable a TLS module. Your current options are:
 
 - [ssl_gnutls](/4/modules/ssl_gnutls) &mdash; requires [the GnuTLS library](https://gnutls.org).
 - [ssl_openssl](/4/modules/ssl_openssl) &mdash; requires [the OpenSSL library](https://www.openssl.org).
@@ -18,24 +18,24 @@ You will also need to install [pkg-config](https://www.freedesktop.org/wiki/Soft
 
 If you have these installed before running `./configure` then the appropriate modules will be enabled automatically. If you are installing after building InspIRCd or they were not automatically enabled for some reason you can build them with `./configure --enable-extras module-name-here` and then `make install`.
 
-### Acquiring a TLS (SSL) certificate and key
+### Acquiring a TLS certificate and key
 
-If you have not already acquired a TLS (SSL) certificate and key you will need to do so. The recommended method of acquiring these files is an ACME client like [Certbot](https://certbot.eff.org/). You can acquire this from either your system package manager or from pip. See [the Certbot installation instructions](https://certbot.eff.org/instructions?ws=other&os=pip) for more information on how to install and configure Certbot. Alternatives to Certbot include [Dehydrated](https://github.com/dehydrated-io/dehydrated), [acme.sh](https://github.com/acmesh-official/acme.sh), and [many others](https://letsencrypt.org/docs/client-options/).
+If you have not already acquired a TLS certificate and key you will need to do so. The recommended method of acquiring these files is an ACME client like [Certbot](https://certbot.eff.org/). You can acquire this from either your system package manager or from pip. See [the Certbot installation instructions](https://certbot.eff.org/instructions?ws=other&os=pip) for more information on how to install and configure Certbot. Alternatives to Certbot include [Dehydrated](https://github.com/dehydrated-io/dehydrated), [acme.sh](https://github.com/acmesh-official/acme.sh), and [many others](https://letsencrypt.org/docs/client-options/).
 
-InspIRCd ships with a script called `deploy-ssl.sh` that you can customise for use as a post-deploy hook to automatically reload your TLS (SSL) profiles when your TLS (SSL) certificate and key are updated. Generally this should not require much tweaking but you should check it just in case. If you are using this you should also make sure that your IRC server has [the sslrehashsignal module](/4/modules/sslrehashsignal) loaded (see below).
+InspIRCd ships with a script called `deploy-ssl.sh` that you can customise for use as a post-deploy hook to automatically reload your TLS profiles when your TLS certificate and key are updated. Generally this should not require much tweaking but you should check it just in case. If you are using this you should also make sure that your IRC server has [the sslrehashsignal module](/4/modules/sslrehashsignal) loaded (see below).
 
-### Loading and configuring a TLS (SSL) module
+### Loading and configuring a TLS module
 
-First you must add a `<module>` tag for the name of the TLS (SSL) module you want to use. e.g. to use the `ssl_gnutls` module use `<module name="ssl_gnutls">`.
+First you must add a `<module>` tag for the name of the TLS module you want to use. e.g. to use the `ssl_gnutls` module use `<module name="ssl_gnutls">`.
 
-Once this is added you need to create a TLS (SSL) profile. The syntax of these depend on the TLS (SSL) module that you are using.
+Once this is added you need to create a TLS profile. The syntax of these depend on the TLS module that you are using.
 
 - [ssl_gnutls](/4/modules/ssl_gnutls#sslprofile)
 - [ssl_openssl](/4/modules/ssl_openssl#sslprofile)
 
 You should note down the value of `<sslprofile:name>` as you will need this in the next step.
 
-Now you have a TLS (SSL) profile you can create [a `<bind>` tag](/4/configuration/#bind) with the `sslprofile` key set to the name you specified in `<sslprofile:name>`. This might vary depending on your configuration but it will look something like this:
+Now you have a TLS profile you can create [a `<bind>` tag](/4/configuration/#bind) with the `sslprofile` key set to the name you specified in `<sslprofile:name>`. This might vary depending on your configuration but it will look something like this:
 
 ```xml
 <bind address="*"
@@ -44,18 +44,18 @@ Now you have a TLS (SSL) profile you can create [a `<bind>` tag](/4/configuratio
       type="clients">
 ```
 
-Once you have added this you should restart your server or run `/REHASH` followed by `/REHASH -ssl` as a server operator to reload both your configuration and your TLS (SSL) profiles.
+Once you have added this you should restart your server or run `/REHASH` followed by `/REHASH -ssl` as a server operator to reload both your configuration and your TLS profiles.
 
 ### Diagnosing issues
 
 InspIRCd ships with a tool named `inspircd-testssl` on binary installations and `./tools/testssl` on source installations. You can run this to diagnose any problems with your server configuration.
 
 ### Common mistakes
 
-In older versions of InspIRCd you configured TLS (SSL) by setting `<bind:ssl>` to the name of a TLS (SSL) module and configuring the TLS (SSL) certificate and key in `<gnutls>`, `<mbedtls>`, or `<openssl>`. Configuring TLS (SSL) in this way is deprecated and will not work if you have a TLS (SSL) profile defined. It is strongly recommended that you do not use this method as it has been removed in the development branch.
+In older versions of InspIRCd you configured TLS by setting `<bind:ssl>` to the name of a TLS module and configuring the TLS certificate and key in `<gnutls>`, `<mbedtls>`, or `<openssl>`. Configuring TLS in this way is deprecated and will not work if you have a TLS profile defined. It is strongly recommended that you do not use this method as it has been removed in the development branch.
 
-In v3 TLS (SSL) certificates are not reloaded by default on a regular config rehash. You need to use `/REHASH -ssl` to reload TLS (SSL) certificates or load [the sslrehashsignal module](/4/modules/sslrehashsignal) and send SIGUSR1 to your IRC server. You can also set `<gnutls onrehash="yes">`, `<mbedtls onrehash="yes">`. or `<openssl onrehash="yes>` to reload your TLS (SSL) certificates on rehash.
+In v3 TLS certificates are not reloaded by default on a regular config rehash. You need to use `/REHASH -ssl` to reload TLS certificates or load [the sslrehashsignal module](/4/modules/sslrehashsignal) and send SIGUSR1 to your IRC server. You can also set `<gnutls onrehash="yes">`, `<mbedtls onrehash="yes">`. or `<openssl onrehash="yes>` to reload your TLS certificates on rehash.
 
-Certbot provides multiple TLS (SSL) certificate files. If you are getting client errors about missing intermediary certificates you have probably used `cert.pem` as your certificate instead of `fullchain.pem`.
+Certbot provides multiple TLS certificate files. If you are getting client errors about missing intermediary certificates you have probably used `cert.pem` as your certificate instead of `fullchain.pem`.
 
 InspIRCd ships with the `inspircd-genssl` tool that allows you to generate a self-signed certificate and key. You can use these for testing your server but you should not use them in production as they do not provide much security over using a plaintext connection and do not work with all clients. This tool will be removed in a future release.
diff --git a/docs/tutorials/index.md b/docs/tutorials/index.md
@@ -8,6 +8,6 @@ title: Tutorials
 
 ## Tutorials
 
-- [How to enable TLS (SSL) on your IRC network](/tutorials/enable-tls)
+- [How to enable TLS on your IRC network](/tutorials/enable-tls)
 - [How to install and configure InspIRCd](/4/installation)
 - [How to prevent spam on your IRC network](/tutorials/prevent-spam)
diff --git a/docs/tutorials/prevent-spam.md b/docs/tutorials/prevent-spam.md
@@ -60,9 +60,9 @@ If you want a softer option you can also use [the muteban module](/4/modules/mut
 /MODE #channel +b mute:unauthed:*!*@*.linodeusercontent.com
 ```
 
-### Require TLS (SSL)
+### Require TLS
 
-Some IRC spambots are very poorly written and do not support TLS (SSL). You can break these bots by requiring TLS (SSL) on your IRC network. This also has the benefit of preventing your users from having their chats snooped on. To do this you can either disable your plaintext listeners entirely or better still use the IRCv3 STS (Strict Transport Security) feature to redirect users of modern clients to your TLS (SSL) port.
+Some IRC spambots are very poorly written and do not support TLS. You can break these bots by requiring TLS on your IRC network. This also has the benefit of preventing your users from having their chats snooped on. To do this you can either disable your plaintext listeners entirely or better still use the IRCv3 STS (Strict Transport Security) feature to redirect users of modern clients to your TLS port.
 
 ```xml
 # These can go anywhere in your configuration
