More fixes to continuous-delivery

Author: asbjornu

docs/configuration.md

@@ -24,7 +24,7 @@ The global configuration options are:
 
  - **`assembly-informational-format:`** Set this to any of the available [variables](/more-info/variables) to change the value of the `AssemblyInformationalVersion` attribute. Default set to `{InformationalVersion}`. It also supports string interpolation (`{MajorMinorPatch}+{Branch}`)
 
- - **`mode:`** Sets the mode of how GitVersion should create a new version. Read more at [versioning mode](/reference/versioning-mode)
+ - **`mode:`** Sets the mode of how GitVersion should create a new version. Read more at [versioning mode](/reference/versioning-mode.md).
 
  - **`continuous-delivery-fallback-tag:`** When using `mode: ContinuousDeployment`, the value specified will be used as the pre-release tag for branches which do not have one specified. Default set to `ci`.
 

docs/reference/continuous-delivery.md

@@ -11,7 +11,8 @@ you have deployed into production.
 In essence continuous delivery means:
 
  - Your code is automatically built and tested
- - If any of the automated tests fail, the teams #1 priority is to fix the build
+ - If any of the automated tests fail, the team's #1 priority is to fix the
+   build
  - If the build is green, the application can be deployed at any time
    - Ideally the business should make that decision
    - The same artifacts which were built and tested should be deployed
@@ -27,20 +28,21 @@ GitHubFlow is a better fit for Continuous delivery, the
 feature branch will be built as a *stable* version and if the build/builds go
 green then you are free to deploy to production at any time.
 
-## How continuous delivery affects GitVersion
+## Usage
+By default, GitVersion is set up to do Continuous Delivery on all branches but
+`develop`, which is set up with [Continuous Deployment](continuous-deployment.md).
+To change the mode to Continuous Delivery, change your
+[configuration](../configuration.md) to:
+
+```yaml
+mode: ContinuousDelivery
+```
+
+## How Continuous Delivery affects GitVersion
 The thing about continuous delivery is that there will be *multiple* candidates
 to deploy to production and it is a human choice to deploy. This means that
 GitVersion will build **the same semantic version** until that version is
-deployed.
-
-GitVersion assumes Continuous Delivery by default in its
-[configuration](../configuration.md), if you want to do
-[continuous deployment](continuous-deployment.md) then just change the
-configuration setting.
-
-## Example
-In Continuous Delivery, GitVersion calculates the next version and will use that
-until it is released. For instance:
+deployed. For instance:
 
  - 1.1.0+5
  - 1.1.0+6
@@ -53,6 +55,4 @@ an external manual process.
 
 ## Resources
  - [Continuous Delivery on Uncyclopedia](https://en.wikipedia.org/wiki/Continuous_delivery)
- - [Continuous Delivery, the book](http://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912)
-
-
+ - [Continuous Delivery, the book](http://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912)