Apply suggestions from code review

Co-authored-by: Heitor Tashiro Sergent <[email protected]>

Author: codebien

docs/sources/k6/next/misc/versioning-and-stability-guarantees.md

@@ -40,13 +40,14 @@ A patch version contains bug fixes **that do not affect** the API.
 Quoting the [SemVer 2.0.0 specification on patch versions](https://semver.org/#spec-item-6) directly:
 
 > *Patch version Z (x.y.Z | x \> 0\) **MUST** be incremented if only backward compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.*
+
 ### Breaking change
 
 As per the [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html) specification, we define a breaking change as a change to k6 that's not backward compatible.
 
 Breaking changes imply that the consumer of k6 is expected to make some effort to adapt to the changes being made.
 
-Although it is possible that, in certain cases, the new major version containing breaking changes might be compatible with the previous version, this is not expected.
+Although it's possible that, in certain cases, the new major version containing breaking changes might be compatible with the previous version, this isn't expected.
 
 ## Release strategy
 
@@ -127,7 +128,7 @@ We guarantee the stability of metric names, types, and units. Any changes to the
 
 ### Breaking changes
 
-In a constantly evolving product, [breaking changes](#breaking-change) are sometimes unavoidable. They require that k6 users have to actively react to them because the state after it is not backward compatible with the state before.
+In a constantly evolving product, [breaking changes](#breaking-change) are sometimes unavoidable. They require that k6 users actively react to them because the state after the changes is not backward compatible with the previous state.
 
 Because we follow the [SemVer 2.0.0](https://semver.org/spec/v2.0.0.html) versioning scheme, we work under the assumption breaking changes will always lead to a new major version. When the k6 team decides to introduce a breaking change, it will automatically define the need for a new major version.