Corrected sp. SemVer.

Signed-off-by: dblock <[email protected]>

RELEASING.md

@@ -65,7 +65,7 @@ Backwards-incompatible changes always result in a new major version and will __n
 
 ## Versioning
 
-All distributions in this organization [follow semver](https://opensearch.org/blog/technical-post/2021/08/what-is-semver/). A user-facing breaking change can only be made in a major release. Any regression that broke semver is considered a high severity bug. 
+All distributions in this organization [follow SemVer](https://opensearch.org/blog/technical-post/2021/08/what-is-semver/). A user-facing breaking change can only be made in a major release. Any regression that broke SemVer is considered a high severity bug.
 
 ### Version Numbers
 

RESPONSIBILITIES.md

@@ -12,7 +12,7 @@
     - [Keep Dependencies up to Date](#keep-dependencies-up-to-date)
   - [Manage Roadmap](#manage-roadmap)
   - [Add Continuous Integration Checks](#add-continuous-integration-checks)
-  - [Use Semver](#use-semver)
+  - [Use SemVer](#use-semver)
   - [Release Frequently](#release-frequently)
   - [Promote Other Maintainers](#promote-other-maintainers)
   - [Describe the Repo](#describe-the-repo)
@@ -104,7 +104,7 @@ Ensure the repo highlights features that should be elevated to the project roadm
 
 Add integration checks that validate pull requests and pushes to ease the burden on Pull Request reviewers.
 
-### Use Semver
+### Use SemVer
 
 Use and enforce [semantic versioning](https://semver.org/) and do not let breaking changes be made outside of major releases.