You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-central/preview/tutorial-define-edge-device-type.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ This tutorial shows you, as a builder, how to use a device template to define a
20
20
For an overview, see [What is Azure IoT Central (preview features)?](overview-iot-central.md).
21
21
22
22
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.
24
24
* The **IoT Edge runtime** runs on each IoT Edge device, and manages the modules deployed to each device.
25
25
* A **cloud-based interface** enables you to remotely monitor and manage IoT Edge devices. IoT Central is the cloud interface.
26
26
@@ -102,7 +102,7 @@ At a high level, a deployment manifest is a list of module twins that are config
102
102
103
103
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).
104
104
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.
106
106
107
107
```JSON
108
108
{
@@ -376,7 +376,7 @@ To publish a device template:
376
376
377
377

378
378
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.
380
380
381
381

0 commit comments