Skip to content

Commit 0210f65

Browse files
committed
made PR reviewer edits
1 parent 5e4daea commit 0210f65

File tree

4 files changed

+20
-5
lines changed

4 files changed

+20
-5
lines changed

.openpublishing.redirection.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3386,6 +3386,21 @@
33863386
"redirect_url": "/azure/iot-edge/how-to-manage-device-certificates",
33873387
"redirect_document_id": true
33883388
},
3389+
{
3390+
"source_path": "articles/iot-edge/how-to-deploy-monitor.md",
3391+
"redirect_url": "/azure/iot-edge/how-to-deploy-at-scale",
3392+
"redirect_document_id": true
3393+
},
3394+
{
3395+
"source_path": "articles/iot-edge/how-to-deploy-monitor-cli.md",
3396+
"redirect_url": "/azure/iot-edge/how-to-deploy-cli-at-scale",
3397+
"redirect_document_id": true
3398+
},
3399+
{
3400+
"source_path": "articles/iot-edge/how-to-deploy-monitor-vscode.md",
3401+
"redirect_url": "/azure/iot-edge/how-to-deploy-vscode-at-scale",
3402+
"redirect_document_id": true
3403+
},
33893404
{
33903405
"source_path": "articles/cognitive-services/cognitive-services-recommendations-quick-start.md",
33913406
"redirect_url": "/azure/cognitive-services/recommendations/overview",

articles/iot-edge/how-to-auto-provision-simulated-device-linux.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -202,7 +202,7 @@ Know your DPS **ID Scope** and device **Registration ID** before beginning the a
202202

203203
In order for the IoT Edge runtime to automatically provision your device, it needs access to the TPM.
204204

205-
You can give TPM access to the IoT Edge runtime by overriding the systemd settings so that the **iotedge** service has root privileges. If you don't want to elevate the service privileges, you can also use the following steps to manually provide TPM access.
205+
You can give TPM access to the IoT Edge runtime by overriding the systemd settings so that the `iotedge` service has root privileges. If you don't want to elevate the service privileges, you can also use the following steps to manually provide TPM access.
206206

207207
1. Find the file path to the TPM hardware module on your device and save it as a local variable.
208208

articles/iot-edge/how-to-deploy-at-scale.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ To add a module from the Azure Marketplace, follow these steps:
9393

9494
1. In the **IoT Edge Modules** section of the page, click **Add**.
9595
1. Select **Marketplace Module** from the drop-down menu.
96-
1. Choose a module from the **IoT Edge Module Marketplace** page. The module you select is automatically configured for your subscription, resource group, and device. It then appears in your list of IoT Edge modules. Some modules may require additional configuration. For more information, see [Deploy modules from Azure marketplace](how-to-deploy-modules-portal.md#deploy-modules-from-azure-marketplace).
96+
1. Choose a module from the **IoT Edge Module Marketplace** page. The module you select is automatically configured for your subscription, resource group, and device. It then appears in your list of IoT Edge modules. Some modules may require additional configuration. For more information, see [Deploy modules from Azure Marketplace](how-to-deploy-modules-portal.md#deploy-modules-from-azure-marketplace).
9797

9898
#### Add a Stream Analytics module
9999

articles/iot-edge/how-to-deploy-vscode-at-scale.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -209,15 +209,15 @@ After you have configured the deployment manifest and configured tags in the dev
209209

210210
1. Navigate to the deployment manifest JSON file that you want to use, and click **Select Edge Deployment Manifest**.
211211

212-
1. Provide values as prompted, starting with the **deployment id**.
212+
1. Provide values as prompted, starting with the **deployment ID**.
213213

214-
![Specify a deployment id](./media/how-to-deploy-monitor-vscode/create-deployment-at-scale.png)
214+
![Specify a deployment ID](./media/how-to-deploy-monitor-vscode/create-deployment-at-scale.png)
215215

216216
Specify values for these parameters:
217217

218218
| Parameter | Description |
219219
| --- | --- |
220-
| Deployment id | The name of the deployment that will be created in the IoT hub. Give your deployment a unique name that is up to 128 lowercase letters. Avoid spaces and the following invalid characters: `& ^ [ ] { } \ | " < > /`. |
220+
| Deployment ID | The name of the deployment that will be created in the IoT hub. Give your deployment a unique name that is up to 128 lowercase letters. Avoid spaces and the following invalid characters: `& ^ [ ] { } \ | " < > /`. |
221221
| Target condition | Enter a target condition to determine which devices will be targeted with this deployment. The condition is based on device twin tags or device twin reported properties and should match the expression format. For example, `tags.environment='test' and properties.reported.devicemodel='4000x'`|
222222
| Priority | A positive integer. If two or more deployments are targeted at the same device, the deployment with the highest numerical value for Priority will apply. |
223223

0 commit comments

Comments
 (0)