Fixing spelling issues

content/arduino-cloud/01.guides/07.node-red/nodered-intro.md

@@ -100,7 +100,7 @@ You can run the simple flow shown below using Node-RED's default nodes:
 - drag the **"debug"** node into the workspace
 - connect the two nodes by dragging a wire from the message node to the debug node
 - click on the debug menu from the sidebar on the right
-- press **Depoly** from the header on the top
+- press **Deploy** from the header on the top
 - finally, press on the checkbox of the message node
 
 ![Creating a simple flow](assets/nodered-02.gif)

content/hardware/02.hero/boards/yun-rev2/tutorials/yun-first-config/content.md

@@ -559,7 +559,7 @@ void wifiConfig(String yunName, String yunPsw, String wifissid, String wifipsw,
 
   p.runShellCommand("uci set network.lan.proto='dhcp'");
 
-  p.runShellCommand("echo -e \"" + yunPsw + "\n" + yunPsw + "\" | passwd root"); //change the passwors
+  p.runShellCommand("echo -e \"" + yunPsw + "\n" + yunPsw + "\" | passwd root"); //change the password
 
   p.runShellCommand("uci commit"); //save the mods done via UCI
 

content/hardware/04.pro/carriers/portenta-hat-carrier/tutorials/user-manual/content.md

@@ -709,7 +709,7 @@ void setup() {
   Serial.println("Mass Storage Device connected.");
 
   /*
-   *  MOUNTIN SDCARD AS FATFS filesystem
+   *  MOUNTING SDCARD AS FATFS filesystem
    */
 
   Serial.println("Mounting Mass Storage Device...");

content/hardware/04.pro/carriers/portenta-max-carrier/tutorials/user-manual/content.md

@@ -938,7 +938,7 @@ void setup() {
   Serial.println("Mass Storage Device connected.");
 
   /* 
-   *  MOUNTIN SDCARD AS FATFS filesystem
+   *  MOUNTING SDCARD AS FATFS filesystem
    */
 
   Serial.println("Mounting Mass Storage Device...");

content/hardware/04.pro/carriers/portenta-mid-carrier/tutorials/user-manual/content.md

@@ -1690,7 +1690,7 @@ void setup() {
   Serial.println("Mass Storage Device connected.");
 
   /*
-   *  MOUNTIN SDCARD AS FATFS filesystem
+   *  MOUNTING SDCARD AS FATFS filesystem
    */
 
   Serial.println("Mounting Mass Storage Device...");

content/hardware/06.nicla/boards/nicla-sense-me/tutorials/connecting-to-iot-cloud/content.md

@@ -129,7 +129,7 @@ Inside `void setup()` initialize the `Serial` communication, set up the variable
     // Connect to Arduino Cloud
     ArduinoCloud.begin(ArduinoIoTPreferredConnection);
 
-    // Wait to be connected before intitalize the communication with the Nicla Sense ME
+    // Wait to be connected before initialize the communication with the Nicla Sense ME
     Serial.println("Connecting to the Arduino Cloud");
     while (ArduinoCloud.connected() != 1) {
       ArduinoCloud.update();

content/tutorials/generic/secrets-of-arduino-pwm/secrets-of-arduino-pwm.md

@@ -248,9 +248,9 @@ The Arduino uses Timer 0 internally for the millis() and delay() functions, so b
 
 The `analogWrite(pin, duty_cycle)` function sets the appropriate pin to PWM and sets the appropriate output compare register to duty_cycle (with the special case for duty cycle of 0 on Timer 0). The `digitalWrite()` function turns off PWM output if called on a timer pin. The relevant code is wiring_analog.c and wiring_digital.c.
 
-If you use `analogWrite(5, 0)` you get a duty cycle of 0%, even though pin 5's timer (Timer 0) is using fast PWM. How can this be, when a fast PWM value of 0 yields a duty cycle of 1/256 as explained above? The answer is that `analogWrite` "cheats"; it has special-case code to explicitly turn off the pin when called on Timer 0 with a duty cycle of 0. As a consequency, the duty cycle of 1/256 is unavailable when you use `analogWrite`` on Timer0, and there is a jump in the actual duty cycle between values of 0 and 1.
+If you use `analogWrite(5, 0)` you get a duty cycle of 0%, even though pin 5's timer (Timer 0) is using fast PWM. How can this be, when a fast PWM value of 0 yields a duty cycle of 1/256 as explained above? The answer is that `analogWrite` "cheats"; it has special-case code to explicitly turn off the pin when called on Timer 0 with a duty cycle of 0. As a consequence, the duty cycle of 1/256 is unavailable when you use `analogWrite`` on Timer0, and there is a jump in the actual duty cycle between values of 0 and 1.
 
-Some other Arduino models use dfferent AVR processors with similar timers. The Arduino Mega uses the ATmega1280 (datasheet), which has four 16-bit timers with 3 outputs each and two 8-bit timers with 2 outputs each. Only 14 of the PWM outputs are supported by the Arduino Wiring library, however. Some older Arduino models use the ATmega8 (datasheet), which has three timers but only 3 PWM outputs: Timer 0 has no PWM, Timer 1 is 16 bits and has two PWM outputs, and Timer 2 is 8 bits and has one PWM output.
+Some other Arduino models use different AVR processors with similar timers. The Arduino Mega uses the ATmega1280 (datasheet), which has four 16-bit timers with 3 outputs each and two 8-bit timers with 2 outputs each. Only 14 of the PWM outputs are supported by the Arduino Wiring library, however. Some older Arduino models use the ATmega8 (datasheet), which has three timers but only 3 PWM outputs: Timer 0 has no PWM, Timer 1 is 16 bits and has two PWM outputs, and Timer 2 is 8 bits and has one PWM output.
 
 ### Troubleshoot
 

scripts/resources/spell-check-ignore-list.txt

@@ -14,4 +14,6 @@ ro
 som
 ser
 Manuel
-technic
+technic
+shiftin
+forsee