Fix links in Markdown after Github changed its parser

Author: mgreter

docs/api-value.md

@@ -1,7 +1,7 @@
 `Sass_Values` are used to pass values and their types between the implementer
 and LibSass. Sass knows various different value types (including nested arrays
 and hash-maps). If you implement a binding to another programming language, you
-have to find a way to [marshal] [1] (convert) `Sass_Values` between the target
+have to find a way to [marshal][1] (convert) `Sass_Values` between the target
 language and C. `Sass_Values` are currently only used by custom functions, but
 it should also be possible to use them without a compiler context.
 

docs/build-on-windows.md

@@ -3,14 +3,14 @@ Both should be considered experimental (MinGW was better tested)!
 
 ## Building via MingGW (makefiles)
 
-First grab the latest [MinGW for windows] [1] installer. Once it is installed, you can click on continue or open the Installation Manager via `bin\mingw-get.exe`.
+First grab the latest [MinGW for windows][1] installer. Once it is installed, you can click on continue or open the Installation Manager via `bin\mingw-get.exe`.
 
 You need to have the following components installed:
 ![Visualization of components installed in the interface](https://cloud.githubusercontent.com/assets/282293/5525466/947bf396-89e6-11e4-841d-4aa916f14de1.png)
 
-Next we need to install [git for windows] [2]. You probably want to check the option to add it to the global path, but you do not need to install the unix tools.
+Next we need to install [git for windows][2]. You probably want to check the option to add it to the global path, but you do not need to install the unix tools.
 
-If you want to run the spec test-suite you also need [ruby] [3] and a few gems available. Grab the [latest installer] [3] and make sure to add it the global path. Then install the missing gems:
+If you want to run the spec test-suite you also need [ruby][3] and a few gems available. Grab the [latest installer][3] and make sure to add it the global path. Then install the missing gems:
 
 ```bash
 gem install minitest

docs/build.md

@@ -1,4 +1,4 @@
-`libsass` is only a library and does not do much on its own. You need an implementation that you can use from the [command line] [6]. Or some [[bindings|Implementations]] to use it within your favorite programming language. You should be able to get [`sassc`] [6] running by following the instructions in this guide.
+`libsass` is only a library and does not do much on its own. You need an implementation that you can use from the [command line][6]. Or some [[bindings|Implementations]] to use it within your favorite programming language. You should be able to get [`sassc`][6] running by following the instructions in this guide.
 
 Before starting, see [setup dev environment](setup-environment.md).
 
@@ -11,27 +11,27 @@ We try to keep the code as OS independent and standard compliant as possible. Re
 
 Linux is the main target for `libsass` and we support two ways to build `libsass` here. The old plain makefiles should still work on most systems (including MinGW), while the autotools build is preferred if you want to create a [system library] (experimental).
 
-- [Building with makefiles] [1]
-- [Building with autotools] [2]
+- [Building with makefiles][1]
+- [Building with autotools][2]
 
 ### Building on Windows (experimental)
 
 Windows build support was added very recently and should be considered experimental. Credits go to @darrenkopp and @am11 for their work on getting `libsass` and `sassc` to compile with visual studio!
 
-- [Building with MinGW] [3]
-- [Building with Visual Studio] [11]
+- [Building with MinGW][3]
+- [Building with Visual Studio][11]
 
 ### Building on Max OS X (untested)
 
 Works the same as on linux, but you can also install LibSass via `homebrew`.
 
-- [Building on Mac OS X] [10]
+- [Building on Mac OS X][10]
 
 ### Building a system library (experimental)
 
 Since `libsass` is a library, it makes sense to install it as a shared library on your system. On linux this means creating a `.so` library via autotools. This should work pretty well already, but we are not yet committed to keep the ABI 100% stable. This should be the case once we increase the version number for the library to 1.0.0 or higher. On Windows you should be able get a `dll` by creating a shared build with MinGW. There is currently no target in the MSVC project files to do this.
 
-- [Building shared system library] [4]
+- [Building shared system library][4]
 
 Compiling with clang instead of gcc
 --
@@ -46,7 +46,7 @@ export CXX=/usr/bin/clang++
 Running the spec test-suite
 --
 
-We constantly and automatically test `libsass` against the official [spec test-suite] [5]. To do this we need to have a test-runner (which is written in ruby) and a command-line tool ([`sassc`] [6]) to run the tests. Therefore we need to additionally compile `sassc`. To do this, the build files of all three projects need to work together. This may not have the same quality for all build flavors. You definitely need to have ruby (2.1?) installed (version 1.9 seems to cause problems at least on windows). You also need some gems installed:
+We constantly and automatically test `libsass` against the official [spec test-suite][5]. To do this we need to have a test-runner (which is written in ruby) and a command-line tool ([`sassc`][6]) to run the tests. Therefore we need to additionally compile `sassc`. To do this, the build files of all three projects need to work together. This may not have the same quality for all build flavors. You definitely need to have ruby (2.1?) installed (version 1.9 seems to cause problems at least on windows). You also need some gems installed:
 
 ```bash
 ruby -v
@@ -67,7 +67,7 @@ export LIBSASS_VERSION="x.y.z."
 Continuous Integration
 --
 
-We use two CI services to automatically test all commits against the latest [spec test-suite] [5].
+We use two CI services to automatically test all commits against the latest [spec test-suite][5].
 
 - [LibSass on Travis-CI (linux)][7]
 [![Build Status](https://travis-ci.org/sass/libsass.png?branch=master)](https://travis-ci.org/sass/libsass)