Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit e4d28d7

Browse files
Update iot-cloud-tech-ref.md
1 parent 838d558 commit e4d28d7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎content/arduino-cloud/01.getting-started/02.technical-reference/iot-cloud-tech-ref.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -369,7 +369,7 @@ For a more complex and commented example, you can have a look at the [BlinkWitho
369369

370370
Components connected via I2C (including the sensors onboard the [MKR IoT Carrier](https://store.arduino.cc/products/arduino-mkr-iot-carrier)) uses the same bus as the **ECCX08** cryptochip. As the crypto chip is an essential part of establishing a connection to the IoT Cloud (it contains the credentials), it is important that other I2C peripherals are initialized after the connection has been made.
371371

372-
For example, if you are initalizing a library such as [Arduino_MKRENV](https://www.arduino.cc/reference/en/libraries/arduino_mkrenv), your `setup()` should be implemented as:
372+
For example, if you are initializing a library such as [Arduino_MKRENV](https://www.arduino.cc/reference/en/libraries/arduino_mkrenv), your `setup()` should be implemented as:
373373

374374
```arduino
375375
void setup() {

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /