Metadata and filename refresh -- c2d

kgremban · kgremban · commit 6abb29e08baa · 2023-03-15T13:37:04.000-07:00
diff --git a/articles/iot-hub/.openpublishing.redirection.iot-hub.json b/articles/iot-hub/.openpublishing.redirection.iot-hub.json
@@ -80,6 +80,31 @@
       "redirect_url": "/azure/iot-develop/quickstart-send-telemetry-iot-hub?pivots=programming-language-python",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/iot-hub/iot-hub-csharp-csharp-c2d.md",
+      "redirect_url": "/azure/iot-hub/c2d-messaging-dotnet",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/iot-hub/iot-hub-python-python-c2d.md",
+      "redirect_url": "/azure/iot-hub/c2d-messaging-python",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/iot-hub/iot-hub-node-node-c2d.md",
+      "redirect_url": "/azure/iot-hub/c2d-messaging-node",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/iot-hub/iot-hub-java-java-c2d.md",
+      "redirect_url": "/azure/iot-hub/c2d-messaging-java",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/iot-hub/iot-hub-ios-swift-c2d.md",
+      "redirect_url": "/azure/iot-hub/c2d-messaging-ios",
+      "redirect_document_id": true
+    },
     {
       "source_path_from_root": "/articles/iot-hub/iot-hub-devguide-glossary.md",
       "redirect_url": "/azure/iot-fundamentals/iot-glossary/",
diff --git a/articles/iot-hub/TOC.yml b/articles/iot-hub/TOC.yml
@@ -310,20 +310,20 @@
         - name: Send cloud-to-device messages
           items:
             - name: .NET
-              displayName: cloud-to-device messages, C2D
-              href: iot-hub-csharp-csharp-c2d.md
+              displayName: cloud-to-device messages, C2D, csharp, C#
+              href: c2d-messaging-dotnet.md
             - name: Python
               displayName: cloud-to-device messages, C2D
-              href: iot-hub-python-python-c2d.md
+              href: c2d-messaging-python.md
             - name: Node.js
               displayName: cloud-to-device messages, C2D
-              href: iot-hub-node-node-c2d.md
+              href: c2d-messaging-node.md
             - name: Java
               displayName: cloud-to-device messages, C2D
-              href: iot-hub-java-java-c2d.md
+              href: c2d-messaging-java.md
             - name: iOS
               displayName: cloud-to-device messages, C2D
-              href: iot-hub-ios-swift-c2d.md
+              href: c2d-messaging-ios.md
         - name: Upload files from devices
           items:
             - name: .NET
diff --git a/articles/iot-hub/c2d-messaging-dotnet.md b/articles/iot-hub/c2d-messaging-dotnet.md
@@ -1,14 +1,14 @@
 ---
-title: Cloud-to-device messages with Azure IoT Hub (.NET) | Microsoft Docs
-description: How to send cloud-to-device messages to a device from an Azure IoT hub using the Azure IoT SDKs for .NET. You modify a device app to receive cloud-to-device messages and modify a back-end app to send the cloud-to-device messages.
+title: Send cloud-to-device messages (.NET)
+titleSuffix: Azure IoT Hub
+description: How to send cloud-to-device messages from a back-end app and receive them on a device app using the Azure IoT SDKs for .NET.
 author: kgremban
 
+ms.author: kgremban
 ms.service: iot-hub
-services: iot-hub
 ms.devlang: csharp
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 10/20/2021
-ms.author: kgremban
 ms.custom:  [amqp, mqtt, 'Role: Cloud Development', 'Role: IoT Device', devx-track-csharp]
 ---
 
@@ -78,14 +78,14 @@ In this section, modify your device app to receive cloud-to-device messages from
    ReceiveC2dAsync();
    ```
 
-The `ReceiveAsync` method asynchronously returns the received message at the time that it is received by the device. It returns *null* after a specifiable timeout period. In this example, the default of one minute is used. When the app receives a *null*, it should continue to wait for new messages. This requirement is the reason for the `if (receivedMessage == null) continue` line.
+The `ReceiveAsync` method asynchronously returns the received message at the time that it's received by the device. It returns *null* after a specifiable timeout period. In this example, the default of one minute is used. When the app receives a *null*, it should continue to wait for new messages. This requirement is the reason for the `if (receivedMessage == null) continue` line.
 
 The call to `CompleteAsync()` notifies IoT Hub that the message has been successfully processed and that the message can be safely removed from the device queue. The device should call this method when its processing successfully completes regardless of the protocol it's using.
 
 With AMQP and HTTPS, but not MQTT, the device can also:
 
 * Abandon a message, which results in IoT Hub retaining the message in the device queue for future consumption.
-* Reject a message, which which permanently removes the message from the device queue.
+* Reject a message, which permanently removes the message from the device queue.
 
 If something happens that prevents the device from completing, abandoning, or rejecting the message, IoT Hub will, after a fixed timeout period, queue the message for delivery again. For this reason, the message processing logic in the device app must be *idempotent*, so that receiving the same message multiple times produces the same result.
 
diff --git a/articles/iot-hub/c2d-messaging-ios.md b/articles/iot-hub/c2d-messaging-ios.md
@@ -1,12 +1,13 @@
 ---
-title: Cloud-to-device messages with Azure IoT Hub (iOS) | Microsoft Docs
-description: How to send cloud-to-device messages to a device from an Azure IoT hub using the Azure IoT SDKs for iOS. 
+title: Send cloud-to-device messages (iOS)
+titleSuffix: Azure IoT Hub
+description: How to send cloud-to-device messages from a back-end app and receive them on a device app using the Azure IoT SDKs for iOS.
 author: kgremban
+
+ms.author: kgremban
 ms.service: iot-hub
-services: iot-hub
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 04/19/2018
-ms.author: kgremban
 ms.custom: mqtt
 ---
 
@@ -65,7 +66,7 @@ Along with installing the pods required for your project, the installation comma
 
 ### Run the sample device application
 
-1. Retrieve the connection string for your device. You can copy this string from the [Azure portal](https://portal.azure.com) in the device details blade, or retrieve it with the following CLI command:
+1. Retrieve the connection string for your device. You can copy this string from the [Azure portal](https://portal.azure.com) in the device details page, or retrieve it with the following CLI command:
 
     ```azurecli-interactive
     az iot hub device-identity connection-string show --hub-name {YourIoTHubName} --device-id {YourDeviceID} --output table
@@ -91,9 +92,9 @@ Along with installing the pods required for your project, the installation comma
 
 ## Send a cloud-to-device message
 
-You are now ready to receive cloud-to-device messages. Use the Azure portal to send a test cloud-to-device message to your simulated IoT device.
+You're now ready to receive cloud-to-device messages. Use the Azure portal to send a test cloud-to-device message to your simulated IoT device.
 
-1. In the **iOS App Sample** app running on the simulated IoT device, click **Start**. The application starts sending device-to-cloud messages, but also starts listening for cloud-to-device messages.
+1. In the **iOS App Sample** app running on the simulated IoT device, select **Start**. The application starts sending device-to-cloud messages, but also starts listening for cloud-to-device messages.
 
    ![View sample IoT device app](media/iot-hub-ios-swift-c2d/view-d2c.png)
 
diff --git a/articles/iot-hub/c2d-messaging-java.md b/articles/iot-hub/c2d-messaging-java.md
@@ -1,13 +1,13 @@
 ---
-title: Cloud-to-device messages with Azure IoT Hub (Java) | Microsoft Docs
-description: How to send cloud-to-device messages to a device from an Azure IoT hub using the Azure IoT SDKs for Java. You modify a simulated device app to receive cloud-to-device messages and modify a back-end app to send the cloud-to-device messages.
+title: Send cloud-to-device messages (Java)
+titleSuffix: Azure IoT Hub
+description: How to send cloud-to-device messages from a back-end app and receive them on a device app using the Azure IoT SDKs for Java.
 author: kgremban
 
 ms.author: kgremban
 ms.service: iot-hub
-services: iot-hub
 ms.devlang: java
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 06/28/2017
 ms.custom: [amqp, mqtt, devx-track-java]
 ---
@@ -84,12 +84,12 @@ In this section, modify your device app to receive cloud-to-device messages from
     mvn clean package -DskipTests
     ```
 
-The `execute` method in the `AppMessageCallback` class returns `IotHubMessageResult.COMPLETE`. This notifies IoT Hub that the message has been successfully processed and that the message can be safely removed from the device queue. The device should return this value when its processing successfully completes regardless of the protocol it's using.
+The `execute` method in the `AppMessageCallback` class returns `IotHubMessageResult.COMPLETE`. This status notifies IoT Hub that the message has been successfully processed and that the message can be safely removed from the device queue. The device should return this value when its processing successfully completes regardless of the protocol it's using.
 
 With AMQP and HTTPS, but not MQTT, the device can also:
 
 * Abandon a message, which results in IoT Hub retaining the message in the device queue for future consumption.
-* Reject a message, which which permanently removes the message from the device queue.
+* Reject a message, which permanently removes the message from the device queue.
 
 If something happens that prevents the device from completing, abandoning, or rejecting the message, IoT Hub will, after a fixed timeout period, queue the message for delivery again. For this reason, the message processing logic in the device app must be *idempotent*, so that receiving the same message multiple times produces the same result.
 
@@ -193,7 +193,7 @@ In this section, you create a Java console app that sends cloud-to-device messag
 
 ## Run the applications
 
-You are now ready to run the applications.
+You're now ready to run the applications.
 
 1. At a command prompt in the simulated-device folder, run the following command to begin sending telemetry to your IoT hub and to listen for cloud-to-device messages sent from your hub:
 
diff --git a/articles/iot-hub/c2d-messaging-node.md b/articles/iot-hub/c2d-messaging-node.md
@@ -1,13 +1,13 @@
 ---
-title: Cloud-to-device messages with Azure IoT Hub (Node) | Microsoft Docs
-description: How to send cloud-to-device messages to a device from an Azure IoT hub using the Azure IoT SDKs for Node.js. You modify a simulated device app to receive cloud-to-device messages and modify a back-end app to send the cloud-to-device messages.
+title: Send cloud-to-device messages (Node.js)
+titleSuffix: Azure IoT Hub
+description: How to send cloud-to-device messages from a back-end app and receive them on a device app using the Azure IoT SDKs for Node.js.
 author: kgremban
 
 ms.author: kgremban
 ms.service: iot-hub
-services: iot-hub
 ms.devlang: javascript
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 06/16/2017
 ms.custom: [amqp, mqtt, devx-track-js]
 ---
@@ -70,12 +70,12 @@ In this section, modify your device app to receive cloud-to-device messages from
     });
     ```
 
-In this example, the device invokes the **complete** function to notify IoT Hub that it has processed the message and that it can safely be removed from the device queue. The call to **complete** is not required if you are using MQTT transport and can be omitted. It is required for AMQP and HTTPS.
+In this example, the device invokes the **complete** function to notify IoT Hub that it has processed the message and that it can safely be removed from the device queue. The call to **complete** isn't required if you're using MQTT transport and can be omitted. It's required for AMQP and HTTPS.
 
 With AMQP and HTTPS, but not MQTT, the device can also:
 
 * Abandon a message, which results in IoT Hub retaining the message in the device queue for future consumption.
-* Reject a message, which which permanently removes the message from the device queue.
+* Reject a message, which permanently removes the message from the device queue.
 
 If something happens that prevents the device from completing, abandoning, or rejecting the message, IoT Hub will, after a fixed timeout period, queue the message for delivery again. For this reason, the message processing logic in the device app must be *idempotent*, so that receiving the same message multiple times produces the same result.
 
@@ -117,7 +117,7 @@ In this section, you create a Node.js console app that sends cloud-to-device mes
     var Message = require('azure-iot-common').Message;
     ```
 
-5. Add the following code to **SendCloudToDeviceMessage.js** file. Replace the "{iot hub connection string}" and "{device id}" placeholder values with the IoT hub connection string and device ID you noted previously:
+5. Add the following code to **SendCloudToDeviceMessage.js** file. Replace the "{iot hub connection string}" and "{device ID}" placeholder values with the IoT hub connection string and device ID you noted previously:
 
     ```javascript
     var connectionString = '{iot hub connection string}';
@@ -170,7 +170,7 @@ In this section, you create a Node.js console app that sends cloud-to-device mes
 
 ## Run the applications
 
-You are now ready to run the applications.
+You're now ready to run the applications.
 
 1. At the command prompt in the **simulated-device** folder, run the following command to send telemetry to IoT Hub and to listen for cloud-to-device messages:
 
diff --git a/articles/iot-hub/c2d-messaging-python.md b/articles/iot-hub/c2d-messaging-python.md
@@ -1,13 +1,14 @@
 ---
-title: Cloud-to-device messages with Azure IoT Hub (Python) | Microsoft Docs
-description: How to send cloud-to-device messages to a device from an Azure IoT hub using the Azure IoT SDKs for Python. You modify a simulated device app to receive cloud-to-device messages and modify a back-end app to send the cloud-to-device messages.
+title: Send cloud-to-device messages (Python)
+titleSuffix: Azure IoT Hub
+description: How to send cloud-to-device messages from a back-end app and receive them on a device app using the Azure IoT SDKs for Python.
 author: kgremban
+
+ms.author: kgremban
 ms.service: iot-hub
-services: iot-hub
 ms.devlang: python
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 01/02/2023
-ms.author: kgremban
 ms.custom: mqtt, devx-track-python, py-fresh-zinc
 ---
 
@@ -75,7 +76,7 @@ In this section, you create a Python console app to simulate a device and receiv
     CONNECTION_STRING = "{deviceConnectionString}"
     ```
 
-1. Define the following function that will be used to print received messages to the console:
+1. Define the following function that is used to print received messages to the console:
 
     ```python
     def message_handler(message):
diff --git a/articles/iot-hub/iot-hub-csharp-csharp-file-upload.md b/articles/iot-hub/iot-hub-csharp-csharp-file-upload.md
@@ -18,7 +18,7 @@ ms.custom: "mqtt, devx-track-csharp"
 
 This article demonstrates how to [file upload capabilities of IoT Hub](iot-hub-devguide-file-upload.md) upload a file to [Azure blob storage](../storage/index.yml), using an Azure IoT .NET device and service SDKs. 
 
-The [Send telemetry from a device to an IoT hub](../iot-develop/quickstart-send-telemetry-iot-hub.md?pivots=programming-language-csharp) quickstart and [Send cloud-to-device messages with IoT Hub](iot-hub-csharp-csharp-c2d.md) article show the basic device-to-cloud and cloud-to-device messaging functionality of IoT Hub. The [Configure Message Routing with IoT Hub](tutorial-routing.md) article shows a way to reliably store device-to-cloud messages in Microsoft Azure blob storage. However, in some scenarios, you can't easily map the data your devices send into the relatively small device-to-cloud messages that IoT Hub accepts. For example:
+The [Send telemetry from a device to an IoT hub](../iot-develop/quickstart-send-telemetry-iot-hub.md?pivots=programming-language-csharp) quickstart and [Send cloud-to-device messages with IoT Hub](c2d-messaging-dotnet.md) article show the basic device-to-cloud and cloud-to-device messaging functionality of IoT Hub. The [Configure Message Routing with IoT Hub](tutorial-routing.md) article shows a way to reliably store device-to-cloud messages in Microsoft Azure blob storage. However, in some scenarios, you can't easily map the data your devices send into the relatively small device-to-cloud messages that IoT Hub accepts. For example:
 
 * Videos
 * Large files that contain images
diff --git a/articles/iot-hub/iot-hub-dev-guide-sas.md b/articles/iot-hub/iot-hub-dev-guide-sas.md
@@ -409,5 +409,5 @@ Now that you have learned how to control access IoT Hub, you may be interested i
 If you would like to try out some of the concepts described in this article, see the following IoT Hub tutorials:
 
 * [Get started with Azure IoT Hub](../iot-develop/quickstart-send-telemetry-iot-hub.md?pivots=programming-language-nodejs)
-* [How to send cloud-to-device messages with IoT Hub](iot-hub-csharp-csharp-c2d.md)
+* [How to send cloud-to-device messages with IoT Hub](c2d-messaging-dotnet.md)
 * [How to process IoT Hub device-to-cloud messages](tutorial-routing.md)
diff --git a/articles/iot-hub/iot-hub-devguide-c2d-guidance.md b/articles/iot-hub/iot-hub-devguide-c2d-guidance.md
@@ -41,4 +41,4 @@ Learn how to use direct methods, desired properties, and cloud-to-device message
 
 * [Use direct methods](quickstart-control-device.md)
 * [Use desired properties to configure devices](tutorial-device-twins.md) 
-* [Send cloud-to-device messages](iot-hub-node-node-c2d.md)
+* [Send cloud-to-device messages](c2d-messaging-node.md)
diff --git a/articles/iot-hub/iot-hub-devguide-messages-c2d.md b/articles/iot-hub/iot-hub-devguide-messages-c2d.md
@@ -43,7 +43,7 @@ A thread could fail to process a message without notifying the IoT hub. In this
 
 The **max delivery count** property on the IoT hub determines the maximum number of times a message can transition between the *Enqueued* and *Invisible* states. After that number of transitions, the IoT hub sets the state of the message to *Dead lettered*. Similarly, the IoT hub sets the state of a message to *Dead lettered* after its expiration time. For more information, see [Message expiration (time to live)](#message-expiration-time-to-live).
 
-The [How to send cloud-to-device messages with IoT Hub](iot-hub-csharp-csharp-c2d.md) article shows you how to send cloud-to-device messages from the cloud and receive them on a device.
+The [How to send cloud-to-device messages with IoT Hub](c2d-messaging-dotnet.md) article shows you how to send cloud-to-device messages from the cloud and receive them on a device.
 
 A device ordinarily completes a cloud-to-device message when the loss of the message doesn't affect the application logic. An example of this completion might be when the device has persisted the message content locally or has successfully executed an operation. The message could also carry transient information, whose loss wouldn't impact the functionality of the application. Sometimes, for long-running tasks, you can:
 
@@ -167,4 +167,4 @@ You can set the configuration options in one of the following ways:
 
 For information about the SDKs that you can use to receive cloud-to-device messages, see [Azure IoT Hub SDKs](iot-hub-devguide-sdks.md).
 
-To try out receiving cloud-to-device messages, see the [Send cloud-to-device](iot-hub-csharp-csharp-c2d.md) tutorial.
+To try out receiving cloud-to-device messages, see the [Send cloud-to-device](c2d-messaging-dotnet.md) tutorial.
diff --git a/articles/iot-hub/iot-hub-java-java-file-upload.md b/articles/iot-hub/iot-hub-java-java-file-upload.md
@@ -18,7 +18,7 @@ ms.custom: [amqp, mqtt, devx-track-java]
 
 This article demonstrates how to [file upload capabilities of IoT Hub](iot-hub-devguide-file-upload.md) upload a file to [Azure blob storage](../storage/index.yml), using Java.
 
-The [Send telemetry from a device to an IoT hub](../iot-develop/quickstart-send-telemetry-iot-hub.md?pivots=programming-language-java) quickstart and [Send cloud-to-device messages with IoT Hub](iot-hub-java-java-c2d.md) articles show the basic device-to-cloud and cloud-to-device messaging functionality of IoT Hub. The [Configure message routing with IoT Hub](tutorial-routing.md) tutorial shows a way to reliably store device-to-cloud messages in Azure blob storage. However, in some scenarios, you can't easily map the data your devices send into the relatively small device-to-cloud messages that IoT Hub accepts. For example:
+The [Send telemetry from a device to an IoT hub](../iot-develop/quickstart-send-telemetry-iot-hub.md?pivots=programming-language-java) quickstart and [Send cloud-to-device messages with IoT Hub](c2d-messaging-java.md) articles show the basic device-to-cloud and cloud-to-device messaging functionality of IoT Hub. The [Configure message routing with IoT Hub](tutorial-routing.md) tutorial shows a way to reliably store device-to-cloud messages in Azure blob storage. However, in some scenarios, you can't easily map the data your devices send into the relatively small device-to-cloud messages that IoT Hub accepts. For example:
 
 * Videos
 * Large files that contain images
diff --git a/articles/iot-hub/iot-hub-node-node-file-upload.md b/articles/iot-hub/iot-hub-node-node-file-upload.md
diff --git a/articles/iot-hub/iot-hub-python-python-file-upload.md b/articles/iot-hub/iot-hub-python-python-file-upload.md
