Typo fixes (Koenkk#1620)

* Fixed a tiny typo: erease -> erase

* Fixed a typo: wether -> whether

(cherry picked from commit cd8e2ef)

Author: OrBin

docs/guide/adapters/flashing/flashing_via_cc2538-bsl.md

@@ -38,7 +38,7 @@ unzip CC1352P2_CC2652P_launchpad_coordinator_20220219.zip
 
 sudo python3 cc2538-bsl.py -ewv -p /dev/ttyUSB0 --bootloader-sonoff-usb ./CC1352P2_CC2652P_launchpad_coordinator_20220219.hex
 ```
-`-ewv` means Mass **e**rease, **w**rite, **v**erify  
+`-ewv` means Mass **e**rase, **w**rite, **v**erify  
 `-p` is the port on which your device is running, in this case `/dev/ttyUSB0`  
 `--bootloader-sonoff-usb` means that the bootloader is activated by the script, by toggeling RTS and DTR in the correct pattern for Sonoff USB dongle (remove this if your device is not a Sonoff dongle).
 

docs/guide/faq/README.md

@@ -36,7 +36,7 @@ This problem can be divided in 2 categories; no logging is shown at all OR inter
 Want to migrate from e.g. a CC2531 to a more powerful adapter (e.g. ZZH)? Then follow these instructions:
 1. First make sure you are running the latest version of Zigbee2MQTT
 1. Stop Zigbee2MQTT
-1. Determine wether migrating [requires re-pairing of your devices](#what-does-and-does-not-require-repairing-of-all-devices)
+1. Determine whether migrating [requires re-pairing of your devices](#what-does-and-does-not-require-repairing-of-all-devices)
     - If re-pairing is required: remove `data/coordinator_backup.json` (if it exists) and `data/database.db`
     - If re-pairing is **not** required: [copy the ieee address of the old adpter into the new one](../adapters/flashing/copy_ieeaddr.html)
 1. Update the `serial` -> `port`  in your `configuration.yaml`

docs/guide/usage/mqtt_topics_and_messages.md

@@ -96,7 +96,7 @@ Example payload:
     "permit_join_timeout": 10, // Time in seconds till permit join is disabled, `undefined` in case of no timeout
     "config": {...}, // Will contain the complete Zigbee2MQTT config expect the network_key
     "config_schema": {...}, // Will contain the JSON schema of the config
-    "restart_required": false // Indicates wether Zigbee2MQTT needs to be restarted to apply options set through zigbee2mqtt/request/bridge/options
+    "restart_required": false // Indicates whether Zigbee2MQTT needs to be restarted to apply options set through zigbee2mqtt/request/bridge/options
 }
 ```
 
@@ -268,7 +268,7 @@ To allow joining for only a specific amount of time add the `time` property (in
 
 #### zigbee2mqtt/bridge/request/health_check
 
-Allows to check wether Zigbee2MQTT is healthy. Payload has to be empty, example response: `{"data":{"healthy":true},"status":"ok"}`.
+Allows to check whether Zigbee2MQTT is healthy. Payload has to be empty, example response: `{"data":{"healthy":true},"status":"ok"}`.
 
 #### zigbee2mqtt/bridge/request/restart
 

docs/guide/usage/ota_updates.md

@@ -17,7 +17,7 @@ Not all manufacturers make their updates available, below is a (not-complete) li
 Gira does unfortunately not seem to offer firmware updates for their wall transmitter 2430-100 (which is very similar to the Jung ZLLxx5004M) and the update file for the Jung wall transmitter does not work for Gira (probably because the Gira wall transmitter only has 6 buttons instead of 8 on the Jung).
 - Sengled devices
 
-To check wether your specific device supports OTA updates via Zigbee2MQTT, go to the supported devices page, click on your device and look for the *OTA updates* section.
+To check whether your specific device supports OTA updates via Zigbee2MQTT, go to the supported devices page, click on your device and look for the *OTA updates* section.
 
 ## Automatic checking for available updates
 Your zigbee devices can request a firmware update check. Zigbee2MQTT obliges this, and will automatically check if updates are available for your devices.