Merge pull request #112066 from v-hearya/master

205156 - ms.custom value added | updated

Author: cmcclister

articles/iot-hub/iot-hub-csharp-csharp-module-twin-getstarted.md

@@ -8,14 +8,15 @@ ms.devlang: csharp
 ms.topic: conceptual
 ms.date: 08/07/2019
 ms.author: menchi
+ms.custom: amqp
 ---
 
 # Get started with IoT Hub module identity and module twin (.NET)
 
 [!INCLUDE [iot-hub-selector-module-twin-getstarted](../../includes/iot-hub-selector-module-twin-getstarted.md)]
 
 > [!NOTE]
-> [Module identities and module 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 twin provide these capabilities for individual components of a device. On capable devices with multiple components, such as operating system based devices or firmware devices, module identities and module twins allow for isolated configuration and conditions for each component.
+> [Module identities and module 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 twin provide these capabilities for individual components of a device. On capable devices with multiple components, such as operating system based devices or firmware devices, module identities and module twins allow for isolated configuration and conditions for each component.
 
 At the end of this tutorial, you have two .NET console apps:
 

articles/iot-hub/iot-hub-csharp-csharp-schedule-jobs.md

@@ -8,6 +8,7 @@ services: iot-hub
 ms.topic: conceptual
 ms.date: 08/20/2019
 ms.author: robinsh
+ms.custom: mqtt
 ---
 
 # Schedule and broadcast jobs (.NET)

articles/iot-hub/iot-hub-csharp-csharp-twin-getstarted.md

@@ -9,6 +9,7 @@ ms.devlang: csharp
 ms.topic: conceptual
 ms.date: 08/26/2019
 ms.author: robinsh
+ms.custom: mqtt
 ---
 
 # Get started with device twins (.NET)

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

@@ -8,6 +8,7 @@ ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
 ms.date: 01/29/2018
+ms.custom:  [amqp, mqtt]
 ---
 
 # Cloud-to-device communications guidance

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

@@ -8,6 +8,7 @@ ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
 ms.date: 01/29/2018
+ms.custom: [amqp, mqtt]
 ---
 
 # Device-to-cloud communications guidance

articles/iot-hub/iot-hub-devguide-develop-for-constrained-devices.md

@@ -7,6 +7,7 @@ services: iot-hub
 ms.topic: conceptual
 ms.date: 05/24/2018
 ms.author: robinsh
+ms.custom: [amqp, mqtt]
 ---
 
 # Develop for constrained devices using Azure IoT C SDK
@@ -77,5 +78,5 @@ Another set of APIs without the _LL_ index is called the convenience layer, wher
 ## Next steps
 
 To learn more about Azure IoT C SDK architecture:
--	[Azure IoT C SDK source code](https://github.com/Azure/azure-iot-sdk-c/)
--	[Azure IoT device SDK for C introduction](iot-hub-device-sdk-c-intro.md)
+-    [Azure IoT C SDK source code](https://github.com/Azure/azure-iot-sdk-c/)
+-    [Azure IoT device SDK for C introduction](iot-hub-device-sdk-c-intro.md)

articles/iot-hub/iot-hub-devguide-device-twins.md

@@ -8,6 +8,7 @@ ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
 ms.date: 02/01/2020
+ms.custom: mqtt
 ---
 
 # Understand and use device twins in IoT Hub
@@ -193,7 +194,7 @@ The solution back end operates on the device twin using the following atomic ope
 
   - Body
 
-    This section includes all the twin changes in a JSON format. It uses the same format as a patch, with the difference that it can contain all twin sections: tags, properties.reported, properties.desired, and that it contains the “$metadata” elements. For example,
+    This section includes all the twin changes in a JSON format. It uses the same format as a patch, with the difference that it can contain all twin sections: tags, properties.reported, properties.desired, and that it contains the "$metadata" elements. For example,
 
     ```json
     {

articles/iot-hub/iot-hub-devguide-direct-methods.md

@@ -7,6 +7,7 @@ services: iot-hub
 ms.topic: conceptual
 ms.date: 07/17/2018
 ms.author: rezas
+ms.custom: [amqp, mqtt]
 ---
 
 # Understand and invoke direct methods from IoT Hub

articles/iot-hub/iot-hub-devguide-endpoints.md

@@ -8,6 +8,7 @@ ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
 ms.date: 06/10/2019
+ms.custom: [amqp, mqtt]
 ---
 
 # Reference - IoT Hub endpoints

articles/iot-hub/iot-hub-devguide-file-upload.md

@@ -8,6 +8,7 @@ ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
 ms.date: 11/07/2018
+ms.custom: mqtt
 ---
 
 # Upload files with IoT Hub