diff --git a/Energy-Saving.md b/Energy-Saving.md
index 5ca80c1e..52c46946 100644
--- a/Energy-Saving.md
+++ b/Energy-Saving.md
@@ -2,7 +2,7 @@ Using the [Sleep](Commands#sleep) command you can instruct Tasmota to sleep for
 
 As of 6.3.0.15 [Dynamic Sleep](Dynamic%20Sleep) is enabled by default with a value of 50. To continue using Normal Sleep you may disable it by using the command:
 
-`[SetOption60](Commands#setoption60) 1`
+[`SetOption60 1`](Commands#setoption60)
 
 [Click here to see the Wiki for Dynamic Sleep](Dynamic%20Sleep)
 
@@ -16,7 +16,7 @@ If your Sonoff needs to do something continuously, this will be affected. E.g. S
 Also, if using [KNX IP Protocol](KNX-Features), `Sleep` needs to be 0 in order to avoid losing any telegram.
 
 **Notes:**
-- Starting with Tasmota 6.1.1.12 `Sleep` ≠ `0` has no impact on real time related commands like `Uptime`, `Delay`, `[PulseTime](Commands#pulsetime)`, `[TelePeriod](Commands#teleperiod)` and `[Blinktime](Commands#blinktime)`.
+- Starting with Tasmota 6.1.1.12 `Sleep` ≠ `0` has no impact on real time related commands like `Uptime`, `Delay`, [`PulseTime`](Commands#pulsetime), [`TelePeriod`](Commands#teleperiod) and [`Blinktime`](Commands#blinktime).
 - As the WiFi Modem on an ESP8266 is the major consumer - using Sleep with WiFi AP mode enabled is more or less without effect.
 
 ## Sonoff power consumption and measurement
@@ -69,4 +69,4 @@ Further increasing the sleep value there are more and more ~90 ms periods with a
 As already noticed with `Sleep 100` the number periods having 8-10 mA instead of 15-20 mA are again increasing:
 ![sleep 250 1](https://user-images.githubusercontent.com/6636844/36341493-5696bf48-13ef-11e8-8155-44ac90200df8.png)
 
-The quantity measurement confirms the suspicion that a sleep value ≠ 0 results in reduce the power consumption about 1/3.
+The quantity measurement confirms the suspicion that a sleep value ≠ 0 results in reducing the power consumption about 1/3.