Updated Upgrading (markdown)

Upgrading.md

@@ -89,13 +89,13 @@ You can set up OTA url and initiate OTA upgrade from TDM using GUI.
 [**OTA over SCP**](OTA-over-SCP) - setup and configure "OTA over SCP" upload for PlatformIO
 
 # Device Settings
-Tasmota uses flash memory to store options and settings. New versions add (or remove) features that use various regions of flash memory. If you did not erase flash when you originally flashed your device, an updated verion of Tasmota may be accessing areas with values left over from the old Tasmota or even the original factory firmware. This might cause unexpected and unwanted behavior or even major problems (contant reboots or reconnect). It is best to address this before upgrading across major versions of Tasmota.
+Tasmota uses flash memory to store options and settings. New versions add (or remove) features that use various regions of flash memory. If you did not erase flash when you originally flashed your device, an updated version of Tasmota may be accessing areas with values left over from the old Tasmota or even the original factory firmware. This might cause unexpected and unwanted behavior or even major problems (constant reboots or reconnect). It is best to address this before upgrading across major versions of Tasmota.
 
 **decode-config.py does not work in Windows**
 1. Make a configuration backup using one of these two methods:
    - Use `decode-config.py` from the Tasmota [`/tools/` folder](../tree/development/tools) to convert a .dmp backup to a readable form (JSON file):  
      `decode-config.py -d <deviceIP> --backup-file Config-@f --backup-type json`
-     > @f will be replaced by that devices FriendlyName
+     > @f will be replaced by that device's FriendlyName
    - If you have a `.dmp` backup already, you can create a JSON extract from that file:  
      `decode-config.py -f <dmpFile> --backup-file Config-@f --backup-type json`
 2. Perform a `Reset 6` (erases flash settings area but retains Wi-Fi and MQTT settings)