Updates

Author: gsteve88

articles/iot-hub/how-to-device-twins.md

@@ -8,7 +8,7 @@ manager: lizross
 ms.service: iot-hub
 ms.devlang: csharp
 ms.topic: how-to
-ms.date: 07/12/2024
+ms.date: 09/10/2024
 zone_pivot_groups: iot-hub-howto-c2d-1
 ms.custom: mqtt, devx-track-csharp, devx-track-dotnet
 ---
@@ -17,16 +17,19 @@ ms.custom: mqtt, devx-track-csharp, devx-track-dotnet
 
 Use the Azure IoT Hub device SDK and service SDK to develop applications that handle common device twin tasks. Device twins are JSON documents that store device state information including metadata, configurations, and conditions. IoT Hub persists a device twin for each device that connects to it. You can use device twins to:
 
-* Store device metadata from your solution back end.
-* Report current state information such as available capabilities and conditions, for example, the connectivity method used, from your device app.
-* Synchronize the state of long-running workflows, such as firmware and configuration updates, between a device app and a back-end app.
-* Query your device metadata, configuration, or state.
+* Store device metadata from your solution back end
+* Report current state information such as available capabilities and conditions, for example, the connectivity method used, from your device app
+* Synchronize the state of long-running workflows, such as firmware and configuration updates, between a device app and a back-end app
+* Query your device metadata, configuration, or state
 
 For more information about device twins, including when to use device twins, see [Understand device twins](iot-hub-devguide-device-twins.md).
 
 [!INCLUDE [iot-hub-basic](../../includes/iot-hub-basic-whole.md)]
 
-This article shows you how to develop two types of applications. Device apps can handle requests to update desired properties and respond with changes to reported properties. Service apps can update device twin tags, set new desired properties, and query devices based on device twin values.
+This article shows you how to develop two types of applications:
+
+* Device apps can handle requests to update desired properties and respond with changes to reported properties.
+* Service apps can update device twin tags, set new desired properties, and query devices based on device twin values.
 
 > [!NOTE]
 > This article is meant to complement [Azure IoT SDKs](iot-hub-devguide-sdks.md) samples that are referenced from within this article. You can use SDK tools to build both device and back-end applications.
@@ -37,8 +40,6 @@ This article shows you how to develop two types of applications. Device apps can
 
 * **A registered device**. Some SDK calls require the device primary connection string, so make a note of the connection string.
 
-* Make sure that **port 8883** is open in your firewall. The device sample in this article uses MQTT protocol, which communicates over port 8883. This port may be blocked in some corporate and educational network environments. For more information and ways to work around this issue, see [Connecting to IoT Hub (MQTT)](../iot/iot-mqtt-connect-to-iot-hub.md#connecting-to-iot-hub).
-
 * **IoT Hub service connection string**
 
   In this article, you create a back-end service that adds desired properties to a device twin and then queries the identity registry to find all devices with reported properties that have been updated accordingly. Your service needs the **service connect** permission to modify desired properties of a device twin, and it needs the **registry read** permission to query the identity registry. There is no default shared access policy that contains only these two permissions, so you need to create one.