I agree with this! SSL is a deprecated protocol and the protocol used nowadays is named "TLS" not "SSL". We can use "Force TLS" or "Force HTTPS" or "Force Secure Connection", any of this options is better than "Force SSL"

IMHO a problem also exists in the mail server config. Made a PR sometime ago for the mail server part. See #8520

Found the word SSL in some text strings:

/language/en-GB/en-GB.mod_login.ini
MOD_LOGIN_FIELD_USESECURE_DESC="Submit encrypted login data (requires SSL). Do not enable this option if Joomla is not accessible using the https:// protocol prefix."

/administrator/language/en-GB/en-GB.mod_login.ini
MOD_LOGIN_FIELD_USESECURE_DESC="Submit encrypted login data (requires SSL). Do not enable this option if Joomla is not accessible using the https:// protocol prefix."

/administrator/language/en-GB/en-GB.com_menus.ini
COM_MENUS_ITEM_FIELD_SECURE_DESC="Selects whether or not this link should use SSL and the Secure Site URL."

/administrator/language/en-GB/en-GB.com_config.ini
COM_CONFIG_FIELD_FORCE_SSL_DESC="Force site access to always occur under SSL (https) for selected areas. You will not be able to access selected areas under non-ssl. Note, you must have SSL enabled on your server to utilise this option."

/administrator/language/en-GB/en-GB.com_config.ini
COM_CONFIG_FIELD_FORCE_SSL_LABEL="Force SSL"

/administrator/language/en-GB/en-GB.com_config.ini
COM_CONFIG_FIELD_VALUE_SSL="SSL"

And the word TLS in other cases:

/language/en-GB/en-GB.ini
PHPMAILER_TLS="Could not start TLS"

/administrator/language/en-GB/en-GB.ini
PHPMAILER_TLS="Could not start TLS"

/administrator/language/en-GB/en-GB.plg_authentication_ldap.ini
PLG_LDAP_FIELD_NEGOCIATE_DESC="Negotiate TLS encryption with the LDAP server. This requires all traffic to and from the LDAP server to be encrypted."

/administrator/language/en-GB/en-GB.plg_authentication_ldap.ini
PLG_LDAP_FIELD_NEGOCIATE_LABEL="Negotiate TLS"

/administrator/language/en-GB/en-GB.com_config.ini
COM_CONFIG_FIELD_VALUE_TLS="TLS"

The COM_CONFIG_FIELD_VALUE_SSL and COM_CONFIG_FIELD_VALUE_TLS are related to mail server configuration as described in #8520.

And some references:

• Deprecating Secure Sockets Layer Version 3.0 (IETF): https://tools.ietf.org/html/rfc7568
• The Transport Layer Security (TLS) Protocol Version 1.2 (IETF): https://tools.ietf.org/html/rfc5246
• The Transport Layer Security (TLS) Protocol Version 1.3 (draft - IETF): https://tools.ietf.org/html/draft-ietf-tls-tls13

"HTTPS" in my opinion

Ah yes great question, finaly needed change that SSL by HTTPS (simply understand for all)

you know maybe why (poddle, logjam, etc.), so!

I see all agree. So, can anyone make a PR for this change?

late that maybe staging...alexonbalangue:patch-1

@alexonbalangue you made a fork of joomla repository, and made the changes in your fork. You also need to make a PR to joomla repository staging branch.
See https://docs.joomla.org/Using_the_Github_UI_to_Make_Pull_Requests

Also:
1. Please don't change the mail server configuration language variables. There is a PR for that already (see #8520)
2. Note, you must have TLS1.2+ enabled on your server to utilise this option, no you don't. You can use the https with SSLv2, SSLv3, TLS 1.0, TLS 1.1 and TLS 1.2 (and the future TLS 1.3 when it comes out), you shouldn't use it with SSL, but you can.
3. And, of course, use correct english in all language variables changed.

PR made #9588

Please test.

@brianteeman this can be closed now that we have a PR.