Updated FAQ (markdown)

FAQ.md

@@ -1,4 +1,4 @@
-#### I have a performance problem....
+# I have a performance problem....
 
 Whoa! Everything got slow all of a sudden...
 
@@ -18,7 +18,7 @@ Starting with revision [725e881a](https://github.com/vim-airline/vim-airline/com
 
 If you still encounter performance issues, provide some profiling information, see issue [1026](https://github.com/vim-airline/vim-airline/issues/1026)
 
-#### A symbol in the statusline looks is overdrawn or too crammed
+# A symbol in the statusline looks is overdrawn or too crammed
 
 This is typically an issue with your terminal which does not correctly draw the symbol. You can configure other symbols, please check the [Documentation](https://github.com/vim-airline/vim-airline/blob/ebb89a0846ff8b8bc64579155d661b825f97d3f2/doc/airline.txt#L369-L389). You can check how it looks like in your terminal using the following command:
 ```vim
@@ -32,7 +32,8 @@ If any of the symbols does not look right, you can configure it in your `.vimrc`
 
   let g:airline_symbols.colnr = ' ℅:'
 ```
-#### The powerline font symbols are not showing up
+
+# The powerline font symbols are not showing up
 
 Adding `let g:airline_powerline_fonts = 1` to your vimrc will automatically populate the `g:airline_symbols` dictionary with the proper font glyphs for various symbols.
 
@@ -48,7 +49,7 @@ If you are using fontconfig, make sure bitmap fonts are not disabled. That rule,
 
 Also make sure Terminal uses the same font style (e.g. Meslo) as specified in your vimrc.
 
-#### The Themes are missing.
+# The Themes are missing.
 
 Themes have moved to
 another repository as of [this commit][e].
@@ -62,7 +63,7 @@ Plugin 'vim-airline/vim-airline-themes'
 
 See https://github.com/vim-airline/vim-airline-themes for more.
 
-#### The powerline font symbols are partially messed up
+# The powerline font symbols are partially messed up
 
 You are likely using the [fontconfig](https://powerline.readthedocs.org/en/latest/installation/linux.html#font-installation) method.  If that is the case, you need to override the space character like so:
 
@@ -71,31 +72,31 @@ You are likely using the [fontconfig](https://powerline.readthedocs.org/en/lates
     endif
     let g:airline_symbols.space = "\ua0"
 
-#### The powerline font is not perfectly lined up, or there a bit of whitespace in between symbols, or they are cut off
+# The powerline font is not perfectly lined up, or there a bit of whitespace in between symbols, or they are cut off
 
 This is a complicated issue with no easy solution.  Depending on the operating system, the font you have installed, the font you have patched, how the font was patched, terminal vs GUI, which terminal emulator itself (and how the emulator is configured), what font size, all have an effect on how the font turns on.
 
 Try various combinations of the above and you'll eventually find something that works.
 
-#### There is a pause when leaving insert mode
+# There is a pause when leaving insert mode
 
 You need to set `ttimeoutlen`; 10 is a good number to start with. Many places say to edit `timeoutlen`, but that could conflict with other plugins.
 
-#### There is a pause when entering insert mode
+# There is a pause when entering insert mode
 
 You are running an older version of Vim 7.3, try updating to a newer version.
 
-#### You don't see any colors
+# You don't see any colors
 
 All of the themes use a 256 terminal color palette.  It's likely that the value of `t_Co` is misconfigured.  please see this [article][n] on how to configure your terminal.  Pull requests for 8 and 16 color terminals are welcome.
 
 If you are using tmux, start it with the -2 option.  This lets it know that the terminal supports 256 colors.
 
-#### The colors look a little off for some themes.
+# The colors look a little off for some themes.
 
 Certain themes are derived from the active colorscheme by extracting colors from predefined highlight groups.  These airline themes will look good for their intended matching colorschemes, but will be hit or miss when loaded with other colorschemes.
 
-#### You do not see the current Git branch
+# You do not see the current Git branch
 
 You need [fugitive](https://github.com/tpope/vim-fugitive) to see the current git branch. If you have it and still don't see it then one of two things is happening:
 
@@ -103,31 +104,31 @@ You need [fugitive](https://github.com/tpope/vim-fugitive) to see the current gi
 
 2. You have too new of a version of vim-fugitive, and are running the latest release of vim-airline rather than a git version.  [tpope/vim-fugitive@5d11ff7](https://github.com/tpope/vim-fugitive/commit/5d11ff7) made `fugitive#head()` autoloadable, which broke the latest 0.9.0 release of vim-airline.  The next release of vim-airline is expected in December (see [#1820](https://github.com/vim-airline/vim-airline/issues/1820)), and the fix will not be backported (see [#1815](https://github.com/vim-airline/vim-airline/issues/1815)).  Until then, you either need to downgrade vim-fugitive to v2.3, or run a recent git commit version of vim-airline.
 
-#### vim-bufferline is printing to the statusline as well as the command bar
+# vim-bufferline is printing to the statusline as well as the command bar
 
 You can disable automatic echoing by adding `let g:bufferline_echo = 0` to your vimrc.
 
-#### The statusline wraps
+# The statusline wraps
 
 You are probably using iTerm with double-width characters enabled. Either disable this, or `set ambiwidth=double` in your vimrc.
 
-#### How do i get rid of the default mode indicator?
+# How do i get rid of the default mode indicator?
 
 Add `set noshowmode` to your vimrc.
 
-#### The completion popup is broken/blank when preview is enabled with vim-airline
+# The completion popup is broken/blank when preview is enabled with vim-airline
 
 For more details see this [issue](https://github.com/bling/vim-airline/issues/78).  This appears to depend on the version of Vim installed.  Upgrade to the newest version available.
 
-#### You see things like `^^^^^` in the statusline.
+# You see things like `^^^^^` in the statusline.
 
 Try adding `set fillchars+=stl:\ ,stlnc:\ ` to your vimrc.  Also, make sure you're using a colorscheme that has different `StatusLine` and `StatusLineNC` highlight groups.
 
-#### Colors go out of sync when I source my `vimrc`
+# Colors go out of sync when I source my `vimrc`
 
 vim-airline internally uses autocmds to change colors, and the order of autocmds may change from one configuration to the next.  Sometimes this means that if you use things like `BufEnter` you may find that the colors go out of sync.  vim-airline exposes a command `AirlineRefresh` which you can use to reload all the colors manually.
 
-#### Where should I store my own custom theme?
+# Where should I store my own custom theme?
 
 You could simply edit `dark.vim` in place, since this is the default theme.
 
@@ -139,10 +140,10 @@ But (especially if you are using a bundler to install airline), you may prefer t
 4. To make it load on startup, add to your `.vimrc`:  
    `:let g:airline_theme='your_theme_name'`
 
-#### Can I get better font rendering in Windows gvim?
+# Can I get better font rendering in Windows gvim?
 
 If you are using a gVim with the +directx interface enabled at compile time, you can use DirectX rendering. This will provide better font rendering for the powerline glyphs. You can enable this using:
-```
+```vim
 set encoding=utf-8   
 set rop=type:directx,gamma:1.0,contrast:0.5,level:1,geom:1,renmode:4,taamode:1
 ```
@@ -155,14 +156,14 @@ Note: There exists a severe [Rendering Bug with Windows Gvim and the Directx Ren
 [e]: https://github.com/vim-airline/vim-airline/commit/d7fd8ca649e441b3865551a325b10504cdf0711b
 [n]: http://vim.wikia.com/wiki/256_colors_in_vim
 
-#### How can I make Airline look like powerline?
+# How can I make Airline look like powerline?
 
 If you want your airline looks like a new powerline install (i.e all options by default), you only have to add
 this option to your `.vimrc` 
 
 `let g:airline_section_z = airline#section#create(['windowswap', '%3p%% ', 'linenr', ':%3v']) `
 
-####  How can I remove those angle at the end?
+#  How can I remove those angle at the end?
 
 This happens, because the warning and error sections are empty. However, because of the way the airline sections are evaluated, those separators will always be shown. 
 You can disable them, if you put this option into your `.vimrc`
@@ -171,7 +172,7 @@ You can disable them, if you put this option into your `.vimrc`
 
 This poses a small performance penalty, however.
 
-#### How can I disable certain autocommands?
+# How can I disable certain autocommands?
 
 You can simply set the `&eventignore` option to the events that you'd like to ignore. For example to disable the `FocusGained` and `FocusLost` events (which some terminals may not be able to handle correctly) you would set in your `.vimrc`: