Added standard tier only note to module twin how-to topics

Author: JimacoMS4

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

@@ -17,6 +17,8 @@ ms.custom:  [amqp, mqtt]
 
 [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 provides 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 devices or firmware devices, it allows for isolated configuration and conditions for each component.
 
+[!INCLUDE [iot-hub-basic](../../includes/iot-hub-basic-whole.md)]
+
 At the end of this article, you have two C apps:
 
 * **CreateIdentities**: creates a device identity, a module identity and associated security key to connect your device and module clients.

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

@@ -17,6 +17,8 @@ ms.custom: "amqp, devx-track-csharp"
 
 [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 devices or firmware devices, module identities and module twins allow for isolated configuration and conditions for each component.
 
+[!INCLUDE [iot-hub-basic](../../includes/iot-hub-basic-whole.md)]
+
 At the end of this article, you have two .NET console apps:
 
 * **CreateIdentities**: creates a device identity, a module identity, and associated security key to connect your device and module clients.

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

@@ -17,6 +17,8 @@ ms.custom: amqp, devx-track-js
 
 [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 provides 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 devices or firmware devices, it allows for isolated configuration and conditions for each component.
 
+[!INCLUDE [iot-hub-basic](../../includes/iot-hub-basic-whole.md)]
+
 At the end of this article, you have two Node.js apps:
 
 * **CreateIdentities**: creates a device identity, a module identity, and associated security keys to connect your device and module clients.

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

@@ -17,6 +17,8 @@ ms.custom: "amqp, devx-track-csharp"
 
 [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 devices or firmware devices, module identities and module twins allow for isolated configuration and conditions for each component.
 
+[!INCLUDE [iot-hub-basic](../../includes/iot-hub-basic-whole.md)]
+
 In this article, you will learn how to:
 
 * Create a module identity in the portal.

articles/iot-hub/iot-hub-python-python-c2d.md

@@ -34,7 +34,7 @@ At the end of this article, you run two Python console apps:
 >You can find more information on cloud-to-device messages in the [IoT Hub developer guide](iot-hub-devguide-messaging.md).
 
 > [!NOTE]
-> See [Azure IoT SDKs](iot-hub-devguide-sdks.md) for more information about the SDK tools available to build both device and back-end apps.
+> IoT Hub has SDK support for many device platforms and languages (C, Java, Python, and JavaScript) through the [Azure IoT device SDKs](iot-hub-devguide-sdks.md).
 
 ## Prerequisites
 

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

@@ -29,7 +29,7 @@ These files are typically batch processed in the cloud, using tools such as [Azu
 At the end of this article, you run the Python console app **FileUpload.py**, which uploads a file to storage using the Python Device SDK.
 
 > [!NOTE]
-> See [Azure IoT SDKs](iot-hub-devguide-sdks.md) for more information about the SDK tools available to build both device and back-end apps.
+> IoT Hub has SDK support for many device platforms and languages (C, Java, Python, and JavaScript) through the [Azure IoT device SDKs](iot-hub-devguide-sdks.md).
 
 [!INCLUDE [iot-hub-include-x509-ca-signed-file-upload-support-note](../../includes/iot-hub-include-x509-ca-signed-file-upload-support-note.md)]
 

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

@@ -17,6 +17,8 @@ ms.custom: devx-track-python
 
 [Module identities and module 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 a back-end application to configure a device and provide visibility on the device's conditions, module identities and module twins provide these capabilities for individual components of a device. On capable devices with multiple components, such as operating system devices or firmware devices, they allow for isolated configuration and conditions for each component.
 
+[!INCLUDE [iot-hub-basic](../../includes/iot-hub-basic-whole.md)]
+
 At the end of this article, you have three Python apps:
 
 * **CreateModule**: creates a device identity, a module identity, and associated security keys to connect your device and module clients.