Review feedback

Author: thompson-tomo

docs/general/attribute-requirement-level.md

@@ -123,7 +123,7 @@ decision.
 ## Migrate
 
 The migrate requirement level is reserved for deprecated attributes and is
-designed to help support a allowing for a phased rollout of the stable semantic conventions.
+designed to help support achieving a phased rollout of the stable semantic conventions.
 Under no circumstances should this attribute be added to an existing instrumentation.
 
 The type of instrumentation helps to determine how the attribute should be handled, see below.
@@ -132,22 +132,22 @@ The type of instrumentation helps to determine how the attribute should be handl
 
 Should continue emitting the attribute unless:
 
-* User has set the domain ie `database` via the `OTEL_SEMCONV_STABILITY_OPT_IN` environment variable.
+* User has set the domain e.g. `database` via the `OTEL_SEMCONV_STABILITY_OPT_IN` environment variable.
 * User has excluded the attribute via explicit configuration
-* The instrumentation bumps it's major version but will continue providing security patches for
+* The instrumentation bumps its major version but will continue providing security patches for
 the previous major version for at least 6 months.
 
 Removal can occur when the major version is bumped provided previous major version will/has received 6 months of security patches from the time the replacement attribute is introduced.
 
 ### Long-term Unstable Instrumentation
 
 > [!NOTE]
-> Example's of long term unstable instrumentation, would be the OpenTelemetry Contrib packages as
+> Examples of long term unstable instrumentation, would be the OpenTelemetry Contrib packages as
 > their stability is following that of the signal they are implementing.
 
 Should stop emitting the attribute unless:
 
-* User has set the domain ie `database/dup` via the `OTEL_SEMCONV_STABILITY_OPT_IN` environment variable.
+* User has set the domain e.g. `database/dup` via the `OTEL_SEMCONV_STABILITY_OPT_IN` environment variable.
 * User has included the attribute via explicit configuration
 
 Removal can occur when the deployment level of the package changes. For instance a beta package moves to release candidate.
@@ -170,10 +170,11 @@ The type of instrumentation helps to determine how the attribute should be handl
 Should continue emitting the attribute unless:
 
 * User has excluded the attribute via explicit configuration
-* The instrumentation bumps it's major version but will continue providing security patches for
+* The instrumentation bumps its major version but will continue providing security patches for
 the previous major version for at least 6 months.
 
-Removal can occur when the major version is bumped provided previous major version will/has received 6 months of security patches from the time the replacement attribute is introduced.
+Removal can occur when the major version is bumped provided that previous major version will/has
+received 6 months of security patches from the time that the default behaviour was changed to not emit.
 
 ### Long-term Unstable Instrumentation