Updated MCP23008 MCP23017 (markdown)

MCP23008-MCP23017.md

@@ -30,7 +30,8 @@ The MCP230xx chip (or breakout board) must be connected to the ESP8266 and the I
 
 One that is complete you may want to confirm that the Tasmota firmware is finding your MCP23008/MCP23017 chip by sending the command through serial or MQTT:
 
-`I2Cscan`
+``I2Cscan``
+
 
 You should see a response giving you an address within the range of the MCP23008/MCP23017 chip (0x20 through 0x27) which may look as follows
 
@@ -44,6 +45,7 @@ This option only requires the main define to be uncommented prior to compilation
 
 `#define USE_MCP230xx`
 
+
 There is a single command that may be used for resetting all pins to INPUT with the weak internal pull-up resistor DISABLED as follows:
 
 `sensor29 reset`
@@ -52,6 +54,7 @@ This will be confirmed by a response like this - note the 99's indicated in each
 
 `MQT: stat/sonoff/RESULT = {"Sensor29":{"D":99,"MODE":99,"PULL-UP":99}}`
 
+
 You may also query the existing configuration for a particular pin using
 
 `sensor29 pin,?`
@@ -119,8 +122,9 @@ Each pin can be in the following modes:
 * (4) Input (Int on High) - Will only respond with immediate telemetry, log and mqtt for the specific pin if the said pin was pulled high to VCC (3.3V or 5V), that would be 1 or High in binary for the specific pin.
 
 Default telemetry logging will occur for all pins as per the configured logging interval of the ESP8266 as configured in the Tasmota firmware options. The telemetry logging will push out to log and mqtt a JSON as follows:
-
-`tele/sonoff/SENSOR = {"Time":"2018-06-30T18:31:49","MCP23008":{"D0":0, "D1":0, "D2":0, "D3":0, "D4":0, "D5":0, "D6":0, "D7":0 }}`
+```
+tele/sonoff/SENSOR = {"Time":"2018-06-30T18:31:49","MCP23008":{"D0":0, "D1":0, "D2":0, "D3":0, "D4":0, "D5":0, "D6":0, "D7":0 }}
+```
 
 Again, this will depend on whether an MCP23008 or MCP23017 is used insofar that the number of pins/bits reported will be 8 (0 to 7) or 16 (0 to 15) respectively.