Documentation: fix inter-page links

Author: borsboom

doc/faq.md

@@ -1,10 +1,10 @@
 So that this doesn't become repetitive: for the reasons behind the answers
-below, see the [[Architecture]] page. The goal of the answers here is to be as
+below, see the [Architecture](architecture.md) page. The goal of the answers here is to be as
 helpful and concise as possible.
 
 #### Where is stack installed and will it interfere with `ghc` (etc) I already have installed?
 
-Stack itself is installed in normal system locations based on the mechanism you used (see the [[Downloads]] page). Stack installs the Stackage libraries in `~/.stack` and any project libraries or extra dependencies in a `.stack-work` directory within each project's directory. None of this should affect any existing Haskell tools at all.
+Stack itself is installed in normal system locations based on the mechanism you used (see the [Install and upgrade](install_and_upgrade.md) page). Stack installs the Stackage libraries in `~/.stack` and any project libraries or extra dependencies in a `.stack-work` directory within each project's directory. None of this should affect any existing Haskell tools at all.
 
 #### What is the relationship between stack and cabal?
 
@@ -174,7 +174,7 @@ of those three. Updating the index will have no impact on stack's behavior.
 
 #### I have a custom package index I'd like to use, how do I do so?
 
-You can configure this in your stack.yaml. See [[stack.yaml]]
+You can configure this in your stack.yaml. See [YAML configuration](yaml_configuration.md).
 
 #### How can I make sure my project builds against multiple ghc versions?
 
@@ -202,7 +202,7 @@ $ STACK_YAML=stack-7.10.yaml stack build  # builds using the given yaml file
 #### I heard you can use this with Docker?
 
 Yes, stack supports using Docker with images that contain preinstalled Stackage
-packages and the tools. See [[Docker]] for details.
+packages and the tools. See [Docker integration](docker_integration.md) for details.
 
 #### How do I use this with Travis CI?
 
@@ -295,4 +295,4 @@ collect2: error: ld returned 1 exit status
 --  While building package tmp-0.1.0.0 using:
       /home/philip/.stack/programs/x86_64-linux/ghc-7.10.1/bin/runghc-7.10.1 -package=Cabal-1.22.2.0 -clear-package-db -global-package-db /home/philip/tmp/Setup.hs --builddir=dist-stack/x86_64-linux/Cabal-1.22.2.0/ build
     Process exited with code: ExitFailure 1
-```
+```

doc/install_and_upgrade.md

@@ -1,6 +1,6 @@
 Distribution packages are available for [Ubuntu](#ubuntu), [Debian](#debian), [CentOS / Red Hat](#centos--red-hat), [Fedora](#fedora) and [Arch Linux](#arch-linux). Binaries for other operating systems are available on [the releases page](https://github.com/fpco/stack/releases). For the future, we have plans to support more OSes.
 
-Binaries are signed with this [[Signing key]].
+Binaries are signed with this [signing key](SIGNING_KEY.md).
 
 ## Windows
 

doc/nonstandard_project_init.md

@@ -62,18 +62,18 @@ packages:
     commit: 8debedd3fcb6525ac0d7de2dd49217dce2abc0d9
 ```
 
-## Issues Referenced 
+## Issues Referenced
   - https://github.com/commercialhaskell/stack/issues/254
   - https://github.com/commercialhaskell/stack/issues/199
 
 # Private Hackage
 Working with a private Hackage is currently supported in certain situations.
-There exist special entries in `stack.yaml` that may help you. In a `stack.yaml` file, it is possible 
+There exist special entries in `stack.yaml` that may help you. In a `stack.yaml` file, it is possible
 to add lines for packages in your database referencing the sdist locations via an `http` entry, or to use a `Hackage` entry.
 
 The recommended stack workflow is to use git submodules instead of a private Hackage. Either by using git submodules and listing the directories in the packages section of `stack.yaml`, or by adding the private dependencies as git URIs with a commit SHA to the `stack.yaml`. This has the large benefit of eliminating the need to manage a Hackage database and pointless version bumps.
 
-For further information see [[stack.yaml]]
+For further information see [YAML configuration](yaml_configuration.md)
 
 ## Issues Referenced
   - https://github.com/commercialhaskell/stack/issues/445