Fixing broken links

Author: JakeGinnivan

docs/build-server-support.md

@@ -14,11 +14,11 @@ When running in MSBuild either from the MSBuild Task or by using the `/proj mypr
 ## Setup guides
  - [AppVeyor](more-info/build-server-setup/appveyor.md)
  - [TeamCity](more-info/build-server-setup/teamCity.md)
- - [AppVeyor](more-info/build-servers/appveyor.md)
- - [TeamCity](more-info/build-servers/teamcity.md)
- - [MyGet](more-info/build-servers/myget.md)
- - [Bamboo](more-info/build-servers/bamboo.md)
- - [Jenkins](more-info/build-servers/jenkins.md)
- - [Continua CI](more-info/build-servers/continua.md))
- - [Team Build (TFS)](more-info/build-servers/teambuild.md)
- - [TFS Build vNext](more-info/build-servers/tfs-build-vnext.md)
+ - [AppVeyor](more-info/build-server-setup/appveyor.md)
+ - [TeamCity](more-info/build-server-setup/teamcity.md)
+ - [MyGet](more-info/build-server-setup/myget.md)
+ - [Bamboo](more-info/build-server-setup/bamboo.md)
+ - [Jenkins](more-info/build-server-setup/jenkins.md)
+ - [Continua CI](more-info/build-server-setup/continua.md))
+ - [Team Build (TFS)](more-info/build-server-setup/teambuild.md)
+ - [TFS Build vNext](more-info/build-server-setup/tfs-build-vnext.md)

docs/examples.md

@@ -1,5 +1,5 @@
 # Examples
-![README](images/CommitGraph.png)
+![README](img/CommitGraph.png)
 
 At each commit sha GitVersion will calculate:
 
@@ -24,10 +24,10 @@ This is just a small sample of the way GitVersion works. The idea is you just pl
  - support/
  - release/
 
-If you have other branch types GitVersion is entirely configuration driven, so check out the [Configuration](#Configuration) section of the readme to understand how to make GitVersion work for you.
+If you have other branch types GitVersion is entirely configuration driven, so check out the [Configuration](configuration.md) section of the readme to understand how to make GitVersion work for you.
 
 ## GitFlow
-[See GitFlow Examples](branchingStrategies/gitFlowExamples.md)
+[See GitFlow Examples](git-branching-strategies/gitflow-examples.md)
 
 ## GitHubFlow
-[See GitHubFlow Examples](branchingStrategies/gitHubFlowExamples.md)
+[See GitHubFlow Examples](git-branching-strategies/githubflow-examples.md)

docs/faq.md

@@ -1,15 +1,15 @@
 # FAQ
 
 ## Why is my version not incrementing?
-GitVersion calculates the semantic version, this will only change once per *release*. Read more at [version increments](./versionIncrements.md)
+GitVersion calculates the semantic version, this will only change once per *release*. Read more at [version increments](more-info/version-increments.md)
 
 ## How can GitVersion run for a shallow clone or checkout on server working directories
-GitVersion needs a proper git repository to run, some build servers do not do a proper clone which can cause issues. GitVersion has a feature called [dynamic repositories](Dynamic-Repositories.md) which solves this by cloning the repository and working against that clone instead of the working directory.
+GitVersion needs a proper git repository to run, some build servers do not do a proper clone which can cause issues. GitVersion has a feature called [dynamic repositories](more-info/dynamic-repositories.md) which solves this by cloning the repository and working against that clone instead of the working directory.
 
 ## I don't understand what SemVer is all about
 Not a problem, we have a quick introduction to SemVer which can be a good primer to read before reading [SemVer.org](http://semver.org)
 
-Read more at [intro to semver](introToSemVer.md)
+Read more at [intro to semver](reference/intro-to-semver.md)
 
 ## I can't use the build number for NuGet
 If you have used NuGet you would notice the versions above are not compatible with NuGet. GitVersion solves this by providing *variables*.

docs/index.md

@@ -1,5 +1,5 @@
 # GitVersion Docs
-GitVersion is a tool to help you achieve *Semantic Versioning* on your project. 
+GitVersion is a tool to help you achieve *Semantic Versioning* on your project.
 
 This influences many of the decisions GitVersion has made, please read and understand this page as it will help you start using GitVersion effectively!
 
@@ -10,7 +10,7 @@ If a commit is tagged, then GitVersion will *always* use that version over any c
 ### The Semantic Version does not increment every commit
 This trips a lot of people up, by default GitVersion *does not* increment the SemVer every commit. This means that you will get multiple builds producing the *same version* of your application.
 
-Read more at [version increments](./versionIncrements.md)
+Read more at [version increments](more-info/version-increments.md)
 
 ### Version sources
 There are a number of sources GitVersion can get it's versions from, they include:
@@ -21,12 +21,12 @@ There are a number of sources GitVersion can get it's versions from, they includ
  - Track version of another branch (i.e develop tracks master, so when master increments so does develop)
  - GitVersionConfig.yaml file (i.e `next-version: 2.0.0`)
 
-Read more at [version sources](./versionSources.md)
+Read more at [version sources](more-info/version-sources.md)
 
 ## Configuration
 GitVersion v3 was rewritten to be very configuration driven rather than hardcoding git workflows into it. This has made it a lot more flexible. Configuration options can be set globally or per branch.
 
-Read more about [configuration](./configuration.md)
+Read more about [configuration](configuration.md)
 
 ## Output Variables
 We recognise that a single formatted version number does not work for all cases. A simple example is NuGet, it doesn't support SemVer 2.0 meaning that the SemVer of `1.3.5-beta.10+500` needs to be formatted as `1.3.5-beta0010` so it will sort properly.
@@ -36,4 +36,4 @@ You can just run `GitVersion.exe` in your repository to see what variables are a
 ## Exe or MSBuild Task
 There are two ways to consume GitVersion, the first is by running GitVersion.exe. The second is an MSBuild task. The MSBuild task is really easy to get up and running, simply install GitVersionTask from NuGet and it will integrate into your project and write out variables to your build server if it's running on one. The exe offers more options and works for not just .net projects.
 
-Read more about [using GitVersion](./usage.md)
+Read more about [using GitVersion](usage.md)

docs/more-info/build-server-setup/teamcity.md

@@ -7,7 +7,7 @@ In [TeamCity](https://www.jetbrains.com/teamcity/) you can create a build step a
 * **Command executable:**  `GitVersion.exe`
 * **Command parameters:** `/output buildserver /updateassemblyinfo true`
 
-Then in your build parameters simply [add a placeholder](https://github.com/Particular/GitVersion/wiki/Variables#recommended-teamcity-setup) of the GitVersion variables you would like to use.
+Then in your build parameters simply [add a placeholder](#nuget-in-teamcity) of the GitVersion variables you would like to use.
 
 GitVersion writes system parameters into TeamCity, so they will automatically be passed to your build scripts to use.
 
@@ -18,7 +18,7 @@ TeamCity has support for meta-runners which allow custom tasks. There is a GitVe
 
 ## Running inside TeamCity
 * Make sure to use **agent checkouts** (required, server checkouts do not copy the needed `.git` directory)
-  - If you want to use *checkout on server*, see [dynamic repositories](Dynamic-Repositories.md)
+  - If you want to use *checkout on server*, see [dynamic repositories](../dynamic-repositories.md)
 * For the moment you need to promote the `%teamcity.build.vcs.branch.{configurationid}%` build parameter to an environment variable with the same name for pull requests to be handled correctly
 * We update the TC build number to the GitVersion number automatically
 * We output the individual values of the GitVersion version as the build parameter: `GitVersion.*` (Eg: `GitVersion.Major`) if you need access to them in your build script

docs/reference/intro-to-semver.md

@@ -24,4 +24,4 @@ For a more complete explaination checkout [semver.org](http://semver.org) which
 ## SemVer in GitVersion
 GitVersion makes it easy to follow semantic versioning in your library by automatically calculating the next semantic version which your library/application is likely to use. In GitFlow the develop branch will bump the *minor* when master is tagged, while GitHubFlow will bump the *patch*.
 
-Because one side does not always fit all, GitVersion provides many [Variables](variables.md) for you to use which contain different variations of the version. For example SemVer will be in the format {major}.{minor}.{patch}-{tag}, but FullSemVer will also include build metadata: {major}.{minor}.{patch}-{tag}+{buildmetadata}
+Because one side does not always fit all, GitVersion provides many [Variables](../more-info/variables.md) for you to use which contain different variations of the version. For example SemVer will be in the format {major}.{minor}.{patch}-{tag}, but FullSemVer will also include build metadata: {major}.{minor}.{patch}-{tag}+{buildmetadata}

docs/usage.md

@@ -1,10 +1,10 @@
 # Usage
 There are two main ways to consume GitVersion, the first is by running GitVersion.exe. The second is an MSBuild task. The MSBuild task is really easy to get up and running, simply install GitVersionTask from NuGet and it will integrate into your project and write out variables to your build server if it's running on one. The exe offers more options and works for not just .net projects.
 
- - [A Command Line tool](usage/commandLine.md)
- - [An MSBuild Task](usage/msbuildTask.md)
- - [A NuGet Library package](#NuGet-Library)
- - [A Ruby Gem](#Gem)
+ - [A Command Line tool](#command-line)
+ - [An MSBuild Task](#msbuild-task)
+ - [A NuGet Library package](#nuget-library)
+ - [A Ruby Gem](#gem)
 
 ## Command Line
 If you want a command line version installed on your machine then you can use [Chocolatey](http://chocolatey.org) to install GitVersion