feat: make yamllint happy

Author: bachgarash

.chloggen/service-criticality-attribute.yaml

@@ -22,4 +22,3 @@ issues: [2986]
 subtext: |
   This attribute enables observability platforms to implement criticality-aware tracing, monitoring,
   and sampling strategies. Supports four levels: critical, high, medium, and low.
-

areas.yaml

@@ -105,7 +105,7 @@ areas:
 
   - name: "Semantic Conventions: Resources and Entities"
     owner:
-      - name: "specs-semconv-maintainers" # TODO: Missing team user for entities?
+      - name: "specs-semconv-maintainers"  # TODO: Missing team user for entities?
         github: specs-semconv-maintainers
     project: "https://github.com/open-telemetry/community/blob/main/projects/resources-and-entities.md"
     board: "https://github.com/orgs/open-telemetry/projects/85"
@@ -158,7 +158,7 @@ areas:
 
   - name: "Semantic Conventions: FaaS"
     owner:
-      - name: "specs-semconv-maintainers" # TODO: Missing team user for faas?
+      - name: "specs-semconv-maintainers"  # TODO: Missing team user for faas?
         github: specs-semconv-maintainers
     project: "https://github.com/open-telemetry/community/blob/main/projects/completed-projects/faas.md"
     board: "N/A"

internal/tools/scripts/schema-diff/yaml/weaver.yaml

@@ -1,5 +1,5 @@
 params:
-  next_version: "next_version_placeholder" # https://github.com/open-telemetry/weaver/issues/775
+  next_version: "next_version_placeholder"  # https://github.com/open-telemetry/weaver/issues/775
 templates:
   - pattern: schema-diff.j2
     filter: >

model/service/registry.yaml

@@ -104,10 +104,10 @@ groups:
         brief: >
           The operational criticality of the service.
         note: >
-          This attribute enables classification of services based on their operational importance, 
-          allowing observability platforms to implement criticality-aware tracing, monitoring, 
-          and sampling strategies. By standardizing service criticality, organizations can implement 
-          adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize 
-          telemetry costs by reducing data from non-critical services, improve incident response by 
+          This attribute enables classification of services based on their operational importance,
+          allowing observability platforms to implement criticality-aware tracing, monitoring,
+          and sampling strategies. By standardizing service criticality, organizations can implement
+          adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize
+          telemetry costs by reducing data from non-critical services, improve incident response by
           surfacing critical service traces first, and enable better capacity planning and resource allocation.
         examples: ["critical", "high", "medium", "low"]