typo...

docs/DeepSleep.md

@@ -71,13 +71,13 @@ The following triggers can be used to execute commands upon wake-up or right bef
 - `Power1#Boot` : is the earliest trigger. But valid only if you have a `Relay` output defined.
 - `Switch1#Boot` : is the next trigger, also occur very early in the boot process. But valid only if you have `Switch` input defined.
 - `System#Boot` : is occuring later in the Tasmota boot process but is always available.
-- `SYstem#Save` : is occuring right before a restart or before entering DeepSleep.
+- `System#Save` : is occuring right before a restart or before entering DeepSleep.
 
 For example the ruleset below turn on power right after Tasmota started, and turn it off just before entering DeepSleep 
 ``` haskel
 Rule1 ON Power1#Boot DO Power on ENDON ON System#Save DO Power off ENDON
 ```
-Any rule apply AFTER the Init() procedures of all sensors/drivers. This does mean that a POWER OFF on the GPIO may prevent sensors from being initialized correctly during start-up (e.g. DS18B20) and do not show up in teleperiod message. To ensure the GPIO is HIGH during restart you should define in the ´Configure` --> `Configure module` --> `Output Hi` on the GPIO instead of `RELAY 1` and avoid using any rules. To ensure the GPIO goes LOW after deepsleep you need to solder a 4.7K resistor between GND and the GPIO.
+Any rule apply AFTER the Init() procedures of all sensors/drivers. This does mean that a POWER OFF on the GPIO may prevent sensors from being initialized correctly during start-up (e.g. DS18B20) and do not show up in teleperiod message. To ensure the GPIO is HIGH during restart you should define in the `Configure` --> `Configure module` --> `GPIO x` to `Output Hi` instead of `RELAY 1` and avoid using any rules. To ensure the GPIO goes LOW after deepsleep you need to solder a 4.7K resistor between GND and the GPIO.
 
 Sequence is then as follow (only key lines are shown):
 ```