Fix up some formatting and a typo. (should be "Using then command line" not "Using command line")

Using-the-command-line.md

@@ -1,14 +1,16 @@
-## CLI
+# CLI
+--
 At its core, RetroArch is a command-line application. Getting familiar with the command-line helps you understand the design principles of RetroArch.
 
-## Load a ROM and libretro core
+## Loading a ROM and libretro core
+--
     retroarch -L /path/to/libretro/core.so game.rom
 
 ### Get verbose logging output
-To get a better idea on what's going on, use `--verbose` flag as well.
+To get a better idea on what's going on, use the `--verbose` flag as well.
 If you want to report a bug, it is **vital** that this log is included.
 
-### Use a config file
+### Using a config file
 By default, RetroArch looks for a config in various places depending on OS:
 
 - **Linux/OSX**: `$XDG_CONFIG_HOME/retroarch/retroarch.cfg`, then `~/.config/retroarch/retroarch.cfg`, then `~/.retroarch.cfg`, and finally, as a fallback, `/etc/retroarch.cfg`.
@@ -20,6 +22,7 @@ To help creating configs with a GUI, RetroArch-Phoenix is a suitable frontend.
 The config file with all options are documented [here](https://raw.github.com/Themaister/RetroArch/master/retroarch.cfg). On Linux and OSX, it is normally installed to `/etc/retroarch.cfg`. On Windows releases you'll find it in the directory along with `retroarch.exe` after a fresh zip extraction (it quickly gets overwritten).
 
 ## `retroarch --help`
+--
 Use it. You'll probably discover some features you didn't think about.
    
     ===================================================================
@@ -83,6 +86,7 @@ Use it. You'll probably discover some features you didn't think about.
         -D/--detach: Detach RetroArch from the running console. Not relevant for all platforms.
 
 ## `retroarch --features`
+--
 If you're unsure if a particular feature is compiled in, this helps:
 
     Features: