Skip to content

Commit c3496e9

Browse files
committed
Review
1 parent 8de8816 commit c3496e9

5 files changed

+16
-16
lines changed

articles/iot-edge/includes/iot-edge-prerequisites-device-requirements-linux.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
ms.topic: include
3-
ms.date: 01/05/2023
4-
author: micahl
5-
ms.author: micahl
3+
ms.date: 06/10/2024
4+
author: PatAltimore
5+
ms.author: patricka
66
ms.service: iot-edge
77
ms.custom: linux-related-content
88
services: iot-edge

articles/iot-edge/includes/iot-edge-prerequisites-register-device.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
ms.topic: include
3-
ms.date: 01/05/2023
3+
ms.date: 06/10/2024
44
author: PatAltimore
55
ms.author: patricka
66
ms.service: iot-edge

articles/iot-edge/includes/iot-edge-register-device-symmetric.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
ms.topic: include
3-
ms.date: 1/31/2023
3+
ms.date: 06/10/2024
44
author: PatAltimore
55
ms.author: patricka
66
ms.service: iot-edge
@@ -43,7 +43,7 @@ Once Azure IoT Edge and Azure IoT Hub extensions are installed, you notice an Az
4343
Registering a new device is akin to creating an IoT Edge device in the Azure portal. This virtual device is one of the *twins*, whereas the real world device is the other twin. Visual Studio Code can set this up for you through the following steps.
4444

4545
1. In the Visual Studio Code Explorer menu, expand the **Azure IoT Hub** section.
46-
1. Click on the **...** in the **Azure IoT Hub** section header. If you don't see the ellipsis, click on or hover over the header.
46+
1. Select on the **...** in the **Azure IoT Hub** section header. If you don't see the ellipsis, select or hover over the header.
4747
1. Select **Create IoT Edge Device**.
4848
1. In the text box that opens, give your device an ID, for example `my-edge-device-1` (all lowercase), then press enter.
4949

@@ -85,7 +85,7 @@ The edge-enabled devices that connect to your IoT hub are listed on the **Device
8585
When you're ready to set up your device, you need the connection string that links your physical device with its identity in the IoT hub. Devices that authenticate with symmetric keys have their connection strings available to copy in the portal. To find your connection string in the portal:
8686

8787
1. From the **Devices** page, select the IoT Edge device ID from the list.
88-
2. Copy the value of either **Primary Connection String** or **Secondary Connection String**. Either key will work.
88+
2. Copy the value of either **Primary Connection String** or **Secondary Connection String**. Either key works.
8989

9090
# [Visual Studio Code](#tab/visual-studio-code)
9191

@@ -108,7 +108,7 @@ To see all devices in your IoT hub, use the [az iot hub device-identity list](/c
108108
az iot hub device-identity list --hub-name hub_name_here
109109
```
110110

111-
Any device that is registered as an IoT Edge device will have the property **capabilities.iotEdge** set to **true**. You see a lot of other metadata as JSON output as well, including your device IDs.
111+
Any device that is registered as an IoT Edge device has the property **capabilities.iotEdge** set to **true**. You see a lot of other metadata as JSON output as well, including your device IDs.
112112

113113
When you're ready to set up your device, you need its connection string that links your physical device with its identity in the IoT hub. Use the following [az iot hub device-identity connection-string show](/cli/azure/iot/hub/device-identity/connection-string) command to return the connection string for a single device. Replace `[device_id]` and `[hub_name]` with your own values. The value for the `device-identity` parameter is case-sensitive.
114114

articles/iot-edge/tutorial-deploy-function.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: 'Tutorial: Deploy Azure Functions as modules - Azure IoT Edge'
2+
title: Deploy Azure Functions as modules - Azure IoT Edge
33
description: In this tutorial, you develop an Azure Function as an IoT Edge module, then deploy it to an edge device.
44
author: PatAltimore
55

66
ms.author: patricka
7-
ms.date: 3/22/2023
7+
ms.date: 06/10/2024
88
ms.topic: tutorial
99
ms.service: iot-edge
1010
services: iot-edge
@@ -49,7 +49,7 @@ To develop an IoT Edge module with Azure Functions, install additional prerequis
4949

5050
## Create a function project
5151

52-
The Azure IoT Edge for Visual Studio Code that you installed in the prerequisites provides management capabilities as well as some code templates. In this section, you use Visual Studio Code to create an IoT Edge solution that contains an Azure Function.
52+
The Azure IoT Edge for Visual Studio Code that you installed in the prerequisites provides management capabilities and some code templates. In this section, you use Visual Studio Code to create an IoT Edge solution that contains an Azure Function.
5353

5454
### Create a new project
5555

@@ -84,7 +84,7 @@ The IoT Edge extension in Visual Studio Code tries to pull your container regist
8484
8585
### Set target architecture to AMD64
8686

87-
Running Azure Functions modules on IoT Edge is supported only on Linux AMD64 based containers. The default target architecture for Visual Studio Code is Linux AMD64, but we will set it explicitly to Linux AMD64 here.
87+
Running Azure Functions modules on IoT Edge is supported only on Linux AMD64 based containers. The default target architecture for Visual Studio Code is Linux AMD64, but we set it explicitly to Linux AMD64 here.
8888

8989
1. Open the command palette and search for **Azure IoT Edge: Set Default Target Platform for Edge Solution**.
9090

@@ -210,7 +210,7 @@ You can use the Azure portal to deploy your Function module to an IoT Edge devic
210210

211211
3. Browse to the solution folder that contains the **CSharpFunction**. Open the config folder, select the **deployment.amd64.json** file, and then choose **Select Edge Deployment Manifest**.
212212

213-
4. Under your device, expand **Modules** to see a list of deployed and running modules. Click the refresh button. You should see the new **CSharpFunction** running along with the **SimulatedTemperatureSensor** module and the **$edgeAgent** and **$edgeHub**.
213+
4. Under your device, expand **Modules** to see a list of deployed and running modules. Select the refresh button. You should see the new **CSharpFunction** running along with the **SimulatedTemperatureSensor** module and the **$edgeAgent** and **$edgeHub**.
214214

215215
It may take a few moments for the new modules to show up. Your IoT Edge device has to retrieve its new deployment information from IoT Hub, start the new containers, and then report the status back to IoT Hub.
216216

articles/iot-edge/tutorial-nested-iot-edge.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Tutorial - Create a hierarchy of Azure IoT Edge devices
3-
description: This tutorial shows you how to create a hierarchical structure of IoT Edge devices with secure communication. This IoT Edge configuration is also known as nested edge.
2+
title: Create a hierarchy of Azure IoT Edge devices
3+
description: This tutorial shows you how to create a hierarchical structure of IoT Edge devices with secure communication. The configuration is also known as nested edge.
44
author: PatAltimore
55

66
ms.author: patricka
7-
ms.date: 05/10/2023
7+
ms.date: 06/10/2024
88
ms.topic: tutorial
99
ms.service: iot-edge
1010
ms.custom: devx-track-azurecli

0 commit comments

Comments
 (0)