Added usage section to continuous-deployment.

Author: asbjornu

docs/reference/continuous-deployment.md

@@ -13,15 +13,21 @@ 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)!
+### Usage
+By default GitVersion is set up to do Continuous Deployment versioning on the
+`develop` branch, but for all other branches,
+[Continuous Delivery](continuous-delivery.md) is the default mode. From version
+3 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
+`ContinuousDelivery` to `ContinuousDeployment` and the version will then
 increment each commit, giving you the features of GitVersion with continuous
-deployment.
+deployment:
+
+```yaml
+mode: ContinuousDeployment
+```
 
 [blog]: http://www.xavierdecoster.com/semantic-versioning-auto-incremented-nuget-package-versions