diff --git a/content/datasheets/development/lopy.md b/content/datasheets/development/lopy.md
index bb4fc14..7010cb8 100644
--- a/content/datasheets/development/lopy.md
+++ b/content/datasheets/development/lopy.md
@@ -18,8 +18,7 @@ aliases:
 
 ## Datasheet
 
-The datasheet of the LoPy is available as a [PDF File]
-(/gitbook/assets/specsheets/Pycom_002_Specsheets_LoPy_v2.pdf)
+The datasheet of the LoPy is available as a [PDF File](/gitbook/assets/specsheets/Pycom_002_Specsheets_LoPy_v2.pdf)
 
 
 The Lopy is certified for [CE RED](/gitbook/assets/16-213298_expertise_pycom_lopy-1.0r.pdf) and [FCC ACC](/gitbook/assets/2090acc16_grant.pdf") [FCC BCC](/gitbook/assets/2090bcc16_grant.pdf) [FCC CCC](/gitbook/assets/2090ccc16_grant.pdf) 
diff --git a/content/updatefirmware/device.md b/content/updatefirmware/device.md
index c6f6347..04f45b1 100644
--- a/content/updatefirmware/device.md
+++ b/content/updatefirmware/device.md
@@ -23,14 +23,24 @@ The basic firmware upgrade procedure can be found below, please follow these ste
 
 After you're done with upgrading, you can use the Pymakr Plugins to upload and run programs in your device.
 
-1. Before connecting your module to a Pysense / Pytrack board, you should update the firmware on the Pysense/Pytrack board. Instructions on how to do this can be found [here](/updatefirmware/expansionboard/).
+1. Before connecting your module to a Pysense / Pytrack board, you should check for updates of the firmware on the Pysense/Pytrack board. Instructions on how to do this can be found [here](/updatefirmware/expansionboard/).
 2. Disconnect your device from your computer
-3. Insert module into Expansion Board
+3. Insert the module into Expansion Board
     * On Expansionboard 2.0, connect a jumper cable or wire between `G23` and `GND`
 4. Reconnect the board via USB to your computer
 5. Run the Firmware Upgrade tool and click through the menus
 
-![](/gitbook/assets/firmware-update-2.png)
+    ![](/gitbook/assets/firmware_update-0.png)
+    > Checking 'Include Development Releases' will check for the development releases of the Firmware Updater Tool
+
+
+    ![](/gitbook/assets/firmware_update-1.png)
+    > Checking 'Show Advanced Settings' will give you the option screen in the next figure.
+
+    ![](/gitbook/assets/firmware_update-2.png)
+
+    > In some cases, erasing the NVS and CONFIG partitions can solve issues relating to WiFi, Timers or other variables stored in the NVS / CONFIG. Erase during update will remove all Python code on the device.
+
 
 6. The firmware version of your device is now upgraded to the latest version.
     * On Expansionboard 2.0, remove the jumper cable.
@@ -39,7 +49,7 @@ After you're done with upgrading, you can use the Pymakr Plugins to upload and r
 
 ## Common issues:
 
-* If you are having any issues, make sure the **TX and RX jumpers** are present on your Expansion Board, as the jumpers sometimes come loose in the box during transport. Without these jumpers, the updater will fail.
+* If you are having any issues uploading firmware to your device, make sure the **TX and RX jumpers** are present on your Expansion Board, as the jumpers sometimes come loose in the box during transport. Without these jumpers, the updater will fail.
 * On MacOS, the firmware upgrade tool needs access to the `/tmp` folder
 * On MacOS, there is an issue with signing of the firmware tool. Go to system preferences --> Security & Privacy --> General, and click "Allow" for the Pycom Firmware Updater tool.
 
diff --git a/static/gitbook/assets/firmware-update-2.png b/static/gitbook/assets/firmware-update-2.png
deleted file mode 100644
index 214c855..0000000
Binary files a/static/gitbook/assets/firmware-update-2.png and /dev/null differ
diff --git a/static/gitbook/assets/firmware-update.png b/static/gitbook/assets/firmware-update.png
deleted file mode 100644
index e04b57e..0000000
Binary files a/static/gitbook/assets/firmware-update.png and /dev/null differ
diff --git a/static/gitbook/assets/firmware_update-0.png b/static/gitbook/assets/firmware_update-0.png
new file mode 100644
index 0000000..29127a1
Binary files /dev/null and b/static/gitbook/assets/firmware_update-0.png differ
diff --git a/static/gitbook/assets/firmware_update-1.png b/static/gitbook/assets/firmware_update-1.png
new file mode 100644
index 0000000..34bc961
Binary files /dev/null and b/static/gitbook/assets/firmware_update-1.png differ
diff --git a/static/gitbook/assets/firmware_update-2.png b/static/gitbook/assets/firmware_update-2.png
new file mode 100644
index 0000000..f87e6a4
Binary files /dev/null and b/static/gitbook/assets/firmware_update-2.png differ