fix: spelling errors detected by typos

Author: id

_typos.toml

@@ -48,4 +48,4 @@ Sur = "Sur"
 iif = "iif"
 
 [files]
-extend-exclude = ["redocly", "cfg-manual-docgen"]
+extend-exclude = ["redocly", "cfg-manual-docgen", "hocon"]

dir.yaml

@@ -6,7 +6,7 @@
 # - A doc node may have edition: ee for enterprise only content
 #
 # Grouping node
-# - Must have a 'title_en' (English), 'title_cn' (Chinese), 'title_ja' (Japanese) is optional wehn no need to translate. e.g. FAQ
+# - Must have a 'title_en' (English), 'title_cn' (Chinese), 'title_ja' (Japanese) is optional when no need to translate. e.g. FAQ
 # - Parent nodes must NOT have a 'path'
 #
 # Content node can be one of:

en_US/changes/changes-ee-v5.md

@@ -572,7 +572,7 @@ Make sure to check the breaking changes and known issues before upgrading to EMQ
 
 - [#14192](https://github.com/emqx/emqx/pull/14192) Allowed will messages to be sent by the clients that disconnect because of authentication/authorization expiration. Previously, such clients could not send a will message because the sending occurred just after the authorization expiration, so the message could not pass the authorization rules.
 
-- [#14122](https://github.com/emqx/emqx/pull/14122) Fixed handling of `PUBACK` and `PUBREC`/`PUBCOMP` when the published message has QoS 2 and 1, repectively.
+- [#14122](https://github.com/emqx/emqx/pull/14122) Fixed handling of `PUBACK` and `PUBREC`/`PUBCOMP` when the published message has QoS 2 and 1, respectively.
 
   Prior to this fix, the broker would accept `PUBACK` and `PUBREC`/`PUBCOMP` packets from clients referencing packet identifiers that corresponded to messages with QoS 2 and 1, respectively. Now, the broker will disconnect clients that behave like this.
 
@@ -603,7 +603,7 @@ Make sure to check the breaking changes and known issues before upgrading to EMQ
 
   Note: while performing a rolling upgrade, this API may not list all existing clients until all nodes are migrated. As a workaround, if HTTP API requests are issued to old core nodes, all clients can be listed before all nodes are fully upgraded.
 
-- [#14182](https://github.com/emqx/emqx/pull/14182) Previously, if a delayed message was published via the `POST /publish` HTTP API, a 202 reponse with the reason code 16 ("no matching subscribers") would be returned. Now, a 200 response is sent along with the message identifier.
+- [#14182](https://github.com/emqx/emqx/pull/14182) Previously, if a delayed message was published via the `POST /publish` HTTP API, a 202 response with the reason code 16 ("no matching subscribers") would be returned. Now, a 200 response is sent along with the message identifier.
 
 #### MQTT Durable Sessions
 
@@ -676,7 +676,7 @@ Make sure to check the breaking changes and known issues before upgrading to EMQ
 
   Previously, upon (re)starting the Connector, it would perform one `ListStreams` request for each worker in its connection pool.  Additionally, each periodic health check would do `ListStreams` for each worker.  The Action health check would do `DescribeStream` for each connection worker in the pool.
 
-  Now, the Connector no longer performs the initial `ListStreams` upon (re)starting.  Both Connector and Action attempt to check if at least one worker has a healthy response from their respective API requests: the request is attempted by each worker serially, and the Connector or Action is considered `connected` upon the first successful response received.  Thus, in the best case scenario, each Connector and each Action will do 1 API request each per health check, regardless of pool sizea.  In the worst case scenario, each worker in the pool might still perform one request each, if they fail to receive a sucessful response.
+  Now, the Connector no longer performs the initial `ListStreams` upon (re)starting.  Both Connector and Action attempt to check if at least one worker has a healthy response from their respective API requests: the request is attempted by each worker serially, and the Connector or Action is considered `connected` upon the first successful response received.  Thus, in the best case scenario, each Connector and each Action will do 1 API request each per health check, regardless of pool sizea.  In the worst case scenario, each worker in the pool might still perform one request each, if they fail to receive a successful response.
 
 - [#14767](https://github.com/emqx/emqx/pull/14767) Kafka producer now smoothly handles Kafka topic re-creation with fewer partitions.
   Previously, the lost partition producers may linger behind to retry and write large amount of error logs.
@@ -696,15 +696,15 @@ Make sure to check the breaking changes and known issues before upgrading to EMQ
 
 - [#15087](https://github.com/emqx/emqx/pull/15087) Fixed an issue with `hocon` library in which, if one had any string one-liner field that ended in a lone backslash, the configuration file would fail to be parsed later.
 
-#### Plugin and Extention
+#### Plugin and Extension
 
 - [#15073](https://github.com/emqx/emqx/pull/15073) Added a validator for the server URL in the `exhook` configuration. This ensures that only valid URLs can be saved. Invalid URLs will now trigger an error and prevent being saved, which helps avoid issues during the import process, where previously invalid URLs could be accepted.
 
 - [#14774](https://github.com/emqx/emqx/pull/14774) Resolved plugin related issues. Fixed a retrieval issue with the plugin configuration file from cluster nodes when initiating the plugin without an existing configuration file.
 
 - [#14826](https://github.com/emqx/emqx/pull/14826) Fixed the issue where the Exhook server's return of "IGNORE" was not taking effect.
 
-- [#15018](https://github.com/emqx/emqx/pull/15018) Fixed a bug with Exhook in which attemtping to import an invalid `exhook` configuration via the CLI would result in a crash with a `badarg` error.
+- [#15018](https://github.com/emqx/emqx/pull/15018) Fixed a bug with Exhook in which attempting to import an invalid `exhook` configuration via the CLI would result in a crash with a `badarg` error.
 
 - [#15108](https://github.com/emqx/emqx/pull/15108) ExHook now includes a built-in gRPC health check mechanism, ensuring that the connection status accurately reflects the actual availability of the external hook server.
 

en_US/deploy/install.md

@@ -142,15 +142,15 @@ The table below introduces the files and subfolders of some directories.
 | Directory | Description         | Permissions | Files                                                        |
 | --------- | ------------------- | ----------- | ------------------------------------------------------------ |
 | bin       | Executables         | Read        | `emqx` and `emqx.cmd`: Executables of EMQX. For details, see [Command Line Interface](../admin/cli.md). |
-| etc       | Configuration files | Read        | `base.hocon`: Base configuration which can be overriden from runtime config changes.<br /><br />`emqx.conf`: Static configurations which cannot be overridden.<br /><br />`emqx-example-en.conf`: Demo configuration files of EMQX, contains all the configurable items.<br /><br />`acl.conf`: Default ACl rules.<br /><br />`vm.args`: Operating parameters of the Erlang virtual machine.<br /><br />`certs/`: X.509 keys and certificate files for EMQX SSL listeners, may also be used in the SSL/TLS connection when integrating with external systems. |
+| etc       | Configuration files | Read        | `base.hocon`: Base configuration which can be overridden from runtime config changes.<br /><br />`emqx.conf`: Static configurations which cannot be overridden.<br /><br />`emqx-example-en.conf`: Demo configuration files of EMQX, contains all the configurable items.<br /><br />`acl.conf`: Default ACl rules.<br /><br />`vm.args`: Operating parameters of the Erlang virtual machine.<br /><br />`certs/`: X.509 keys and certificate files for EMQX SSL listeners, may also be used in the SSL/TLS connection when integrating with external systems. |
 | data      | Operating data      | Write       | `authz`: Stores file authorization rules uploaded by REST API or Dashboard. For details, see [Authorization - File](../access-control/authz/file.md). <br /><br />`certs`: Stores certificate files uploaded by REST API or Dashboard.<br /><br />`configs`: Stores configuration files generated at boot, or configuration overrides by changes from API or CLI.<br /><br />`mnesia`: Built-in database to store EMQX operating data, including alarm records, authentication and authorization data of the clients, Dashboard user information, etc. **If the directory is deleted, all these operating data will be lost.**<br /><br />  —  May contain subdirectories named after different node, e.g., `[email protected]`. Note: In case of node renaming, you should also delete or remove the corresponding subdirectory. <br /><br />  —  Can use command `emqx ctl mnesia` to  query the built-in database. For details, see [Management Command CLI](https://docs.emqx.com/en/enterprise/v5.0/admin/cli.html).<br /><br />`patches`: Stores the `.beam` files for EMQX to load as a hot patch. Can be used for a quick fix.<br /><br />`trace`: Online tracing log files.<br /><br />In production, it is recommended to periodically backup the `data` directory (excluding the `trace` folder )  for data safety. |
 | log       | Operating logs      | Read        | `emqx.log.*`: Operation logs of EMQX, for more information, see [logs](../observability/log.md). |
 
 :::tip
 
 EMQX stores the configuration information in the `data/configs` and the `etc` directory. The `etc` directory stores read-only configuration files, while configuration updates from the Dashboard or REST API are saved in the `data/configs` directory to support hot configuration reloads at runtime.
 
-- `etc/base.hocon`: Base configuration which can be overriden from runtime config changes.
+- `etc/base.hocon`: Base configuration which can be overridden from runtime config changes.
 - `etc/emqx.conf`: Static configuration which cannot be overridden.
 - `data/configs/cluster.hocon`: Runtime configuration overrides.