MPAE-19439 fixed path to image, version 1.0.1

Author: Glen-Nilsen

.main-meta/main.json

@@ -4,7 +4,7 @@
     "content": {
         "metaDataVersion": "1.3.0",
         "name": "com.microchip.mcu8.mplabx.project.avr128db48-i2c-io-expander2-leds-and-buttons-polled-printf",
-        "version": "1.0.0",
+        "version": "1.0.1",
         "displayName": "avr128db48-i2c-io-expander2-leds-and-buttons-polled-printf",
         "projectName": "avr128db48-i2c-io-expander2-leds-and-buttons-polled-printf",
         "shortDescription": "I/O Expander 1 pins (8 LEDs) set as outputs, low (LEDs on). I/O Expander 2 pins (SW1-3, 5 joystick inputs) as digital inputs. Button/joystick turns LED off. Curiosity Nano SW resets LEDs on.",

README.md

@@ -15,7 +15,7 @@ The [I<sup>2</sup>C Host IO Expander 2 - LEDs and Buttons Example](https://onlin
 ), of the [MCC Melody I<sup>2</sup>C Example Component (for the Curiosity Nano Explorer)](https://onlinedocs.microchip.com/v2/keyword-lookup?keyword=I2C.HOST.EXAMPLE.COMPONENT&version=latest&redirect=true "MCC Melody I<sup>2</sup>C Example Component for the Curiosity Nano Explorer"
 ), is used here in the Polled implementation with the Printf visualization. 
 
-![alt text](images\avr128db48-i2c-io-expander2-leds-and-buttons-polled-printf_intro.png)
+![alt text](images/avr128db48-i2c-io-expander2-leds-and-buttons-polled-printf_intro.png)
 
 On the Curiosity Nano Explorer, the pins on the I<sup>2</sup>C I/O Expander 1 are connected to active-low LEDs, while the pins on the I<sup>2</sup>C I/O Expander 2 are connected to buttons (SW1, SW2 and SW3) as well as the joystick inputs (left, right, up, down, press).
 
@@ -24,8 +24,8 @@ This example configures the I/O Expander 1 pins as outputs set LOW, so the activ
 ## Operation
 When running the application using the [MPLAB® Data Visualizer](https://www.microchip.com/en-us/tools-resources/debug/mplab-data-visualizer "MPLAB® Data Visualizer"), you should see something similar to the following: 
 
-When running the application, using the MPLAB Data Visualizer, you should see something similar to the following: 
 ![alt text](images/avr128db48-i2c-io-expander2-leds-and-buttons-polled-printf.png)
+
 **Note:** Behaviour is not as reliable as in the Callbacks version. 
 
 **Note:** Debug I/O is not actively used. However, since the SW pin on the Curiosity Nano is a Debug I/O pin, so when pushing the IO_Reset, a toggle is picked up on the Debug I/O pin.