Fix markdown lint

https://github.com/DavidAnson/markdownlint/blob/v0.5.0/doc/Rules.md

MD012 - Multiple consecutive blank lines
MD014 - Dollar signs used before commands without showing output
MD022 - Headers should be surrounded by blank lines
MD026 - Trailing punctuation in header
MD029 - Ordered list item prefix
MD031 - Fenced code blocks should be surrounded by blank lines
MD032 - Lists should be surrounded by blank lines
MD033 - Inline HTML
MD034 - Bare URL used

Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>

3 files changed, 32 insertions, 28 deletions

diff --git a/getting-started/footers/intel-footer.md b/getting-started/footers/intel-footer.md
index 191ff98..0c75128 100644
--- a/getting-started/footers/intel-footer.md
+++ b/getting-started/footers/intel-footer.md
@@ -1,47 +1,52 @@
 ## BIOS update
-Both the Joule and the Minnowboard require a BIOS upgrade. **Don t loose time trying without.**<br>
-https://firmware.intel.com/projects/minnowboard-max<br>
-https://software.intel.com/en-us/flashing-the-bios-on-joule
+
+Both the Joule and the Minnowboard require a BIOS upgrade. **Don t loose time trying without.**  
+<https://firmware.intel.com/projects/minnowboard-max>  
+<https://software.intel.com/en-us/flashing-the-bios-on-joule>
 
 ## Creating a bootable image
-Multiple options are avaiable but dd and tar can very easily let you down due to the requirement to pass SMACK labels, create a proper UEFI configuration and a few other tricks.<br>
-The script [mkefi-agl.sh](https://github.com/dominig/mkefi-agl.sh) has been done to help you.<br>
-The option -h will print the help and the option -v will detailled the operation and ease any debug.<br>
-
-## Selecting the SD or USB to boot.
-When booting a Minnowboard or a Joule you can change the default boot device by hitting F2 during initial UEFI boot.
-It's easier to acheive it in the right time with a USB keyboard than via serial link.
-During boot USB hub are not supported, you need to connect the keyboard directly in the USB socket.<br>
-It's also preferable to use F9 and to change the boot order once for all.<br>
+
+Multiple options are avaiable but dd and tar can very easily let you down due to the requirement to pass SMACK labels, create a proper UEFI configuration and a few other tricks.  
+The script [mkefi-agl.sh](https://github.com/dominig/mkefi-agl.sh) has been done to help you.  
+The option -h will print the help and the option -v will detailled the operation and ease any debug.  
+
+## Selecting the SD or USB to boot
+
+When booting a Minnowboard or a Joule you can change the default boot device by hitting F2 during initial UEFI boot.  
+It's easier to acheive it in the right time with a USB keyboard than via serial link.  
+During boot USB hub are not supported, you need to connect the keyboard directly in the USB socket.  
+It's also preferable to use F9 and to change the boot order once for all.  
 Please note: You can only change the boot order, when a valid device is inserted in the corresponding port (USB or SD).
 
-The Minnow, Joule, many laptops and NUCs will not accept to boot with some USB3 stick. If you have some trouble to get your USB3 stick detected during boot, swap it for a USB2. In anycase working with SD card is faster to flash and to boot. SD should be prefered.<br>
+The Minnow, Joule, many laptops and NUCs will not accept to boot with some USB3 stick. If you have some trouble to get your USB3 stick detected during boot, swap it for a USB2. In anycase working with SD card is faster to flash and to boot. SD should be prefered.  
 The Joule seems to refuse to boot with my SD-HC-I type cards while I had no problem with the Minnow. If you work with a Joule, use regular SD-HC (mode 4 and 10 work fine)
 
-
 ## Serial debug Port
 
-Serial debug port ID varies with the HW platform :<br>
-By default AGL build Intel target as a Minnowboard where serial is /dev/ttyS0 <br>
-On Joule and MRB the serial debug is /dev/ttyS2 <br>
+Serial debug port ID varies with the HW platform :  
+By default AGL build Intel target as a Minnowboard where serial is /dev/ttyS0  
+On Joule and MRB the serial debug is /dev/ttyS2  
 
 You may have to change the configuration in your boot loader which is located in the EFI partition.
 
 ## Serial debug cable
 
-On the Minnowboard the serial cable is a FTDI serial cable. The wiring can be found [here](http://wiki.minnowboard.org/MinnowBoard_MAX_HW_Setup).<br>
-On the Joule the serial connection is done via the micro USB cable which is not provided in the Developer kit. Details can be found [here](https://software.intel.com/en-us/node/667851).<br>
+On the Minnowboard the serial cable is a FTDI serial cable. The wiring can be found [here](http://wiki.minnowboard.org/MinnowBoard_MAX_HW_Setup).  
+On the Joule the serial connection is done via the micro USB cable which is not provided in the Developer kit. Details can be found [here](https://software.intel.com/en-us/node/667851).  
 Interface speed is 115200 bps, 8 bits, no parity, no flow control
 
 ## Which port name is used to define the connected display(s)
 
-Port naming may change with HW platforms and connected display. The simplest is to check following the fist boot, in the systemd journal which display names are listed.<br>
-```
+Port naming may change with HW platforms and connected display. The simplest is to check following the fist boot, in the systemd journal which display names are listed.
+
+```bash
 journalctl |grep Output
 ```
-**Note:** The Output information is only listed if a real Display is connected to the connector on the board.<br>
-The file holding that configuration is /etc/xdg/weston/weston.ini<br>
+
+**Note:** The Output information is only listed if a real Display is connected to the connector on the board.  
+The file holding that configuration is /etc/xdg/weston/weston.ini  
 Common Display name for Intel are
+
 * HDMI-A-1
 * HDMI-A-2
 * LVDS-1
diff --git a/getting-started/footers/porter-footer.md b/getting-started/footers/porter-footer.md
index 697ff39..7d1417d 100644
--- a/getting-started/footers/porter-footer.md
+++ b/getting-started/footers/porter-footer.md
@@ -5,7 +5,7 @@ If Weston fails to start double check :
 and verify that the output name and screen resolution matches the configured U-Boot environment.  
 For example on Renesas Porter board rev 1.0 with screen resolution 1024x768:
 
-```
+```bash
 [core]
 shell=desktop-shell.so
 backend=drm-backend.so
@@ -21,4 +21,3 @@ mode=1024x768
 #mode=1920x1080
 #mode=173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync
 ```
-
diff --git a/getting-started/footers/raspberrypi-footer.md b/getting-started/footers/raspberrypi-footer.md
index cb914dc..f5ff16f 100644
--- a/getting-started/footers/raspberrypi-footer.md
+++ b/getting-started/footers/raspberrypi-footer.md
@@ -2,7 +2,7 @@
 
 Append to following lines to **conf/local.conf** to include libomxil under a commercial license to your build:
 
-```
+```bash
 # For libomxil
 LICENSE_FLAGS_WHITELIST = "commercial"
 
@@ -13,7 +13,7 @@ IMAGE_INSTALL_append = " libomxil"
 
 If you have Raspberry Pi official 7" touchscreen connected, you can rotate it with these lines in /etc/xdg/weston/weston.ini
 
-```
+```bash
 root@raspberrypi3:/etc/xdg/weston# cat weston.ini
 [core]
 backend=drm-backend.so
@@ -49,7 +49,7 @@ It is possible to debug AGL images on Raspberry Pi using 3.3V USB to serial cabl
 
 * Plug the USB connector of the cable to your computer and use your favorite tool for serial communication, for example on Ubuntu and other Linux distributions you may use screen:
 
-```
+```bash
 sudo screen /dev/ttyUSB0 115200
 ```