Updated PackageReadMe.md (#22)

* Reformatted
* Corrected typos

Author: smaillet

src/Ubiquity.NET.Versioning/PackageReadMe.md

@@ -4,16 +4,17 @@ The Ubiquity.NET.Versioning library provides types to support use of versioning
 2) [Constrained Semantic Versioning](https://csemver.org)
     - Including Continuous Integration (CI) via CSemVer-CI
 
-It is viable as a standalone package to allow validation of or comparisons to versions reported
-at runtime. (Especially from native interop that does not support package dependencies or
-versioning at runtime.)
+It is viable as a standalone package to allow validation of or comparisons to versions
+reported at runtime. (Especially from native interop that does not support package
+dependencies or versioning at runtime.)
 
 ## Example
 ``` C#
 var quad = new FileVersionQuad(SomeAPiThatRetrievesAFileVersionAsUInt64());
 // ...
 // NOTE: Since all that is available is a QUAD, which has only 1 bit for CI information,
-// there is no way to translate that to a formal CSemVer-CI. Just test ordering of the quad.
+// there is no way to translate that to a formal CSemVer-CI. Just test ordering of the
+// quad.
 if(quad > MinimumVer.FileVersion)
 {
     // Good to go!
@@ -30,31 +31,33 @@ static readonly CSemVer MinimumVer = new(1,2,3/*, ...*/);
 ## Formatting
 The library contains support for proper formatting of strings based on the rules
 of a SemVer, CSemVer, and CSemVer-CI. The formatting is done case preserving when
-possible (Some cases of CSemVer will use string substitution such that `PreRelease` would
-simply become `pre`).
+possible (Some cases of CSemVer will use string substitution such that `PreRelease`
+would simply become `pre`).
 
 ## Parsing
 The library contains support for parsing of strings based on the rules of a
 SemVer, CSemVer, and CSemVer-CI
 
 ## Ordering
-The types all support `IComparable<T>`<sup>[1](#footnote_1)</sup> and properly handle correct
-sort ordering of the versions according to the rules of SemVer (Which, CSemVer and CSemVer-CI
-follow with the exception of explicit case insensitivity for AphaNumeric IDs)
+The types all support `IComparable<T>`<sup>[1](#footnote_1)</sup> and properly handle
+correct sort ordering of the versions according to the rules of SemVer (Which, CSemVer
+and CSemVer-CI follow with the exception of explicit case insensitivity for AphaNumeric
+IDs)
 
 >[!WARNING]
-> The formal 'spec' for [CSemVer](https://csemver.org) remains mostly silent on the point
-> of the short format. See this [known issue](https://github.com/CK-Build/csemver.org/issues/2).
+> The formal 'spec' for [CSemVer](https://csemver.org) remains mostly silent on the
+> point of the short format. See this [known issue](https://github.com/CK-Build/csemver.org/issues/2).
 > Since, the existence of that form was to support NuGet V2, which is now obsolete, this
-> library does not support the short form at all. (This choice keeps documentation clarity
-> [NOT SUPPORTED] and implementation simplicity)
+> library does not support the short form at all. (This choice keeps documentation
+> clarity [NOT SUPPORTED] and implementation simplicity)
 
 ------
 <sup><a id="footnote_1">1</a></sup>Unfortunately, major repositories using SemVer have
-chosen to use different comparisons. Thus, a consumer is required to know a-priori if the
-version is compared insensitive or not. Thus all constructors accept an enum indicating
-the sort ordering to use. Additional, parsing accepts an IFormatProvider, which should
-provide an `AlphaNumeirvOrdering` value to specify the ordering. If none is provided, the
-default is used. (SemVer uses CaseSensitive comparisons, CSemVer and CSemVerCI ALWAYS use
-case insensitive) `IComparer<SemVer>` instances are available for cases where the versions
-are from mixed sources and the application wishes to order the versions.
+chosen to use different comparisons. Thus, a consumer is required to know a-priori if
+the version is compared insensitive or not. Thus all constructors accept an enum
+indicating the sort ordering to use. Additional, parsing accepts an IFormatProvider,
+which should provide an `AlphaNumeircOrdering` value to specify the ordering. If none is
+provided, the default is used. (SemVer uses CaseSensitive comparisons, CSemVer and
+CSemVerCI ALWAYS use case insensitive) `IComparer<SemVer>` instances are available for
+cases where the versions are from mixed sources and the application wishes to order the
+versions.