Update CONTRIBUTING.md

Co-Authored-By: mkaz <marcus@mkaz.com>

CONTRIBUTING.md

@@ -167,7 +167,7 @@ Maintaining dozens of npm packages is difficult—it can be tough to keep track
 The developer who proposes a change (pull request) is responsible to choose the correct version increment (`major`, `minor`, or `patch`) according to the following guidelines:
 
 - Major version X (X.y.z | X > 0) should be changed with any backward incompatible/"breaking" change. This will usually occur at the final stage of deprecating and removing of a feature.
-- Minor version Y (x.Y.z | x > 0) should be changed when you add functionality or change functionality in a backward  compatible manner. It must be incremented if any public API functionality is marked as deprecated.
+- Minor version Y (x.Y.z | x > 0) should be changed when you add functionality or change functionality in a backward compatible manner. It must be incremented if any public API functionality is marked as deprecated.
 - Patch version Z (x.y.Z | x > 0) should be incremented when you make backward  compatible bug fixes.
 
 When in doubt, refer to [Semantic Versioning specification](https://semver.org/).