Updates to intro and .net article

Author: gsteve88

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

@@ -15,14 +15,14 @@ ms.custom: mqtt, devx-track-csharp, devx-track-dotnet
 
 # Get started with IoT Hub module identities and module identity twins
 
-[Module identities and module identity twins](iot-hub-devguide-module-twins.md) are similar to Azure IoT Hub device identity and device twin, but provide finer granularity. While Azure IoT Hub device identity and device twin enable the back-end application to configure a device and provide visibility on the device's conditions, a module identity and module identity twin provide these capabilities for individual components of a device. On capable devices with multiple components, such as operating system devices or firmware devices, module identities and module identity twins allow for isolated configuration and conditions for each component.
+[Module identities and module identity twins](iot-hub-devguide-module-twins.md) are similar to Azure IoT Hub device identities and device twins, but provide finer granularity. While Azure IoT Hub device identities and device twins enable the back-end application to configure a device and provide visibility on the device's conditions, a module identity and module identity twin provide these capabilities for individual components of a device. On capable devices with multiple components, such as operating system devices or firmware devices, module identities and module identity twins allow for isolated configuration and conditions for each component.
 
 [!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 module desired properties and respond with changes to reported properties.
-* Service apps that can set new desired properties.
+* Device apps that view and update reported properties and handle requests to update module desired properties.
+* Service apps that can add modules and read and set new desired properties.
 
 > [!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.

includes/iot-hub-howto-module-twins-dotnet.md

@@ -7,7 +7,7 @@ ms.author: kgremban
 ms.service: iot-hub
 ms.devlang: csharp
 ms.topic: include
-ms.date: 09/03/2024
+ms.date: 10/02/2024
 ms.custom: mqtt, devx-track-csharp, devx-track-dotnet
 ---
 
@@ -34,22 +34,17 @@ Device client applications written in C# require the **Microsoft.Azure.Devices.C
 Add these `using` statements to use the device library.
 
 ```csharp
-using Microsoft.Azure.Devices;
-using Microsoft.Azure.Devices.Common.Exceptions;
+using Microsoft.Azure.Devices.Client;
+using Microsoft.Azure.Devices.Shared;
 ```
 
 ### Connect to a device
 
 The [ModuleClient](/dotnet/api/microsoft.azure.devices.client.moduleclient) class exposes all the methods required to interact with module identity twins from the device.
 
-Connect to the device using the [CreateFromConnectionString](/dotnet/api/microsoft.azure.devices.client.moduleclient.createfromconnectionstring) method with the module connection string. The method connects using the default AMQP transport.
+Connect to the device using the [CreateFromConnectionString](/dotnet/api/microsoft.azure.devices.client.moduleclient.createfromconnectionstring) method with the module connection string. `CreateFromConnectionString` connects using the default AMQP transport.
 
 ```csharp
-using Microsoft.Azure.Devices.Client;
-using Microsoft.Azure.Devices.Shared;
-using System.Threading.Tasks;
-using Newtonsoft.Json;
-
 static string ModuleConnectionString = "{Device module connection string}";
 private static ModuleClient _moduleClient = null;
 
@@ -83,10 +78,10 @@ For example:
 ```csharp
 try
 {
-Console.WriteLine("Sending sample start time as reported property");
-TwinCollection reportedProperties = new TwinCollection();
-reportedProperties["DateTimeLastAppLaunch"] = DateTime.UtcNow;
-await _moduleClient.UpdateReportedPropertiesAsync(reportedProperties);
+  Console.WriteLine("Sending sample start time as reported property");
+  TwinCollection reportedProperties = new TwinCollection();
+  reportedProperties["DateTimeLastAppLaunch"] = DateTime.UtcNow;
+  await _moduleClient.UpdateReportedPropertiesAsync(reportedProperties);
 }
 catch (Exception ex)
 {
@@ -141,12 +136,22 @@ The [RegistryManager](/dotnet/api/microsoft.azure.devices.registrymanager) class
 
 This section describes how to create backend application code to:
 
+* Add a module
 * Read and update module fields
 
 ### Add service NuGet Package
 
 Backend service applications require the **Microsoft.Azure.Devices** NuGet package.
 
+### Service using statements
+
+Add these `using` statements to use the service library.
+
+```csharp
+using Microsoft.Azure.Devices;
+using Microsoft.Azure.Devices.Shared;
+```
+
 ### Connect to IoT hub
 
 Connect a backend application to a device using [CreateFromConnectionString](/dotnet/api/microsoft.azure.devices.registrymanager.createfromconnectionstring).
@@ -159,7 +164,6 @@ The SDK methods in this section require these shared access policy permissions:
 As a parameter to `CreateFromConnectionString`, supply a shared access policy connection string that includes these permissions. For more information about shared access policies, see [Control access to IoT Hub with shared access signatures](/azure/iot-hub/authenticate-authorize-sas).
 
 ```csharp
-using Microsoft.Azure.Devices;
 static RegistryManager registryManager;
 static string connectionString = "{IoT hub shared access policy connection string}";
 registryManager = RegistryManager.CreateFromConnectionString(connectionString);
@@ -195,11 +199,11 @@ Console.WriteLine("Generated module key: {0}", module.Authentication.SymmetricKe
 
  Call [GetModuleAsync](/dotnet/api/microsoft.azure.devices.registrymanager.getmoduleasync) to retrieve current module identity twin fields into a [Module](/dotnet/api/microsoft.azure.devices.module) object.
 
-The `Module` class includes [properties](/dotnet/api/microsoft.azure.devices.shared.twin?&#properties) that correspond to each section of a module. Use the `Module` class properties to view and update module identity twin fields. You can use the `Module` object properties to update multiple fields before writing the updates to the device using `UpdateModuleAsync`.
+The `Module` class includes [properties](/dotnet/api/microsoft.azure.devices.shared.twin?&#properties) that correspond to sections of an identity module twin. Use the `Module` class properties to view and update module identity twin fields. You can use the `Module` object properties to update multiple fields before writing the updates to the device using `UpdateModuleAsync`.
 
 After making module identity twin field updates, call [UpdateModuleAsync](/dotnet/api/microsoft.azure.devices.registrymanager.updatemoduleasync) to write `Module` object field updates back to a device. Use `try` and `catch` logic coupled with an error handler to catch incorrectly formatted patch errors from `UpdateModuleAsync`.
 
-This example retrieves a module into a `Module` object, updates the `module`, and then updates the module in IoT Hub using `UpdateModuleAsync`.
+This example retrieves a module into a `Module` object, updates the `module` `LastActivityTime` property, and then updates the module in IoT Hub using `UpdateModuleAsync`.
 
 ```csharp
 // Retrieve the module
@@ -221,8 +225,8 @@ catch (Exception e)
 
 ### Other module API
 
-* [GetModulesOnDeviceAsync](/dotnet/api/microsoft.azure.devices.registrymanager.getmodulesondeviceasync) - Retrieves the module identities on a device.
-* [RemoveModuleAsync](/dotnet/api/microsoft.azure.devices.registrymanager.removemoduleasync) - Deletes a previously registered module from a device.
+* [GetModulesOnDeviceAsync](/dotnet/api/microsoft.azure.devices.registrymanager.getmodulesondeviceasync) - Retrieves the module identities on a device
+* [RemoveModuleAsync](/dotnet/api/microsoft.azure.devices.registrymanager.removemoduleasync) - Deletes a previously registered module from a device
 
 ### SDK service sample