Merge branch 'main' into martab1994-patch-2

Author: sebromero

.vscode/launch.json

@@ -14,6 +14,17 @@
             "program": "validate.js",
             "args": ["-p", "../../content"],
             "cwd": "${workspaceFolder}/scripts/validation/"
+        },
+        {
+            "type": "pwa-node",
+            "request": "launch",
+            "name": "Debug Quickfix",
+            "skipFiles": [
+                "<node_internals>/**"
+            ],
+            "program": "fix-issues.js",
+            "args": ["-p", "../../content"],
+            "cwd": "${workspaceFolder}/scripts/validation/"
         }
     ]
 }

content/cloud/iot-cloud/tutorials/01.iot-cloud-getting-started/iot-cloud-getting-started.md

@@ -84,6 +84,8 @@ Connection through mobile networks can be considered in remote areas where there
 
 ***For more information, visit the [Arduino SIM page](https://store.arduino.cc/digital/sim).***
 
+***Note that a secured connection is a memory intense operation, so there's not a lot of memory for the user application (e.g. around 2.6 kB on the MKR GSM 1400). Using a lot of IoT Cloud variables may cause the sketch to run out of memory on boards which don't offload the SSL stack and make it crash.***
+
 ### ESP32 / ESP8266
 
 The Arduino IoT Cloud supports a wide range of third party boards based on the ESP32 and ESP8266 microcontrollers with support for Wi-Fi. To set them up, simply choose the **third party option** in the device setup.

content/hardware/01.mkr/01.boards/mkr-1000-wifi/tutorials/AnalogToMidi/AnalogToMidi.md

@@ -56,13 +56,13 @@ Defines the correspondence between notes and MIDI note values. Part of MIDIUSB
 
 ### Functions In Sketch
 
-*searchForNote(float frequency)*
+**searchForNote(float frequency)**
 Search for the nearest frequency that is in the vector of frequencies noteFrequency[ ]
 
-*noteOn(byte channel, byte pitch, byte velocity)*
+**noteOn(byte channel, byte pitch, byte velocity)**
 Sends out to MIDI the event to turn on the note of the specified pitch on the specified MIDI Channel
 
-*void noteOff(byte channel, byte pitch, byte velocity)*
+**void noteOff(byte channel, byte pitch, byte velocity)**
 Sends out to MIDI the event to turn off  the note of the specified pitch on the specified MIDI Channel
 
 ## Code

content/hardware/01.mkr/01.boards/mkr-1000-wifi/tutorials/WiFi101OTA/WiFi101OTA.md

@@ -202,4 +202,4 @@ void printWifiStatus() {
 
 
 
-*Last revision 2017/03/24 by AG*
+**Last revision 2017/03/24 by AG**

content/hardware/01.mkr/01.boards/mkr-1000-wifi/tutorials/wifi-101-library-examples/wifi-101-library-examples.md

@@ -156,7 +156,7 @@ void loop() {
 
 The 19.6.1 firmware is only available for model B of the WINC1500, this is used in the MKR1000 board. Unfortunately, the WiFi101 shield uses model A, which Atmel has stopped supporting, so there is no 19.6.1 firmware release for it, 19.4.4 will be the latest firmware version that is compatible.
 
-To simplify the process, we have prepared a specific sketch - this *FirmwareUpdater* - that you must load on the host board (either the one with the shield plugged in, or the MKR1000 itself) and an easy to use plug-in available in Arduino Software (IDE) 1.6.10 onwards.
+To simplify the process, we have prepared a specific sketch - this **FirmwareUpdater** - that you must load on the host board (either the one with the shield plugged in, or the MKR1000 itself) and an easy to use plug-in available in Arduino Software (IDE) 1.6.10 onwards.
 
 The `FirmwareUpdater.ino` sketch is available in **Examples > WiFi101**
 
@@ -180,7 +180,7 @@ To update the firmware you should choose the right typer of board. You can find
 
 ![Find the model.](assets/MKR1000_RevA_B_20copy.png)
 
-Choose in the dropdown list the model corresponding to your unit and proceed clicking on the *Update Firmware button*. A bar at the bottom will show you the progress of the procedure that includes erasing, writing and verifying of the firmware. At the end you get a clear notice of the successful operation.
+Choose in the dropdown list the model corresponding to your unit and proceed clicking on the **Update Firmware button**. A bar at the bottom will show you the progress of the procedure that includes erasing, writing and verifying of the firmware. At the end you get a clear notice of the successful operation.
 
 ![Firmware has been updated.](assets/firmware_uploaded_101.png)
 
@@ -189,7 +189,7 @@ Choose in the dropdown list the model corresponding to your unit and proceed cli
 With the same procedure, you may load root certificates on the WiFi module to access securely specific websites. Your board must be running the **FirmwareUpdater** sketch to work .The root certificates are issued by a limited number of certification authorities, but it is difficult to know which site is using which authority. To ease your life, we allow you to specify directly the URL to which you need to connect securely, leaving to us the task to download the root certificate.
 The list you are building is not saved from one session to the next one. It might happen that a few websites share the same root certificate. You don't have to worry about this as we take care of it. The space available on your WiFi module to store the certificates is limited to around 10 certificates that, being issued by a limited number of authorities, should be more than enough for the average projects.
 
-The procedure starts connecting your board (either the one with the shield plugged in, or the MKR1000 itself) to your computer and selecting it from the Tools menu of the Arduino Software (IDE). Load the FirmwareUpdater on the board and launch the *WiFi 101 Firmware Updater* from Tools and go to the third section of the interface.
+The procedure starts connecting your board (either the one with the shield plugged in, or the MKR1000 itself) to your computer and selecting it from the Tools menu of the Arduino Software (IDE). Load the FirmwareUpdater on the board and launch the **WiFi 101 Firmware Updater** from Tools and go to the third section of the interface.
 
 ![Adding SSL root certificates.](assets/certificates_upload_101.png)
 

content/hardware/01.mkr/01.boards/mkr-nb-1500/tutorials/securely-connecting-an-arduino-nb-1500-to-azure-iot-hub/securely-connecting-an-arduino-nb-1500-to-azure-iot-hub.md

@@ -155,7 +155,7 @@ In the Azure IoT Hub portal, click the device id row in the IoT Devices table fo
 
 ![Click "Message to device"](assets/screen_shot_2019-02-06_at_12_06_14_pm_554ggffxiP.png)
 
-You can now enter a message body to send to the device, in the screenshot below "*Hello there :)*" was entered. Click the "Send Message" button in the toolbar to send the message.
+You can now enter a message body to send to the device, in the screenshot below "**Hello there :)**" was entered. Click the "Send Message" button in the toolbar to send the message.
 
 ![Send your message!](assets/screen_shot_2019-02-06_at_12_07_18_pm_jZHRAyebN2.png)
 

content/hardware/01.mkr/01.boards/mkr-vidor-4000/tutorials/VidorDrawLogo/VidorDrawLogo.md

@@ -126,4 +126,4 @@ void loop()
 ```
 
 
-*Last revision 2018/07/22 by SM*
+**Last revision 2018/07/22 by SM**

content/hardware/01.mkr/01.boards/mkr-vidor-4000/tutorials/VidorEnableCam/VidorEnableCam.md

@@ -107,4 +107,4 @@ void loop()
 ```
 
 
-*Last revision 2018/07/22 by SM*
+**Last revision 2018/07/22 by SM**

content/hardware/01.mkr/01.boards/mkr-vidor-4000/tutorials/VidorEncoder/VidorEncoder.md

@@ -155,4 +155,4 @@ void loop() {
 ```
 
 
-*Last revision 2018/07/22 by SM*
+**Last revision 2018/07/22 by SM**

content/hardware/01.mkr/01.boards/mkr-vidor-4000/tutorials/VidorQrRecognition/VidorQrRecognition.md

@@ -29,7 +29,7 @@ Include the VidorCamera library, which is part of VidorGraphics.
 `#include "VidorGraphics.h"`
 `#include "VidorCamera.h"`
 
-You have a number of functions available to manage the recognition of a QR Code. VidorQR is part of the VidorCam library; the functions are accessible with *cam.qrrec*.
+You have a number of functions available to manage the recognition of a QR Code. VidorQR is part of the VidorCam library; the functions are accessible with **cam.qrrec**.
 
 - `void begin()` - start recognition algorithm
 
@@ -150,4 +150,4 @@ void loop()  {
 }
 ```
 
-*Last revision 2018/07/22 by SM*
+**Last revision 2018/07/22 by SM**

content/hardware/01.mkr/01.boards/mkr-wifi-1010/tech-specs.yml

@@ -21,7 +21,7 @@ Communication:
   SPI: Yes
 Power:
   I/O Voltage: 3.3V
-  Input Voltage (nominal): 5-17V
+  Input Voltage (nominal): 5-7V
   DC Current per I/O pin: 7 mA
   Supported battery: Li-Po Single Cell, 3.7V, 1024mAh Minimum
   Battery connector: JST

content/hardware/01.mkr/01.boards/mkr-wifi-1010/tutorials/atmel-ice/using-an-atmel-ice-with-the-ide-v2.md

@@ -99,9 +99,9 @@ If the SWD interfaces of the debugger and the board are connected properly, a **
 
 ## Using the Debugger Tool
 
-Now that we have our hardware set up, we can learn how to use the IDE 2.0 Debugger Tool main functionalities through the [_Debugging with the Arduino IDE 2.0 tutorial_](https://docs.arduino.cc/software/ide-v2/tutorials/ide-v2-debugger). This tutorial goes through some key features of the Debugger Tool, and includes pointers to get started. 
+Now that we have our hardware set up, we can learn how to use the IDE 2.0 Debugger Tool main functionalities through the [**Debugging with the Arduino IDE 2.0 tutorial**](https://docs.arduino.cc/software/ide-v2/tutorials/ide-v2-debugger). This tutorial goes through some key features of the Debugger Tool, and includes pointers to get started. 
 
-As explained in the [_Debugging with the Arduino IDE 2.0 tutorial_](https://docs.arduino.cc/software/ide-v2/tutorials/ide-v2-debugger), before we can use the Debugger Tool of the Arduino IDE 2.0, we need to upload a sketch to our MKR WiFi 1010 board, making sure it is optimized for debugging. Let's try a simple program that blinks the onboard LED of our MKR WiFi 1010 board and changes the value of several variables while running. 
+As explained in the [**Debugging with the Arduino IDE 2.0 tutorial**](https://docs.arduino.cc/software/ide-v2/tutorials/ide-v2-debugger), before we can use the Debugger Tool of the Arduino IDE 2.0, we need to upload a sketch to our MKR WiFi 1010 board, making sure it is optimized for debugging. Let's try a simple program that blinks the onboard LED of our MKR WiFi 1010 board and changes the value of several variables while running. 
 
 ### 1. Setting Up
 

content/hardware/01.mkr/01.boards/mkr-wifi-1010/tutorials/securely-connecting-an-arduino-mkr-wifi-1010-to-aws-iot-core/securely-connecting-an-arduino-mkr-wifi-1010-to-aws-iot-core.md

@@ -24,7 +24,7 @@ source: "https://create.arduino.cc/projecthub/Arduino_Genuino/securely-connectin
 
 [AWS IoT Core](https://aws.amazon.com/iot-core/) is a managed cloud service that lets connected devices easily and securely interact with cloud applications and other devices. AWS IoT Core can support billions of devices and trillions of messages, and can process and route those messages to AWS endpoints and to other devices reliably and securely. 
 
-Devices can connect to AWS IoT Core using the following protocols: HTTP, WebSockets and MQTT. This tutorial will walk you through how to connect an [Arduino MKR WiFi 1010](https://store.arduino.cc/usa/arduino-mkr-wifi-1010) (or MKR1000) board securely to AWS IoT Core using the MQTT protocol. [MQTT](http://mqtt.org/) (*Message Queuing Telemetry Transport*) is an extremely lightweight M2M (machine-to-machine) connectivity protocol which provides a messaging subscription and publish transport.
+Devices can connect to AWS IoT Core using the following protocols: HTTP, WebSockets and MQTT. This tutorial will walk you through how to connect an [Arduino MKR WiFi 1010](https://store.arduino.cc/usa/arduino-mkr-wifi-1010) (or MKR1000) board securely to AWS IoT Core using the MQTT protocol. [MQTT](http://mqtt.org/) (**Message Queuing Telemetry Transport**) is an extremely lightweight M2M (machine-to-machine) connectivity protocol which provides a messaging subscription and publish transport.
 
 When connecting to AWS IoT Core using MQTT, devices are required to use X.509 certificates with TLS for authentication, as AWS IoT Core does not support authentication via username and password like many other MQTT broker services provide support for. More information on X.509 certificate support on AWS IoT can be found [here](https://docs.aws.amazon.com/iot/latest/developerguide/x509-certs.html).
 
@@ -114,7 +114,7 @@ Now that we have a CSR to identify the board, we need to login into the AWS cons
 
 ![Create a policy.](assets/screen_shot_2019-01-14_at_3_25_34_pm_C67jg7LTXy.png)
 
-13) Click "Create a policy." We'll be creating a very open policy for testing, **later on we suggest you create a stricter policy**. We'll call this policy "AllowEverything," fill in "iot:*" for the Action and "*" for the Resource ARN, then check the "Allow" box, then click "Create."
+13) Click "Create a policy." We'll be creating a very open policy for testing, **later on we suggest you create a stricter policy***. We'll call this policy "AllowEverything," fill in "iot:\*" for the Action and "\*" for the Resource ARN, then check the "Allow" box, then click "Create."
 
 ![Click create.](assets/screen_shot_2019-01-14_at_3_26_58_pm_bkfMovt51e.png)
 
@@ -175,7 +175,7 @@ Now that your board has successfully connected to AWS IoT, we can use the AWS co
 
 Every five seconds the board sends a hello message with the current millis() value.
 
-Now let's send a message to the board. In the Publish section, change the topic to **arduino/incoming** and click the "Publish to topic" button*.*
+Now let's send a message to the board. In the Publish section, change the topic to **arduino/incoming** and click the "Publish to topic" button.
 
 ![Click Publish to topic.](assets/screen_shot_2019-01-14_at_5_53_47_pm_LKDzWUW8VV.png)
 

content/hardware/01.mkr/03.carriers/mkr-iot-carrier/tutorials/mkr-iot-carrier-01-technical-reference/mkr-iot-carrier-01-technical-reference.md

@@ -106,7 +106,7 @@ The `carrier.begin();` command is essential to initializing the carrier and must
 
 ![The HTS221 Humidity Sensor on the MKR IoT Carrier](assets/mkrIotCarrier-sensor-temp&humi.png)
 
-The **HTS221 Humidity Sensor** is mounted on the top side of the carrier under the display, marked with a drop icon. The sensor uses capacitive sensing with a **humidity sensing range** of _0-100%_ and **accuracy** of _± 3.5% rH (20 to +80% rH)_, and a **temperature sensing range** of _-40 to 120° C_, with an **accuracy** of _± 0.5 °C,15 to +40 °C_. The sensor uses a low power consumption (2μA at 1 Hz sampling rate) and connects to the mounted Arduino MKR board through a I2C interface.
+The **HTS221 Humidity Sensor** is mounted on the top side of the carrier under the display, marked with a drop icon. The sensor uses capacitive sensing with a **humidity sensing range** of **0-100%** and **accuracy** of **± 3.5% rH (20 to +80% rH)**, and a **temperature sensing range** of **-40 to 120° C**, with an **accuracy** of **± 0.5 °C,15 to +40 °C**. The sensor uses a low power consumption (2μA at 1 Hz sampling rate) and connects to the mounted Arduino MKR board through a I2C interface.
 
 ### Code
 
@@ -135,7 +135,7 @@ Returns relative humidity (rH) in percentage.
 
 ![The LPS22HBTR Pressure Sensor on the MKR IoT Carrier](assets/mkrIotCarrier-sensor-pressure.png)
 
-The **LPS22HBTR Pressure Sensor** is mounted on the top side of the carrier under the display, marked with a meter icon. The sensor measures **absolute pressure range** of _260 to 1260 hPa (0.25 to 1.24 atm)_ and connects to the mounted Arduino MKR board through a I2C interface.
+The **LPS22HBTR Pressure Sensor** is mounted on the top side of the carrier under the display, marked with a meter icon. The sensor measures **absolute pressure range** of **260 to 1260 hPa (0.25 to 1.24 atm)** and connects to the mounted Arduino MKR board through a I2C interface.
 
 ### Code
 

content/hardware/02.hero/boards/uno-wifi-rev2/tutorials/uno-wifi-rev-2/uno-wifi-r2-chromebook-installation/uno-wifi-r2-chromebook-installation.md

@@ -33,7 +33,7 @@ The goals of this project are:
 
 ## Hardware & Software Needed
 
-- [Arduino IDE](https://www.arduino.cc/en/software).
+- [Arduino IDE 2](https://www.arduino.cc/en/software#future-version-of-the-arduino-ide).
 - [Arduino Web Editor](https://create.arduino.cc/).
 - [Arduino Create for Education](https://chrome.google.com/webstore/detail/arduino-create-for-educat/elmgohdonjdampbcgefphnlchgocpaij) (Chrome Web Store)
 - [Arduino UNO WiFi Rev 2](https://store.arduino.cc/arduino-uno-wifi-rev2).
@@ -44,18 +44,18 @@ The goals of this project are:
 
 Since Chromebooks cannot run executables, the firmware upgrade for the UNO WiFi Rev 2 needs to be done through a Windows/Mac/Linux computer. 
 
-**1.** Make sure you have installed [Arduino IDE 1.8.X](https://www.arduino.cc/en/software).
+**1.** Make sure you have installed [Arduino IDE 2](https://www.arduino.cc/en/software#future-version-of-the-arduino-ide).
 
 **2.** Download the [optiboot_atmega4.hex](/resources/firmware/optiboot_atmega4809.hex) file, and move it to your **Desktop folder**. 
 
 ![.hex file in your Desktop folder.](assets/hex-file-desktop.png)
 
-**3.** Open your Command Prompt (Windows) or Terminal (Mac/Linux), copy paste the command for your OS from the snippets below.
+**3.** Connect your UNO WiFi Rev2 board to your computer and open your Command Prompt (Windows) or Terminal (Mac/Linux), copy paste the command for your OS from the snippets below.
 
 ### Mac
 
 ```
-/Applications/Arduino.app/Contents/Java/hardware/tools/avr/bin/avrdude -C /Applications/Arduino.app/Contents/Java/hardware/tools/avr/etc/avrdude.conf -v -patmega4809 -cxplainedmini_updi -Pusb -b115200 -e -D -Ufuse2:w:0x01:m -Ufuse5:w:0xC9:m -Ufuse8:w:0x02:m -Uflash:w:/Users/$(whoami)/Desktop/optiboot_atmega4809.hex:i
+/Users/$(whoami)/Library/Arduino15/packages/arduino/tools/avrdude/6.3.0-arduino17/bin/avrdude -C/Users/$(whoami)/Library/Arduino15/packages/arduino/tools/avrdude/6.3.0-arduino17/etc/avrdude.conf -v -patmega4809 -cxplainedmini_updi -Pusb -b115200 -e -D -Ufuse2:w:0x01:m -Ufuse5:w:0xC9:m -Ufuse8:w:0x02:m -Uflash:w:/Users/$(whoami)/Desktop/optiboot_atmega4809.hex:i
 ```
 
 ### Windows
@@ -153,4 +153,4 @@ If things are not working as expected:
 
 ## Conclusion
 
-In this tutorial, we learned how to upload sketches to the UNO WiFi Rev 2 board, using the Web Editor on a Chromebook. For more tutorials on the UNO WiFi Rev 2 board, visit the [official documentation](/hardware/uno-wifi-rev2).
+In this tutorial, we learned how to upload sketches to the UNO WiFi Rev 2 board, using the Web Editor on a Chromebook. For more tutorials on the UNO WiFi Rev 2 board, visit the [official documentation](/hardware/uno-wifi-rev2).

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

@@ -128,7 +128,7 @@ void process(YunClient client) {
 }
 ```
 
-Create a function to deal with *digital* commands. Accept the client as the argument. Create some local variables to hold the pin and value of the command.
+Create a function to deal with **digital** commands. Accept the client as the argument. Create some local variables to hold the pin and value of the command.
 
 ```arduino
 void digitalCommand(YunClient client) {
@@ -162,7 +162,7 @@ Print the value to the client and update the datastore key with the current pin
 
 By wrapping the value to the client in `F()`, you'll be printing form the flash memory. This helps conserve space in SRAM, which is useful when dealing with long strings like URLs.
 
-The key will be the pin, and type. For example *D2* will be saved for for digital pin 2. The value will be whatever value the pin is currently set to, or was read from the pin.
+The key will be the pin, and type. For example **D2** will be saved for for digital pin 2. The value will be whatever value the pin is currently set to, or was read from the pin.
 
 ```arduino
 client.print(F("Pin D"));

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

@@ -236,4 +236,4 @@ void loop() {
 }
 ```
 
-*Last revision 2016/05/25 by SM*
+**Last revision 2016/05/25 by SM**

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

@@ -187,4 +187,4 @@ void loop() {
 }
 ```
 
-*Last revision 2016/05/25 by SM*
+**Last revision 2016/05/25 by SM**

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

@@ -190,4 +190,4 @@ void loop() {
 ```
 
 
-*Last revision 2016/05/25 by SM*
+**Last revision 2016/05/25 by SM**

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

@@ -252,4 +252,4 @@ void runScript() {
 }
 ```
 
-*Last revision 2016/05/25 by SM*
+**Last revision 2016/05/25 by SM**

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

@@ -80,4 +80,4 @@ The complete sketch is below :
 
 <iframe src='https://create.arduino.cc/example/library/bridge_1_7_0/bridge_1_7_0%5Cexamples%5CHttpClient/HttpClient/preview?embed' style='height:510px;width:100%;margin:10px 0' frameborder='0'></iframe>
 
-*Last revision 2016/05/25 by SM*
+**Last revision 2016/05/25 by SM**

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

@@ -159,4 +159,4 @@ void loop() {
 ```
 
 
-*Last revision 2016/05/25 by SM*
+**Last revision 2016/05/25 by SM**