(doc) Fixing line lengths and settin env variable

This should hopefully allow Wyam to roll forward to using the newest
.Net Core which is installed on the machine, rather than looking for a
specific one.

Author: gep13

build/stages/publish.yml

@@ -26,3 +26,4 @@ steps:
     ENABLED_PUBLISH_TFS: $(ENABLED_PUBLISH_TFS)
     ENABLED_PUBLISH_NUGET: $(ENABLED_PUBLISH_NUGET)
     ENABLED_PUBLISH_CHOCOLATEY: $(ENABLED_PUBLISH_CHOCOLATEY)
+    DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX: 2

docs/input/docs/more-info/incrementing-per-commit.md

@@ -3,8 +3,12 @@ Order: 60
 Title: Incrementing per commit
 ---
 
-When using the continuous deployment mode (which will increment the SemVer every commit) all builds *must* have a pre-release tag, except for builds which are explicitly tagged as stable.
-Then the build metadata (which is the commit count) is promoted to the pre-release tag. Applying those rules the above commit graph would produce:
+When using the continuous deployment mode (which will increment the SemVer every
+commit) all builds *must* have a pre-release tag, except for builds which are
+explicitly tagged as stable.
+
+Then the build metadata (which is the commit count) is promoted to the
+pre-release tag. Applying those rules the above commit graph would produce:
 
 ```
 e137e9		->		1.0.0+0
@@ -17,6 +21,9 @@ d53ab6		->		2.0.0-rc.2 (If there was another commit on the release branch it wou
 b5d142		->		2.0.0-ci.0 (2.0.0 branch was merged, so master is now at 2.0.0)
 ```
 
-As you can see the versions now no longer conflict. When you want to create a stable `2.0.0` release you simply `git tag 2.0.0` then build the tag and it will produce a stable 2.0.0 package.
+As you can see the versions now no longer conflict. When you want to create a
+stable `2.0.0` release you simply `git tag 2.0.0` then build the tag and it will
+produce a stable 2.0.0 package.
 
-For more information/background on why we have come to this conclusion read [Xavier Decoster's blog post on the subject](http://www.xavierdecoster.com/semantic-versioning-auto-incremented-nuget-package-versions).
+For more information/background on why we have come to this conclusion read
+[Xavier Decoster's blog post on the subject](http://www.xavierdecoster.com/semantic-versioning-auto-incremented-nuget-package-versions).