fix(iot): review faq (#4729)

* fix(iot): review faq

* Update pages/iot-hub/faq.mdx

* Update pages/iot-hub/faq.mdx

Co-authored-by: ldecarvalho-doc <[email protected]>

---------

Co-authored-by: ldecarvalho-doc <[email protected]>

Author: RoRoJ

pages/iot-hub/faq.mdx

@@ -5,26 +5,26 @@ meta:
 content:
   h1: IoT Hub FAQ
 dates:
-  validation: 2024-09-19
+  validation: 2025-03-27
 category: managed-services
 productIcon: IotProductIcon
 ---
 
 ## What is IoT Hub?
 
 IoT Hub is an IoT Platform as a service, it sits between connected devices and business-specific software.
-Connected devices is the common name for all devices able to communicate over the internet (via Wi-Fi or 4G for instance). Connected devices are everywhere and can be used in a very broad range of applications. They can be smartphones, doorbells, light bulbs, refrigerators, cars, or TVs. Even a web browser can act as a connected device.
+Connected devices is the common name for all devices able to communicate over the internet (via Wi-Fi or 4G, for instance). Connected devices are everywhere and can be used in a very broad range of applications. They can be smartphones, doorbells, light bulbs, refrigerators, cars, or TVs. Even a web browser can act as a connected device.
 
 [MQTT](https://mqtt.org/) is a lightweight and standardized publish/subscribe messaging transport protocol, designed for low-power usage, minimized data packets, and efficient distribution of information to one or many receivers. MQTT supports secure communication using TLS, and it is often used in IoT use cases.
 All kinds of connected devices supporting the MQTT protocol can be connected to IoT Hub. MQTT through WebSockets is also supported. There is no limitation to specific vendors.
-To learn more about what is a **Hub**, what is a **Device** and what is a **Route**, head over to our dedicated pages:
+To learn more about **Hubs**, **Devices*,* and **Routes**, head over to our dedicated pages:
 
 * [Scaleway IoT Hub Overview](/iot-hub/quickstart/)
 * [Hub](/iot-hub/reference-content/hubs/)
 * [Device](/iot-hub/concepts/#device)
 * [Route](/iot-hub/concepts/#routes)
 
-IoT Hub is only available at PAR1 (Paris, France) for the moment, other regions are planned.
+IoT Hub is only available in PAR1 (Paris, France).
 
 ## What are the differences between the IoT Hub offers?
 
@@ -47,12 +47,12 @@ For devices not supporting secure connections, it is possible to also enable pla
 
 ## Can you detail what messages are?
 MQTT is a Publish/Subscribe protocol (more info on the MQTT protocol here).
-A message is the base unit for data transmission, it mainly contains:
+A message is the base unit for data transmission. It contains:
 
 - a **topic**: the message information type identifier, such as fr/paris/weather. Devices that have subscribed to a topic will receive any message published to this topic.
 - a **payload**: the actual data to be transmitted. Can be anything (temperature, image, notification, …) in any format (binary, xml, json, yaml, …)
 
-The Hub will provide an endpoint to connect the devices to and supports the following protocols:
+The Hub will provide an endpoint to connect the devices to, and supports the following protocols:
 
 - `MQTTs`: `MQTT` over `TLS`, port `8883`
 - `MQTT`: Plaintext `MQTT`, port `1883`
@@ -67,7 +67,7 @@ It must also be used as the MQTT Client Identifier field during connection.
 If your software doesn't have a setting for Client ID, you can use the Device ID in the Username field instead. If no Device ID is found in the client ID field, but it is present in the Username field, the one used in the Username field will be used as the Client ID.
 
 ## My software/library limits MQTT client ID to 23 characters, what should I do?
-MQTT's specifications state The Server MUST allow ClientIds which are between 1 and 23 UTF-8 encoded bytes in length and The Server MAY allow ClientId's that contain more than 23 encoded bytes. Certain software/libraries restrict MQTT client ID field to 23 characters **maximum**.
+MQTT's specifications state The Server MUST allow ClientIds which are between 1 and 23 UTF-8 encoded bytes in length. The Server MAY allow ClientId's that contain more than 23 encoded bytes. Certain software/libraries restrict the MQTT client ID field to 23 characters **maximum**.
 
 If you fall into this situation, you can type your Device ID in the MQTT Username field. If no valid Device ID is found in the MQTT client ID field, but one is found in the MQTT Username field, the one found in the Username field will be used as the client ID.
 
@@ -86,7 +86,7 @@ When creating a “shared” Hub, your Devices connect to the same message broke
 On a dedicated or High-Availability Hub, you are the only customer on the message brokers, you can access this topic subtree.
 
 ## How are messages billed?
-Any MQTT message between the Hub and a Device will be billed. If the message is bigger than 4 kB, then each 4 kB chunk of the message will be counted billed as one message. For example, a 9 kB message will be billed as 3 messages.
+Any MQTT message between the Hub and a Device will be billed. If the message is bigger than 4 kB, then each 4 kB chunk of the message will be counted as a message for billing purposes. For example, a 9 kB message will be billed as 3 messages.
 
 ## What is the maximum message size?
 The maximum size for a message is 4 MB.