Minor doc updates (#77)

* While this does contain legit updates to docs, it is mostly about verifying that signatures work on a different machine.
(FYI, signing does work and is verified by GH - :yeah:

Author: smaillet

README.md

@@ -64,7 +64,7 @@ of the last one released publicly.
 > (NuGet v3 can handle the full name just fine!). Thus, the lack of support in this library.
 
 ## End User Documentation
-Full documentation on the tasks is available in the project's [docs site](https://ubiquitydotnet.github.io/CSemVer.GitBuild/)
+Full documentation on the tasks are available in the project's [docs site](https://ubiquitydotnet.github.io/CSemVer.GitBuild/)
 
 ## Building the tasks
 Documentation on building and general maintenance of this repo are provided in the [Wiki](https://github.com/UbiquityDotNET/CSemVer.GitBuild/wiki).

docfx/build-tasks/index.md

@@ -49,7 +49,7 @@ components of the version match<sup>[1](#footnote_1)</sup>. This ensures that wh
 the dependent components you just built instead of the last one released publicly.
 
 ### Understanding CI builds
-Understanding CI builds is important and an complete [article](xref:understanding-ci-builds)
+Understanding CI builds is important and an seperate [article](xref:understanding-ci-builds)
 is available on the subject. An important point to understand here is that a CI build
 version number is a POST-RELEASE version that is ordered AFTER the release it is based
 on AND BEFORE the next release. That is a CI build is ordered BETWEEN releases. Though