doc fixes

Author: thompson-tomo

docs/general/attribute-requirement-level.md

@@ -11,6 +11,14 @@
 - [Conditionally Required](#conditionally-required)
 - [Recommended](#recommended)
 - [Opt-In](#opt-in)
+- [Migrate](#migrate)
+  - [Stable Instrumentation](#stable-instrumentation)
+  - [Long-term Unstable Instrumentation](#long-term-unstable-instrumentation)
+  - [Unstable Instrumentation](#unstable-instrumentation)
+- [Remove](#remove)
+  - [Stable Instrumentation](#stable-instrumentation-1)
+  - [Long-term Unstable Instrumentation](#long-term-unstable-instrumentation-1)
+  - [Unstable Instrumentation](#unstable-instrumentation-1)
 - [Performance suggestions](#performance-suggestions)
 
 <!-- tocstop -->
@@ -115,36 +123,38 @@ 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 a allowing for 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.
 
 ### Stable Instrumentation
 
 Should continue emitting the attribute unless:
+
 * User has set the domain ie `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 previous major version for at least 6 months.
 
-Removal can occur when the major version is bumped provided previous major version will/has recieved 6 months of security patches from the time the replacement attribute is introduced.
+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 
+> Example's 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 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.
 
 ### Unstable Instrumentation
 
-Removal can occur once the new attribute is implemented, 
+Removal can occur once the new attribute is implemented,
 provided that the instrumentation does not fall into any of the other categories.
 Should that be the case the guidance for that category should be followed.
 
@@ -158,15 +168,17 @@ The type of instrumentation helps to determine how the attribute should be handl
 ### Stable Instrumentation
 
 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 previous major version for at least 6 months.
 
-Removal can occur when the major version is bumped provided previous major version will/has recieved 6 months of security patches from the time the replacement attribute is introduced.
+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
 
 Should stop emitting the attribute unless:
+
 * 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.