Skip to content

Commit 991c248

Browse files
committed
Add feedback
1 parent 41a9f43 commit 991c248

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

articles/iot-edge/how-to-create-transparent-gateway.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ Now, you need to copy the certificates to the Azure IoT Edge for Linux on Window
155155
Copy-EflowVMFile -fromFile <path>\certs\azure-iot-test-only.root.ca.cert.pem -toFile /home/iotedge-user/certs/certs/azure-iot-test-only.root.ca.cert.pem -pushFile
156156
```
157157

158-
1. Invoke the following commands on the EFLOW VM to grant iotedge permissions to the certificate files since `Copy-EflowVMFile` copies files with root only access permissions.
158+
1. Invoke the following commands on the EFLOW VM to grant *iotedge* permissions to the certificate files since `Copy-EflowVMFile` copies files with root only access permissions.
159159

160160
```powershell
161161
Invoke-EflowVmCommand "sudo chown -R iotedge /home/iotedge-user/certs/"

articles/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-tpm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ Simulated TPM samples:
140140
Provision-EflowVM -provisioningType "DpsTpm" -scopeId "SCOPE_ID_HERE"
141141
```
142142

143-
If you have enrolled the device using a custom **Registration Id**, you must specify that Registration Id as well when provisioning:
143+
If you have enrolled the device using a custom **Registration Id**, you must specify that registration ID as well when provisioning:
144144

145145
```powershell
146146
Provision-EflowVM -provisioningType "DpsTpm" -scopeId "SCOPE_ID_HERE" -registrationId "REGISTRATION_ID_HERE"
@@ -174,7 +174,7 @@ Simulated TPM samples:
174174
Provision-EflowVM -provisioningType "DpsTpm" -scopeId "SCOPE_ID_HERE"
175175
```
176176

177-
If you have enrolled the device using a custom **Registration Id**, you must specify that Registration Id as well when provisioning:
177+
If you have enrolled the device using a custom **Registration Id**, you must specify that registration ID as well when provisioning:
178178

179179
```powershell
180180
Provision-EflowVM -provisioningType "DpsTpm" -scopeId "SCOPE_ID_HERE" -registrationId "REGISTRATION_ID_HERE"

articles/iot-edge/how-to-update-iot-edge.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ For information about IoT Edge for Linux on Windows updates, see [EFLOW Updates]
135135
:::moniker range=">=iotedge-2020-11"
136136

137137
>[!NOTE]
138-
>Currently, there is not support for IoT Edge version 1.4 running on Windows devices.
138+
>Currently, there is no support for IoT Edge version 1.4 running on Windows devices.
139139
>
140140
>To view the steps for updating IoT Edge for Linux on Windows, see [IoT Edge 1.1](?view=iotedge-2018-06&preserve-view=true&tabs=windows).
141141

0 commit comments

Comments
 (0)