Fixed newlines...

Author: jeanlemotan

README.md

@@ -17,20 +17,20 @@ The ESP camera component was modified to send the data as it's received from the
 
 The wifi data is send using packet injection with configurable rate - from 2 MB CCK to 72MB MCS7 - and power.
 
-The air unit can also record the video straight from the camera to a sd card. The format is a rudimentary MJPEG without any header so when playing back the FPS will be whatever your player will decide.
+The air unit can also record the video straight from the camera to a sd card. The format is a rudimentary MJPEG without any header so when playing back the FPS will be whatever your player will decide.\
 There is significant buffering when writing to SD (3MB at the moment) to work around the very regular slowdowns of sd cards.
 
 
 
 The receiver is a Raspberry PI 4 with 2 wifi adapters in monitor mode (TL-WN722N). The adapters work as diversity receivers and the data is reconstructed from the FEC packets.
 
-The JPEG decoding is done with turbojpeg to lower latency and - based on the resolution - can take between 1 and 7 milliseconds.
+The JPEG decoding is done with turbojpeg to lower latency and - based on the resolution - can take between 1 and 7 milliseconds.\
 It's then uploaded to 3 separate textures as YUV and converted to RGB in a shader.
 
-The link is bi-directional so the ground station can send data to the air unit. At the moment it sends camera and wifi configuration data but I plan to have a full bi-directional serial port for telemetry coming soon.
+The link is bi-directional so the ground station can send data to the air unit. At the moment it sends camera and wifi configuration data but I plan to have a full bi-directional serial port for telemetry coming soon.\
 The back link uses 64byte packets with a 2/6 FEC encoding (so quite solid) at a low wifi rate (I think 1Mb).
 
-This is very WIP at the moment, but it proves that the ESP32 can definitely stream video with very low latency. 
+This is very WIP at the moment, but it proves that the ESP32 can definitely stream video with very low latency. \
 I plan to use this is a long range micro quad.
 
 Here is a video shot at 30 FPS at 800x600 (video converted from the source mjpeg):
@@ -44,18 +44,18 @@ https://user-images.githubusercontent.com/10252034/116135308-43c08c00-a6d1-11eb-
 - In the air_firmware, execute this: `idf.py -p /dev/tty.usbserial1 flash monitor`. Replace `tty.usbserial1` with your serial port.
 - Make sure you place the board in flashing mode bu connecting IO0 to GND and resetting the board.
 - After compiling and resetting, you should get some stats per second, smth like this in the console:
-`WLAN S: 695196, R: 350, E: 0, D: 0, % : 0 || FPS: 64, D: 401268 || D: 0, E: 0`
-`WLAN S: 761616, R: 420, E: 0, D: 0, % : 0 || FPS: 69, D: 443679 || D: 0, E: 0`
-`WLAN S: 763092, R: 420, E: 0, D: 0, % : 0 || FPS: 69, D: 449410 || D: 0, E: 0`
-`WLAN S: 764568, R: 420, E: 0, D: 0, % : 0 || FPS: 69, D: 450996 || D: 0, E: 0`
+`WLAN S: 695196, R: 350, E: 0, D: 0, % : 0 || FPS: 64, D: 401268 || D: 0, E: 0`\
+`WLAN S: 761616, R: 420, E: 0, D: 0, % : 0 || FPS: 69, D: 443679 || D: 0, E: 0`\
+`WLAN S: 763092, R: 420, E: 0, D: 0, % : 0 || FPS: 69, D: 449410 || D: 0, E: 0`\
+`WLAN S: 764568, R: 420, E: 0, D: 0, % : 0 || FPS: 69, D: 450996 || D: 0, E: 0`\
 `WLAN S: 761616, R: 350, E: 0, D: 0, % : 0 || FPS: 69, D: 449347 || D: 0, E: 0`
 
 ### Raspberry Pi ground station:
 - I use a Raspberry Pi 4 in a RasPad3 enclosure, but any HDMI display should work. Raspberry Pi 3 should work as well.
 - You need to use 2 TL-WN722N adapters connected to USB. Check the EZ-wifibroadcast wiki for more info about the hardware revision of these adapters and alternative adapters. Make sure you get the 2.4GHz ones, of course. NOTE: the adapters are critical, not all work in monitor mode!
-- If you only have one adapter or they are not called `wlan1` & `wlan2`, check the `main.cpp` file and change the names and number there:
-	`rx_descriptor.interfaces = {"wlan1", "wlan2"};`
-	`tx_descriptor.interface = "wlan1";`
+- If you only have one adapter or they are not called `wlan1` & `wlan2`, check the `main.cpp` file and change the names and number there:\
+	`rx_descriptor.interfaces = {"wlan1", "wlan2"};`\
+	`tx_descriptor.interface = "wlan1";`\
 	Eventually this should be command line driven.
 - The UI uses ImGui and is touch driven - but mouse should work as well
 - Dependencies:
@@ -64,15 +64,15 @@ https://user-images.githubusercontent.com/10252034/116135308-43c08c00-a6d1-11eb-
 - Run `sudo -E DISPLAY=:0 ./gs`
 
 The GS can run both with X11 and without. However, to run it without GS you need to compile SDL2 yourself to add support for kmsdrm:
-`git clone https://github.com/libsdl-org/SDL.git`
-`cd SDL`
-`mkdir build`
-`cd build`
-`../configure --disable-video-rpi --enable-video-kmsdrm --enable-video-x11 --disable-video-opengl`
-`make -j5`
+`git clone https://github.com/libsdl-org/SDL.git`\
+`cd SDL`\
+`mkdir build`\
+`cd build`\
+`../configure --disable-video-rpi --enable-video-kmsdrm --enable-video-x11 --disable-video-opengl`\
+`make -j5`\
 `sudo make install`
 
-To run without X11 using the just compiled SDL2, do this:
+To run without X11 using the just compiled SDL2, do this:\
 `sudo -E LD_LIBRARY_PATH=/usr/local/lib DISPLAY=:0 ./gs`
 
 Some other things that should improve latency: