minor changes

Author: blakadder

Diff for: Components.md

@@ -4,15 +4,15 @@ Components can be: buttons, switches, relays, LEDs, sensors, displays, MCU units
 
 Every Tasmota device has some components configured by default. Most often there is a relay, a button and a LED configured as is the case for a Sonoff Basic in the following image.
 
-![Overview of a Template](/docs/_media/components.png ':size=150')
+![Overview of a Template](_media/components.png ':size=150')
 
 
 > GPIOs configured as User (255) are the GPIOs that can be assigned to components in the Configure Module page. See next image for an example!
 
 ## Assigning Components
 If you wish to expand a device with a [peripheral](Peripherals) component, after properly wiring everything, you need to assign it to a free GPIO in **Configure Module** page or use command [`GPIO<x>`](commands#gpio).
 
-![GPIO Assign](/docs/_media/components2.png ':size=150')
+![GPIO Assign](_media/components2.png ':size=150')
 
 Read more about [peripherals](Peripherals).
 

Diff for: For-Developers.md

@@ -4,4 +4,4 @@
 
 ### Maintained Tasmota forks with additional features:  
 [**Time Proportioned Output Fork**](Time-Proportioned-Output-support)  
-[**PID Control Fork**](PID-Control-with-Sonoff-Devices)  
+[**PID Control Fork**](PID-Control)  

Diff for: New-device-page.md

@@ -2,13 +2,15 @@
 
 If MQTT is defined and [`PowerRetain`](Commands#powerretain) is used the last state will be stored permanently in MQTT database.
 
-| | |
+|Command | Description |
 |-|-|
 [`PowerRetain`](Commands#powerretain)	| Show current MQTT power retain state.<BR> `0` / `off` = disable MQTT power retain on status update *(default)* <BR> `1` / `on` = enable MQTT power retain on status update
 
-A message in your MQTT broker flagged as 'retained' will ***_always_ override the `PowerOnState`***. This is usually the cause for "ghost switching". Learn more in [MQTT retained messages explained](http://www.steves-internet-guide.com/mqtt-retained-messages-example/). Check out [this tutorial](https://www.youtube.com/watch?v=31IyfM1gygo) for troubleshooting switch ghosting.
+**BUT**, a message in your MQTT broker flagged as 'retained' will ***_always_ override the `PowerOnState`***. 
 
-### Clearing retained messages
+This is usually the main cause for "ghost switching". Learn more in [MQTT retained messages explained](http://www.steves-internet-guide.com/mqtt-retained-messages-example/). Check out [this tutorial](https://www.youtube.com/watch?v=31IyfM1gygo) for troubleshooting switch ghosting.
+
+### Clearing Retained Messages
 To check, if there is a retain flag set for the switch's power topic, monitor `cmnd/+/power` in a MQTT client (recommended [MQTT.fx](https://mqttfx.jensd.de/) for Windows or [Eclipse Mosquitto](https://mosquitto.org/) in linux).
 
 You can use [Tasmota Device Manager](https://github.com/jziolkowski/tdm) to clear all retained messages for selected device with a single click.
@@ -22,7 +24,7 @@ or use the following tutorials/forum threads:
 
 ## Predefined PowerOnState functionality
 
-| | |
+| Command | Description |
 |-|-|
 |[`PowerOnState`](Commands#poweronstate) | Control relay state after _**powering up**_ the device.<BR> `0` / `OFF` = keep relay(s) OFF after power up <BR> `1` / `ON` = turn relay(s) ON after power up <BR> `2` / `TOGGLE` = toggle relay(s) from last saved state <BR> `3` = switch relay(s) to their last saved state *(default)* <BR> `4` = turn relay(s) ON and disable further relay control <BR> `5` = after a `PulseTime` period turn relay(s) ON (acts as inverted [`PulseTime`](Commands#pulsetime) mode)|