[deep_sleep] removed extra spaces (#5366)

Co-authored-by: Jonathan Swoboda <[email protected]>

Author: kotnik

content/components/deep_sleep.md

@@ -20,7 +20,7 @@ Next, tell the node how it should wakeup. On the ESP8266, you can only put the n
 for a duration using `sleep_duration`, note that on the ESP8266 `GPIO16` must be connected to
 the `RST` pin so that it will wake up again. On the ESP32, you additionally have the option
 to wake up on any RTC pin (`GPIO0`, `GPIO2`, `GPIO4`, `GPIO12`, `GPIO13`, `GPIO14`,
-`GPIO15`, `GPIO25`, `GPIO26`, `GPIO27`, `GPIO32`, `GPIO39`  ).
+`GPIO15`, `GPIO25`, `GPIO26`, `GPIO27`, `GPIO32`, `GPIO39`).
 
 While in deep sleep mode, the node will not do any work and not respond to any network traffic,
 even Over The Air updates. If the device's entities are appearing as **Unavailable** while your device is actively
@@ -36,7 +36,6 @@ deep_sleep:
 
 {{< note >}}
 Some ESP8266s have an onboard USB chip (e.g. D1 mini) on the chips' control line that is connected to the RST pin. This enables the flasher to reboot the ESP when required. This may interfere with deep sleep on some devices and prevent the ESP from waking when it's powered through its USB connector. Powering the ESP from a separate 3.3V source connected to the 3.3V pin and GND will solve this issue. In these cases, using a USB to TTL adapter will allow you to log ESP activity.
-
 {{< /note >}}
 
 ## Configuration variables