yaml lint issues

.chloggen/device_app_lifecycle.yaml

@@ -10,7 +10,9 @@ change_type: breaking
 component: device.app.lifecycle
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Reformat and update the `device.app.lifecycle` event description adds constraints for the possible values of the `android.state` and `ios.state`.
+note: >
+  Reformat and update the `device.app.lifecycle` event description adds constraints for the possible values of
+  the `android.state` and `ios.state`.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
 # The values here must be integers.
@@ -19,4 +21,6 @@ issues: [794]
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
-subtext: Removes the `ios.lifecycle.events` and `android.lifecycle.events` attributes from the global registry and adds constraints for the possible values of the `android.state` and `ios.state` attributes.
+subtext: >
+  Removes the `ios.lifecycle.events` and `android.lifecycle.events` attributes from the global registry and adds
+  constraints for the possible values of the `android.state` and `ios.state` attributes.

docs/mobile/events.md

@@ -9,7 +9,7 @@ events on mobile platforms. All mobile events MUST use a namespace of
 <!-- toc -->
 
 - [Lifecycle instrumentation](#lifecycle-instrumentation)
-  * [Event details](#event-details)
+  - [Event details](#event-details)
 
 <!-- tocstop -->
 

model/logs/mobile-events.yaml

@@ -1,7 +1,6 @@
 groups:
   - id: device.app.lifecycle
     stability: experimental
-    requirement_level: "required"
     type: event
     name: device.app.lifecycle
     brief: >