fix: typos (Koenkk#3698)

Author: Rotzbua

docs/devices/0402946.md

@@ -27,7 +27,7 @@ pageClass: device-page
 
 
 ### Pairing
-If pairing failed, try the followings:
+If pairing failed, try the following:
 - Make sure door are in open state
 - Press and hold manual lock button and wait for 3 beeps
 - Keypad in front lights up

docs/devices/14153905L.md

@@ -41,7 +41,7 @@ The delay between on/off actions is critical. Quickly turning the device on/off
 10. Wait for 1 second
 11. On
 12. Wait for 1 second
-13. The device should now slowly glow brigher and dimmer and is now in pairing mode.
+13. The device should now slowly glow brighter and dimmer and is now in pairing mode.
 
 If you do not succeed, try slightly increasing the time between on/off actions, and leave it off for several seconds before attempting again.
 <!-- Notes END: Do not edit below this line -->

docs/devices/14158704L.md

@@ -41,7 +41,7 @@ The delay between on/off actions is critical. Quickly turning the device on/off
 10. Wait for 1 second
 11. On
 12. Wait for 1 second
-13. The device should now slowly glow brigher and dimmer and is now in pairing mode.
+13. The device should now slowly glow brighter and dimmer and is now in pairing mode.
 
 If you do not succeed, try slightly increasing the time between on/off actions, and leave it off for several seconds before attempting again.
 <!-- Notes END: Do not edit below this line -->

docs/devices/404036_45327_45317_45328.md

@@ -31,7 +31,7 @@ Model 45327 (with firmware version `MGU10501`), a GU10-spot, and model 45328 (wi
 
 ### Pairing
 New Bulbs are automatically in pairing mode. 
-Factory resetting a bulb can be accomplished by switching it on and off five times with an interval of 1 second. After sucessful factory reset you will see a color transition.
+Factory resetting a bulb can be accomplished by switching it on and off five times with an interval of 1 second. After a successful factory reset, you will see a color transition.
 <!-- Notes END: Do not edit below this line -->
 
 

docs/devices/404127.md

@@ -25,7 +25,7 @@ pageClass: device-page
 <!-- Notes BEGIN: You can edit here. Add "## Notes" headline if not already present. -->
 ## Notes
 manufacturer: https://www.mueller-licht.de/produktinformationen/artikel/404127
-techical specs: https://tool.mueller-licht.net/web/pdf/404127.pdf
+technical specs: https://tool.mueller-licht.net/web/pdf/404127.pdf
 manual: https://tool.mueller-licht.net/web/pim/404127+404128_tint-Strip-RGB_BDA_003.pdf
 <!-- Notes END: Do not edit below this line -->
 

docs/devices/4058075208384.md

@@ -28,7 +28,7 @@ pageClass: device-page
 ### Pairing
 Switch the lamp off and on again 5 times, starting with a switched on lamp:
 Lamp is ON (starting point) > switch OFF > wait 5s > switch ON (1.) > wait 5s > switch OFF > wait 5s > switch ON (2.) > switch OFF > wait 5s > switch ON (3.) > switch OFF > wait 5s > switch ON (4.) > switch OFF > wait 5s > switch ON (5.) > blinking light signals active pairing mode
-Use a clock to do the switching with the 5s rhythm as it has to be relativly accurat.
+Use a clock to do the switching with the 5s rhythm as it has to be relatively accurate.
 <!-- Notes END: Do not edit below this line -->
 
 

docs/devices/4058075208421.md

@@ -28,7 +28,7 @@ pageClass: device-page
 ### Pairing
 Switch the lamp off and on again 5 times, starting with a switched on lamp:
 Lamp is ON (starting point) > switch OFF > wait 5s > switch ON (1.) > wait 5s > switch OFF > wait 5s > switch ON (2.) > switch OFF > wait 5s > switch ON (3.) > switch OFF > wait 5s > switch ON (4.) > switch OFF > wait 5s > switch ON (5.) > blinking light signals active pairing mode
-Use a clock to do the switching with the 5s rhythm as it has to be relativly accurat.
+Use a clock to do the switching with the 5s rhythm as it has to be relatively accurate.
 
 ### Set default power on/off transition
 Various Osram/Sylvania LED support setting a default transition when turning a light on and off.

docs/devices/550D6001.md

@@ -37,7 +37,7 @@ pageClass: device-page
 Depending on the firmware version the device may support both 1-channel and 2-channel mode. In 1-channel mode both the upper and lower buttons
 works as the upper buttons. On some firmware versions (incl. those sold as Elko EKO07117) the device starts out in 1-channel mode and must be
 switched into 2-channel mode either by using the Elko / Wiser gateway or by holding down button 1 and 4 (upper left and lower right) for approx.
-10 seconds - the led will flash red and the become green once successfull.
+10 seconds - the led will flash red and the become green once successful.
 
 ### Battery
 The battery used is a standard CR2032. The battery can be replaced by pulling

docs/devices/552-721X1.md

@@ -26,7 +26,7 @@ pageClass: device-page
 ## Notes
 
 ### Pairing
-Remove the cover and press the little button 3x, the led will flash blue when in pairing mode. The device stays in this mode for 5 minutes or until it succesfully paired.
+Remove the cover and press the little button 3x, the led will flash blue when in pairing mode. The device stays in this mode for 5 minutes or until it successfully paired.
 
 ### Binding
 This device does not support binding to groups or devices.
@@ -41,7 +41,7 @@ This device does support decoupling from the build in relay, when the device is
 | white continues | normal operation, the load is on |
 | red flashing | connection to the zigbee network lost |
 | blue flashing | connecting to the zigbee network |
-| blue continues for 4 sec | connected succesfully to the zigbee network |
+| blue continues for 4 sec | connected successfully to the zigbee network |
 
 The LED can be disabled while the load is on by using a toothpick and holding the **PROG** button for 10 seconds.
 <!-- Notes END: Do not edit below this line -->

docs/devices/552-721X2.md

@@ -26,7 +26,7 @@ pageClass: device-page
 ## Notes
 
 ### Pairing
-Remove the cover and press the either of the little buttons 3x, the led will flash blue when in pairing mode. The device stays in this mode for 5 minutes or until it succesfully paired.
+Remove the cover and press the either of the little buttons 3x, the led will flash blue when in pairing mode. The device stays in this mode for 5 minutes or until it successfully paired.
 
 ### Binding
 This device does not support binding to groups or devices.

docs/devices/57004000.md

@@ -27,7 +27,7 @@ pageClass: device-page
 This device can be setup in different modes: control, switch, sensors/blinds and scenes.
 
 In switch mode, this device has a rather long internal debounce (waiting for 2x the switch flipped for 50% brightness, or
-3x for 100% brightness). This causes a noteable delay before sending a e1_toggle or e2_toggle.
+3x for 100% brightness). This causes a notable delay before sending a e1_toggle or e2_toggle.
 
 For a simple lights on/off scenario you can avoid this delay by putting the device into sensor mode, and call a lights
 toggle function on both e1_on / e1_off actions.

docs/devices/6735_6736_6737.md

@@ -82,7 +82,7 @@ The battery-operated wall switch might be sending duplicate `action` events. In
     - action:
 ```
 
-This introduces a tiny lag after each button press, but you can get rid of the duplicate events if they are occuring in your environment.
+This introduces a tiny lag after each button press, but you can get rid of the duplicate events if they are occurring in your environment.
 
 #### Battery-operated control panel is very hard to wake up for configuration
 

docs/devices/8719514440937_8719514440999.md

@@ -26,7 +26,7 @@ pageClass: device-page
 ## Notes
 
 ### Pairing
-The device can be set to pairing mode by removing the device's back cover. There is a small "setup" button next to the battery which must be pressed for a few seconds by using a paperclip or something similiar, which will bring the device into pairing mode. If this is a brand new device, hold button 1 for 3 sec to pair. If this does not work, holding down the top left (#1) button for approximately five seconds may put the device into pairing mode.
+The device can be set to pairing mode by removing the device's back cover. There is a small "setup" button next to the battery which must be pressed for a few seconds by using a paperclip or something similar, which will bring the device into pairing mode. If this is a brand new device, hold button 1 for 3 sec to pair. If this does not work, holding down the top left (#1) button for approximately five seconds may put the device into pairing mode.
 <!-- Notes END: Do not edit below this line -->
 
 

docs/devices/AC0251100NJ_AC0251600NJ_AC0251700NJ.md

@@ -35,7 +35,7 @@ If the Switch is connected hold Middle and Arrow Up Buttons for 3 Seconds to dis
 This is referenced in [this issue](https://github.com/Koenkk/zigbee2mqtt/issues/962). Problem occurs because of default bindings to group 0.
 
 Known workaround is to create an empty group in Z2M with different ID (example: 1111), bind all three buttons to this group and remove default bindings to group 0.  
-Read more on a simmilar issue and workarounds in [this issue](https://github.com/Koenkk/zigbee2mqtt/issues/12397) related to other device.
+Read more on a similar issue and workarounds in [this issue](https://github.com/Koenkk/zigbee2mqtt/issues/12397) related to other device.
 
 ### Actions
 #### Arrow up 

docs/devices/AU-A1ZBMPRO1ZX.md

@@ -28,7 +28,7 @@ pageClass: device-page
 ### Pairing
 
 The first time the downlight is powered on, it will be in pairing mode.  
-Once the downlight has successfully paired it will change from a warm white to a cool white color to indicate a succesfull pairing. 
+Once the downlight has successfully paired it will change from a warm white to a cool white color to indicate a successful pairing. 
 
 In order to put the downlight into pairing mode after the initial pairing, power cycle the downlight 6 times in quick succession.
 <!-- Notes END: Do not edit below this line -->

docs/devices/E1524_E1810.md

@@ -43,7 +43,7 @@ Make sure that automations that are triggered by the 'action' attribute of the r
 ### Binding
 The [binding](../guide/usage/binding.md) functionality of this remote varies per firmware version:
 - < 2.3.014: binding is not supported, OTA update your device to get binding functionality
-- 2.3.014 - 2.3.074: suppports binding to groups only. It can only be bound to 1 group at a time. By default this remote is bound to the default bind group which you first have to unbind it from. This can be done by sending to `zigbee2mqtt/bridge/request/device/unbind` payload `{"from": "DEVICE_FRIENDLY_NAME", "to": "default_bind_group"}`. Wake up the device right before sending the commands by pressing a button on it.
+- 2.3.014 - 2.3.074: supports binding to groups only. It can only be bound to 1 group at a time. By default this remote is bound to the default bind group which you first have to unbind it from. This can be done by sending to `zigbee2mqtt/bridge/request/device/unbind` payload `{"from": "DEVICE_FRIENDLY_NAME", "to": "default_bind_group"}`. Wake up the device right before sending the commands by pressing a button on it.
 - 2.3.075 - 2.3.080 : supports binding to devices only
 - 24.4.5: supports binding to device or groups
 

docs/devices/E1743.md

@@ -52,7 +52,7 @@ If your main ZigBee coordinator is a SONOFF Zigbee 3.0 USB Dongle Plus, you may
 
 ### Binding
 The [binding](../guide/usage/binding.md) functionality of this remote varies per firmware version:
-- below 2.3.075: suppports binding to groups only. It can only be bound to 1 group at a time. By default this remote is bound to the default bind group which you first have to unbind it from. This can be done by sending to `zigbee2mqtt/bridge/request/device/unbind` payload `{"from": "DEVICE_FRIENDLY_NAME", "to": "default_bind_group"}`. Wake up the device right before sending the commands by pressing a button on it.
+- below 2.3.075: supports binding to groups only. It can only be bound to 1 group at a time. By default this remote is bound to the default bind group which you first have to unbind it from. This can be done by sending to `zigbee2mqtt/bridge/request/device/unbind` payload `{"from": "DEVICE_FRIENDLY_NAME", "to": "default_bind_group"}`. Wake up the device right before sending the commands by pressing a button on it.
 - 2.3.075 and greater: supports binding to devices only
 
 ### Battery Replacement

docs/devices/E1766.md

@@ -50,7 +50,7 @@ If subsequently held down for > 0.5s, a `stop` action is triggered upon release.
 
 ### Binding
 The [binding](../guide/usage/binding.md) functionality of this remote varies per firmware version:
-- below 2.3.075: suppports binding to groups only. It can only be bound to 1 group at a time. By default this remote is bound to the default bind group which you first have to unbind it from. This can be done by sending to `zigbee2mqtt/bridge/request/device/unbind` payload `{"from": "DEVICE_FRIENDLY_NAME", "to": "default_bind_group"}`. Wake up the device right before sending the commands by pressing a button on it.
+- below 2.3.075: supports binding to groups only. It can only be bound to 1 group at a time. By default this remote is bound to the default bind group which you first have to unbind it from. This can be done by sending to `zigbee2mqtt/bridge/request/device/unbind` payload `{"from": "DEVICE_FRIENDLY_NAME", "to": "default_bind_group"}`. Wake up the device right before sending the commands by pressing a button on it.
 - 2.3.075 and greater: supports binding to devices only
 
 ### Starting OTA updates

docs/devices/E1812.md

@@ -36,7 +36,7 @@ To resolve the `Device didn't respond to OTA request` error, you can try to push
 
 ### Binding
 The [binding](../guide/usage/binding.md) functionality of this remote varies per firmware version:
-- below 2.3.75: suppports binding to groups only. It can only be bound to 1 group at a time. By default this remote is bound to the default bind group which you first have to unbind it from. This can be done by sending to `zigbee2mqtt/bridge/request/device/unbind` payload `{"from": "DEVICE_FRIENDLY_NAME", "to": "default_bind_group"}`. Wake up the device right before sending the commands by pressing a button on it.
+- below 2.3.75: supports binding to groups only. It can only be bound to 1 group at a time. By default this remote is bound to the default bind group which you first have to unbind it from. This can be done by sending to `zigbee2mqtt/bridge/request/device/unbind` payload `{"from": "DEVICE_FRIENDLY_NAME", "to": "default_bind_group"}`. Wake up the device right before sending the commands by pressing a button on it.
 - 2.3.075 and greater: supports binding to devices only
 
 ### Troubleshooting: no battery level

docs/devices/NLG-TW_light.md

@@ -36,7 +36,7 @@ I got the pairing right with this method once. However, it is extremley difficul
 
 1. Switch on the light for 5 to 10 seconds.
 2. Switch off the light.
-3. Switch on and off the light at least 4 times untill the light starts blinking several times. In this sequence assure to wait for 1-2 seconds between each new switch-on.
+3. Switch on and off the light at least 4 times until the light starts blinking several times. In this sequence assure to wait for 1-2 seconds between each new switch-on.
 <!-- Notes END: Do not edit below this line -->
 
 

docs/devices/PTM_215ZE.md

@@ -35,7 +35,7 @@ Not all Zigbee devices can do this translation, currently the only devices known
 Green Power devices don't support binding and are not included in network scans.
 
 ### Pairing
-Before starting a pairing attempt, please read carefully this section from the **[documentation ](https://www.zigbee2mqtt.io/advanced/zigbee/01_zigbee_network.html#green-power-devices)**
+Before starting a pairing attempt, please carefully read this section from the **[documentation ](https://www.zigbee2mqtt.io/advanced/zigbee/01_zigbee_network.html#green-power-devices)**
 
 The pairing may be done via NFC or the physical buttons. The use of NFC is highly recommended in order to ease the paring process and as the direct commisioning mode is disabled by default.
 
@@ -70,7 +70,7 @@ Then, press the selected button contact shortly (< 7s) to select radio channel 1
 
 Once the device is paired you need to confirm the channel. To do this, press any button other than the one used previously.
 
-For more informations, please refer to the [EnOcean PTM 215ZE manual chapter 3.6.2.1](https://www.enocean.com/wp-content/uploads/downloads-produkte/en/products/enocean_modules_24ghz/ptm-215ze/user-manual-pdf/PTM_215ZE_User_Manual-1.pdf).
+For more information's, please refer to the [EnOcean PTM 215ZE manual chapter 3.6.2.1](https://www.enocean.com/wp-content/uploads/downloads-produkte/en/products/enocean_modules_24ghz/ptm-215ze/user-manual-pdf/PTM_215ZE_User_Manual-1.pdf).
 <!-- Notes END: Do not edit below this line -->
 
 

docs/devices/TS0001_power.md

@@ -25,7 +25,7 @@ pageClass: device-page
 <!-- Notes BEGIN: You can edit here. Add "## Notes" headline if not already present. -->
 ### Re-Pairing
 - long press Button until the indicator light flashes 
-- if there is a physical switch conntected, you can turn on/off 5 times, then the indicator light will flash
+- if there is a physical switch connected, you can turn on/off 5 times, then the indicator light will flash
 <!-- Notes END: Do not edit below this line -->
 
 

docs/devices/V3-BTZB_V3-BTZBE.md

@@ -27,7 +27,7 @@ pageClass: device-page
 
 
 ### Pairing
-If pairing failed, try the followings:
+If pairing failed, try the following:
 - Pairing it closer to the coordinator
 - Connecting the CC2531 via an USB extension cable (to avoid interference)
 - Replacing the batteries of the danalock.

docs/devices/WB-MSW-ZIGBEE_v.4.md

@@ -29,10 +29,10 @@ pageClass: device-page
 Wiren Board WB-MSW v.4 — hybrid digital sensor of motion, temperature, humidity, illumination, noise, CO2 and VOC level. It is equipped with the IR blaster (and the receiver for learning). Designed for climate control in residential and office premises.
 
 ### Switch endpoints
-The device allways exposes 3 on/off endpoints named `l1`, `l2` and `l3`. Frist two of them only work if illuminannce + IR blaster addon is installed. Their finctuons as follows:
+The device always exposes 3 on/off endpoints named `l1`, `l2` and `l3`. The first two of them only work if illuminance + IR blaster addon is installed. Their functions as follows:
 - `l1` – controls blinking red led
 - `l2` – controls blinking green led
-- `l3` – controlls buzzer
+- `l3` – controls buzzer
 
 Warning, the installed buzzer is very loud.
 

docs/devices/WV704R0A0902.md

@@ -86,7 +86,7 @@ The last known twist-top boost state.
 
 ### keypad_lockout
 Keypad lock, i.e. enable/disable twist-top boost.
-* Setting the keypad to lock (i.e. `lock1`) disables the twist-top boost button which prevents booting and installation mode. The deivce can still be reset, but it appears the keypad remains locked after reset (?).
+* Setting the keypad to lock (i.e. `lock1`) disables the twist-top boost button which prevents booting and installation mode. The device can still be reset, but it appears the keypad remains locked after reset (?).
 * Value can be found in the published state on the `keypad_lockout` property.
 * Possible values are: `unlock`, `lock1`.
 * To write: 
@@ -96,10 +96,10 @@ Keypad lock, i.e. enable/disable twist-top boost.
   - publish a message to `zigbee2mqtt/FRIENDLY_NAME/get` with payload `{"keypad_lockout": ""}`.
 
 ### ADC
-Unknown - appears to be device parameter values as a comma-seperated list.
+Unknown - appears to be device parameter values as a comma-separated list.
 
 ### ALG
-Unknown - appears to be device parameter values as a comma-seperated list.
+Unknown - appears to be device parameter values as a comma-separated list.
 <!-- Notes END: Do not edit below this line -->
 
 

docs/devices/WXKG15LM.md

@@ -32,7 +32,7 @@ Factory reset the switch by pressing and holding left and right rocker for 10 se
 If you have issues changing the click_mode with Zigbee2MQTT you can switch between click mode physically. This is done by clicking either of the two rockers quickly five times. The click mode will then toggle between fast mode and multi mode.
 
 ### Binding
-Please note, that currently you will only get one endpoint for binding even though there are two rockers (see https://github.com/Koenkk/zigbee-herdsman-converters/blob/eed5fde987891f996c428339569dbff1893e62a1/devices/xiaomi.js#L2370). You will always receive the `toggle_1` event no matter whick rocker you use.
+Please note, that currently you will only get one endpoint for binding even though there are two rockers (see https://github.com/Koenkk/zigbee-herdsman-converters/blob/eed5fde987891f996c428339569dbff1893e62a1/devices/xiaomi.js#L2370). You will always receive the `toggle_1` event no matter which rocker you use.
 <!-- Notes END: Do not edit below this line -->