Serial-Communication.md

@@ -2,7 +2,7 @@ This page describes how the serial drivers work and how to access them.
 
 ## Using `stdio.h` (*printf()*, *scanf()*, ...)
 
-When you use functions like *printf()*, *scanf()*, *puts()*, *gets()* etc... inside your code, Miosix redirects them to one of the microcontroller's serial ports, called the **default** serial port. This is defined in `miosix/config/arch/<your_arch>/<your_board>/board_settings.h`, along with the default baudrate and other related configurations. The file looks like this:
+When you use functions like _printf()_, _scanf()_, _puts()_, _gets()_ etc... inside your code, Miosix redirects them to one of the microcontroller's serial ports, called the **default** serial port. This is defined in `miosix/config/arch/<your_arch>/<your_board>/board_settings.h`, along with the default baudrate and other related configurations. The file looks like this:
 
 ```cpp
 const unsigned int defaultSerial=1;             //default serial = USART1
@@ -12,7 +12,7 @@ const bool defaultSerialFlowctrl=false;         //use rts/cts
 #define SERIAL_1_DMA                            //use the DMA
 ```
 
-> :warning: **WARNING: *printf()* is very heavy and can significantly modify the timings if used inside drivers. For this reason, we suggest instead the use of *TRACE()* throughout the code. *TRACE()* works as a normal *printf()* if *DEBUG* is defined (see below example), otherwise it does not perform any operation.**
+> :warning: **WARNING: __printf()__ is very heavy and can significantly modify the timings if used inside drivers. For this reason, we suggest instead the use of __TRACE()__ throughout the code. __TRACE()__ works as a normal __printf()__ if __DEBUG__ is defined (see below example), otherwise it does not perform any operation.**
 
 You can find an example in the [Hello Skyward tutorial](Hello-Skyward) page.
 
@@ -26,7 +26,7 @@ A part from the default serial port, Miosix offers access to up to 3 USARTs in S
    | 2      | PA2  | PA3  | PA0  | PA1  |             |             |
    | 3      | PB10 | PB11 | PB13 | PB14 |             | default     |
 
-Miosix gives the possibility to access these USART ports through Unix-like [device files](https://en.wikipedia.org/wiki/Device_file). In particular, to access a particular USART of your microcontroller (e.g. USART2) you should modify the *bspInit2()* method
+Miosix gives the possibility to access these USART ports through Unix-like [device files](https://en.wikipedia.org/wiki/Device_file). In particular, to access a particular USART of your microcontroller (e.g. USART2) you should modify the _bspInit2()_ method
  inside the [Board Support Package](BSP) as follows:
 
 ```cpp
@@ -67,15 +67,15 @@ To communicate with a board from your PC you will need a USB-TTL driver, or you
 Once your USB-TTL dongle is attached to the PC, you will need to connect the RX and TX of the dongle to the TX and RX of the decided serial port in your Discovery (**ATTENTION:** RX discovery<-->TX usb dongle and vice-versa).
 
 Then you can open a communication using:
-- **Putty** in Windows: Select the *Session* tab on the left panel and select *Serial* as "Connection type". You will need to know the COM port to which the Discovery is attached (you can find it out in *Control Pane > Device Manager*).
-- **GTKTerm** on Linux: *Configuration* > *Port* > `/dev/ttyUSB0` and select baudrate (19200 for the default serial). You can also use `screen` or `minicom`.
+- **Putty** in Windows: Select the _Session_ tab on the left panel and select _Serial_ as "Connection type". You will need to know the COM port to which the Discovery is attached (you can find it out in _Control Pane > Device Manager_).
+- **GTKTerm** on Linux: _Configuration_ > _Port_ > `/dev/ttyUSB0` and select baudrate (19200 for the default serial). You can also use `screen` or `minicom`.
 
 In both cases, you will need to set the correct port and baudrate, and you may need install some drivers for the USB dongle to make things work.
 
 --------
 
 ### Auxtty USART (STM32F407VG only)
-For the *f407vg* board, there's also another serial port, called **auxtty**: you need to remove the comment from the `board_settings.h` in order to use it:
+For the _STM32F407VG_ board, there's also another serial port, called `auxtty`: you need to remove the comment from the `board_settings.h` in order to use it:
 
 ```cpp
 //#define AUX_SERIAL "auxtty"    UNCOMMENT THIS TO OPEN THE SERIAL