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/core/concepts-get-connected.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -140,11 +140,11 @@ The flow is slightly different depending on whether the devices use SAS tokens o
140
140
141
141
### Connect devices that use X.509 certificates without registering
142
142
143
-
1. [Add and verify a root or intermediate X.509 certificate](#connect-devices-using-x509-certificates) to your IoT Central application.(#connect-devices-using-x509-certificates)
143
+
1. [Add and verify a root or intermediate X.509 certificate](#connect-devices-using-x509-certificates) to your IoT Central application.
144
144
145
145
1. Generate the leaf-certificates for your devices using the root or intermediate certificate you added to your IoT Central application. Use lower-case device IDs as the `CNAME` in the leaf certificates.
146
146
147
-
1. The OEM flashes each device with a device ID, a generated left X.509 certificate, and the application **ID scope** value.
147
+
1. The OEM flashes each device with a device ID, a generated leaf X.509 certificate, and the application **ID scope** value.
148
148
149
149
1. When you switch on a device, it first connects to DPS to retrieve its IoT Central registration information.
0 commit comments