Skip to content

Commit 60c037f

Browse files
authored
Update tutorial-define-edge-device-type.md
1 parent 14d6e55 commit 60c037f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/iot-central/preview/tutorial-define-edge-device-type.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This tutorial shows you, as a builder, how to use a device template to define a
2020
For an overview, see [What is Azure IoT Central (preview features)?](overview-iot-central.md).
2121

2222
IoT Edge is made up of three components:
23-
* **IoT Edge modules** are containers that run Azure services, third-party services, or your own code. Modules are deployed to IoT Edge devices, and run locally on those devices.
23+
* **IoT Edge modules** are containers that run Azure services, partner services, or your own code. Modules are deployed to IoT Edge devices, and run locally on those devices.
2424
* The **IoT Edge runtime** runs on each IoT Edge device, and manages the modules deployed to each device.
2525
* A **cloud-based interface** enables you to remotely monitor and manage IoT Edge devices. IoT Central is the cloud interface.
2626

@@ -102,7 +102,7 @@ At a high level, a deployment manifest is a list of module twins that are config
102102

103103
Use Visual Studio Code to create a deployment manifest. To learn more, see [Azure IoT Edge for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-edge).
104104

105-
Here's a basic deployment manifest, with one module as an example to be used for this tutorial. Copy the following JSON, and save it as .json file.
105+
Here's a basic deployment manifest, with one module as an example to be used for this tutorial. Copy the following JSON, and save it as a .json file.
106106

107107
```JSON
108108
{
@@ -376,7 +376,7 @@ To publish a device template:
376376

377377
![Screenshot of Publish a Device Template dialog box, with Publish highlighted](./media/tutorial-define-edge-device-type/edgepublishtemplate.png)
378378

379-
After a device template is published, it's visible on the **Devices** page and to the operator. In a published device template, you can't edit a device capability model without creating a new version. However, you can make updates to cloud properties, customizations, and views, in a published device template. These updates don't cause a new version to be created. After making any changes, select **Publish** to push those changes out to your operator.
379+
After a device template is published, it's visible on the **Devices** page and to the operator. In a published device template, you can't edit a device capability model without creating a new version. However, you can make updates to cloud properties, customizations, and views, in a published device template. These updates don't cause a new version to be created. After you make any changes, select **Publish** to push those changes out to your operator.
380380

381381
![Screenshot of Device templates list of published templates](./media/tutorial-define-edge-device-type/publishedtemplate.png)
382382

0 commit comments

Comments
 (0)