Fix various outdated TLS config references.

Author: sadiepowell

docs/4/modules/ssl_gnutls.yml

@@ -65,7 +65,7 @@ configuration:
     required: true
     default: null
     description: |-
-      The name of this TLS profile. This is used in `<bind:ssl>` for incoming connections and `<link:ssl>` for outgoing server connections.
+      The name of this TLS profile. This is used in `<bind:sslprofile>` for incoming connections and `<link:sslprofile>` for outgoing server connections.
   - name: provider
     type: Text
     required: true

docs/4/modules/ssl_openssl.yml

@@ -66,7 +66,7 @@ configuration:
     required: true
     default: null
     description: |-
-      The name of this TLS profile. This is used in `<bind:ssl>` for incoming connections and `<link:ssl>` for outgoing server connections.
+      The name of this TLS profile. This is used in `<bind:sslprofile>` for incoming connections and `<link:sslprofile>` for outgoing server connections.
   - name: provider
     type: Text
     required: true

docs/faq.md

@@ -63,7 +63,7 @@ Server operators do not automatically get channel privileges by default. You can
 
 You are trying to connect using TLS but your server is not configured to listen for TLS connections.
 
-Check that you have a TLS module loaded and that your bind tag has the name of a TLS 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:sslprofile>`.
 
 If you're using v3.7.0 or newer you can also use the `inspircd-testssl` script to help diagnose this issue.
 

docs/tutorials/enable-tls.md

@@ -52,7 +52,7 @@ InspIRCd ships with a tool named `inspircd-testssl` on binary installations and
 
 ### Common mistakes
 
-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 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 will not work in v4. You must now configure a `<sslprofile>` instead.
 
 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.