M contents/conver.md → contents/conver.md

@@ -209,7 +209,7 @@ Assuming that two projects "A" and "B" both follow Convergent Versioning, if "B" depends on "A", then "B" MUST be compatible exactly with one or more specific versions of "A", unless "A" is in _consolidated_ or _bedrock_ stage, in which case "B" MAY be compatible with a specific version of "A" and all subsequent versions of it, since the project cannot break compatibility once it enters _consolidated_ stage.
 
 #### Alternative Decimal Format
 
-In cases when a the canonical format is deemed inconvenient or too cryptic for end users, an alternative decimal format MAY be used. 
+In cases when the canonical format is deemed inconvenient or too cryptic for end users, an alternative decimal format MAY be used. 
 In this case, a ConVer release MUST be formatted as follows:
 
 "v" followed by the conversion of the dependability score into exactly four decimal digits, followed by "-", followed by metadata expressed via three-letters.
@@ -282,7 +282,7 @@ - If you depend on a project in _consolidated_ or _bedrock_ stage, you can specify a single version and _any version after that_ since projects in those stage cannot break compatibility.
 
 #### Can I convert a ConVer release number to SemVer?
 
-In situations where a SemVer like version is expected, such as in formats used by package managers and similar, a ConVer release can be converted into the corresponding SemVer-compliant release provides that the entire history project releases is known. 
+In situations where a SemVer like version is expected, such as in formats used by package managers and similar, a ConVer release can be converted into the corresponding SemVer-compliant release provided that the entire history project releases is known. 
 
 To determine the exact SemVer version number of a ConVer project, do the following: