PR fixes based on comments

specification/versioning-and-stability.md

@@ -162,7 +162,7 @@ the changes can be described by schema files. The following changes can be
 currently described and are allowed:
 
 - Renaming of attributes.
-- Renaming of metrics
+- Renaming of metrics.
 - Renaming of span events.
 
 All such changes MUST be described in the OpenTelemetry
@@ -185,7 +185,7 @@ capable of describing such changes.
 #### Telemetry Stability
 
 This section defines stability requirements for telemetry produced by
-instrumentations, such as OpenTelemetry SDKs.
+OpenTelemetry instrumentations.
 
 Instrumentations, which include the Schema URL in the produced telemetry are
 allowed to change the produced telemetry after July 1, 2022 if both of the
@@ -209,10 +209,12 @@ Note that adding of new attributes, metrics, spans, span events or log records
 are considered additive, non-breaking changes and are always allowed, whether
 the instrumentation includes the Schema URL in the produced telemetry or no.
 
-OpenTelemetry SDKs SHOULD NOT produce telemetry that is not described by
-OpenTelemetry semantic conventions. If, however, this rule is broken the SDKs
-MUST NOT change such telemetry, regardless of whether they include the Schema
-URL in the produced telemetry or no.
+OpenTelemetry instrumentations SHOULD NOT produce telemetry that is not
+described by OpenTelemetry semantic conventions. If, however, this rule is
+broken the instrumentations MUST NOT change such telemetry, regardless of
+whether they include the Schema URL in the produced telemetry. Once the produced
+telemetry is added to the semantic conventions changes will be allowed as
+described above.
 
 ### Deprecated