Merge pull request #222672 from KennedyDMSFT/US44747-06

December freshness (6/11)

Author: JamesJBarnett

articles/iot-hub/iot-hub-devguide-d2c-guidance.md

@@ -7,13 +7,13 @@ ms.author: kgremban
 ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
-ms.date: 01/29/2018
+ms.date: 12/27/2022
 ms.custom: [amqp, mqtt, 'Role: Cloud Development', 'Role: IoT Device']
 ---
 
 # Device-to-cloud communications guidance
 
-When sending information from the device app to the solution back end, IoT Hub exposes three options:
+IoT Hub exposes three options for sending information from the device app to the solution back end:
 
 * [Device-to-cloud messages](iot-hub-devguide-messages-d2c.md) for time series telemetry and alerts.
 
@@ -23,19 +23,19 @@ When sending information from the device app to the solution back end, IoT Hub e
 
 [!INCLUDE [iot-hub-basic](../../includes/iot-hub-basic-partial.md)]
 
-Here is a detailed comparison of the various device-to-cloud communication options.
+Here's a detailed comparison of the various device-to-cloud communication options.
 
 | Factor | Device-to-cloud messages | Device twin's reported properties | File uploads |
 | ---- | ------- | ---------- | ---- |
 | Scenario | Telemetry time series and alerts. For example, 256-KB sensor data batches sent every 5 minutes. | Available capabilities and conditions. For example, the current device connectivity mode such as cellular or WiFi. Synchronizing long-running workflows, such as configuration and software updates. | Video or other large media files. Large (typically compressed) telemetry batches. |
-| Storage and retrieval | Temporarily stored by IoT Hub, up to 7 days. Only sequential reading. | Stored by IoT Hub in the device twin. Retrievable using the [IoT Hub query language](iot-hub-devguide-query-language.md). | Stored in user-provided Azure Storage account. |
+| Storage and retrieval | Temporarily stored by IoT Hub, up to seven days. Only sequential reading. | Stored by IoT Hub in the device twin. Retrievable using the [IoT Hub query language](iot-hub-devguide-query-language.md). | Stored in user-provided Azure Storage account. |
 | Size | Up to 256-KB messages. | Maximum reported properties size is 32 KB. | Maximum file size supported by Azure Blob Storage. |
-| Frequency | High. For more information, see [IoT Hub limits](iot-hub-devguide-quotas-throttling.md). | Medium. For more information, see [IoT Hub limits](iot-hub-devguide-quotas-throttling.md). | Low. For more information, see [IoT Hub limits](iot-hub-devguide-quotas-throttling.md). |
+| Frequency | High. For more information, see [IoT Hub quotas and throttling](iot-hub-devguide-quotas-throttling.md). | Medium. For more information, see [IoT Hub quotas and throttling](iot-hub-devguide-quotas-throttling.md). | Low. For more information, see [IoT Hub quotas and throttling](iot-hub-devguide-quotas-throttling.md). |
 | Protocol | Available on all protocols. | Available using MQTT or AMQP. | Available when using any protocol, but requires HTTPS on the device. |
 
 An application may need to send information both as a telemetry time series or alert and make it available in the device twin. In this scenario, you can choose one of the following options:
 
 * The device app sends a device-to-cloud message and reports a property change.
 * The solution back end can store the information in the device twin's tags when it receives the message.
 
-Since device-to-cloud messages enable a much higher throughput than device twin updates, it is sometimes desirable to avoid updating the device twin for every device-to-cloud message.
+Since device-to-cloud messages enable a much higher throughput than device twin updates, it's sometimes desirable to avoid updating the device twin for every device-to-cloud message.