Moved content from versioing-mode to continuous-deployment to avoid duplication.

Author: asbjornu

docs/reference/continuous-deployment.md

@@ -1,6 +1,27 @@
 # Continuous Deployment
-Continuous deployment is the process of checking into master, running all the tests and if everything goes green it is automatically pushed to production.
+Continuous Deployment is the process of checking into master, running all the
+tests and if everything goes green it is automatically pushed to production.
 
-By default GitVersion is *not* setup to do this. The good news is in v3 of GitVersion this behavior is configurable!
+A good case for Continuous Deployment is when using Octopus deploy, as you
+cannot publish the same version of a package into the same feed.
 
-The default behavior for v3 and how v1 & 2 worked was that the version only incremented after a tag, which signified a release. In v3 you can simply switch the default mode in the [configuration](../configuration.md) from `continuous-delivery` to `continuous-deployment` and the version will then increment each commit, giving you the features of GitVersion with continuous deployment.
+For this mode we follow the logic in [this blog post by Xavier Decoster][blog]
+on the issues of incrementing automatically.
+
+As such we force a pre-release tag on all branches, this is fine for
+applications but can cause problems for libraries. As such this mode may or may
+not work for you, which leads us into a new mode in v4 of GitVersion:
+[Mainline Development](mainline-development.md).
+
+By default GitVersion is *not* setup to do Continuous Deployment versioning.
+The good news is in v3 of GitVersion this behavior is
+[configurable](../configuration.md)!
+
+The default behavior for v3 and how v1 & 2 worked was that the version only
+incremented after a tag, which signified a release. In v3 you can simply switch
+the default mode in the [configuration](../configuration.md) from
+`continuous-delivery` to `continuous-deployment` and the version will then
+increment each commit, giving you the features of GitVersion with continuous
+deployment.
+
+[blog]: http://www.xavierdecoster.com/semantic-versioning-auto-incremented-nuget-package-versions

docs/reference/versioning-mode.md

@@ -6,18 +6,10 @@ GitVersion has multiple modes to fit different different ways of working.
 this mode, GitVersion calculates the next version and will use that until that
 is released.
 
-## Continuous deployment
-Sometimes you just want the version to keep changing and
-[continuously deploy](/reference/continuous-deployment). A good case for this is
-when using Octopus deploy, as you cannot publish the same version of a package
-into the same feed.
-
-For this mode we followed the logic in [this blog post by Xavier Decoster][blog]
-on the issues of incrementing automatically.
-
-As such we force a pre-release tag on all branches, this is fine for
-applications but can cause problems for libraries. As such this mode may or may
-not work for you, which leads us into a new mode in v4. Mainline development.
+## Continuous Deployment
+Sometimes you just want the version to keep changing and deploy continuously.
+In this case, [Continuous Deployment](/reference/continuous-deployment) is a
+good mode to operate GitVersion by.
 
 ## Mainline development
 [Mainline development](/reference/mainline-development) works more like the
@@ -48,6 +40,4 @@ Here is an example of what mainline development looks like:
 intermitently (maybe for minor or major releases) because then GitVersion
 will start the version calculation from that point. Much like a snapshot in an
 event sourced system. We will probably add in warnings to tag when things are
-slowing down.
-
-[blog]: http://www.xavierdecoster.com/semantic-versioning-auto-incremented-nuget-package-versions
+slowing down.