Skip to content

Commit 2f10daa

Browse files
authored
Update README.md
1 parent b914e36 commit 2f10daa

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -84,9 +84,9 @@ git clone https://github.com/Leverege/microchip-avr-iot.git && cd microchip-avr-
8484

8585
<a href="https://console.cloud.google.com/iot/registries" target="_blank">OPEN IOT CORE REGISTRY MANAGEMENT</a>
8686

87-
3. Click on your device's ID in the list.
87+
3. Click on your device's UID in the list.
8888

89-
Because registry entries must begin with a letter **your device ID will be prefixed with a 'd'**. To search for your device by id, you must enter 'd<your_device_id>' in the search box.
89+
Because registry entries must begin with a letter **your device UID will be prefixed with a 'd'**. To search for your device by uid, you must enter 'd<your_device_id>' in the search box.
9090

9191
4. Click the **Add public key** button.
9292

@@ -102,4 +102,4 @@ git clone https://github.com/Leverege/microchip-avr-iot.git && cd microchip-avr-
102102

103103
## View your live data!
104104

105-
And that's it! If you've edited your device with the Microchip editor, you should see live data flowing to your new Firebase app at \<your-project-id\>.firebaseapp.com/device/\<your-device-id\>.
105+
And that's it! If you've edited your device with the Microchip editor, you should see live data flowing to your new Firebase app at \<your-project-id\>.firebaseapp.com/device/\<your-device-uid\>.

0 commit comments

Comments
 (0)