yuanbiao
/
emqx
1
0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: fix typos

This commit is contained in:
Zaiming (Stone) Shi 2022-10-27 20:09:31 +02:00
parent ed8286aff7
commit 4cadb86b18
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
apps/emqx/i18n/emqx_schema_i18n.conf
View File

@ -1529,7 +1529,7 @@ common_ssl_opts_schema_versions {
en: """
All TLS/DTLS versions to be supported.<br/>
NOTE: PSK ciphers are suppressed by 'tlsv1.3' version config.<br/>
In case PSK cipher suites are intended, make sure to configured
In case PSK cipher suites are intended, make sure to configure
<code>['tlsv1.2', 'tlsv1.1']</code> here.
"""
zh: """

6
rel/emqx_conf.template.en.md
View File

@ -146,7 +146,7 @@ For example, this environment variable sets an array value.
export EMQX_LISTENERS__SSL__L1__AUTHENTICATION__SSL__CIPHERS='["TLS_AES_256_GCM_SHA384"]'
```
However this also means a string value should be quoted if it happen to contain special
However this also means a string value should be quoted if it happens to contain special
characters such as `=` and `:`.
For example, a string value `"localhost:1883"` would be
@ -248,9 +248,9 @@ authentication=[{enable=true}]
#### TLS/SSL ciphers
Starting from v5.0.6, EMQX no longer pre-populate the ciphers list with a default
Starting from v5.0.6, EMQX no longer pre-populates the ciphers list with a default
set of cipher suite names.
Instead, the default ciphers are applyed at runtime when starting the listener
Instead, the default ciphers are applied at runtime when starting the listener
for servers, or when establishing a TLS connection as a client.
Below are the default ciphers selected by EMQX.