[chore] Run prettier (#2892)

Author: thompson-tomo

.prettierignore

@@ -5,8 +5,7 @@
 /docs/**
 !/docs/cloud*
 !/docs/cloud*/**
-!/docs/registry*
-!/docs/registry*/**
+/docs/registry
 !/docs/non-normative*
 !/docs/non-normative/groups*
 !/docs/non-normative/groups/system*

docs/cicd/cicd-logs.md

@@ -17,6 +17,5 @@ When a trace context is available (cf. [CICD Spans](cicd-spans.md)) then emitted
 
 Any resources of the [CICD and VCS resource conventions][cicdres] that apply SHOULD be used.
 
-[cicdres]: /docs/resource/cicd.md (CICD and VCS resource conventions)
-
+[cicdres]: /docs/resource/cicd.md "CICD and VCS resource conventions"
 [DocumentStatus]: https://opentelemetry.io/docs/specs/otel/document-status

docs/cicd/cicd-metrics.md

@@ -52,7 +52,7 @@ When reporting host, container, runtime, and other metrics in CI/CD pipelines, i
 
 The [`cicd.pipeline.run`](/docs/resource/cicd.md#cicd-pipeline-run) entity identifies a pipeline run. Associating it with metrics inherently causes high cardinality and may increase costs with some metric storage backends. Thus, `cicd.pipeline.run` entity MUST be opt-in.
 
-[cicdres]: /docs/resource/cicd.md (CICD and VCS resource conventions)
+[cicdres]: /docs/resource/cicd.md "CICD and VCS resource conventions"
 
 ### Metric: `cicd.pipeline.run.duration`
 

docs/cicd/cicd-spans.md

@@ -20,7 +20,7 @@ The conventions described in this section are specific to Continuous Integration
 
 Any resources of the [CICD and VCS resource conventions][cicdres] that apply SHOULD be used.
 
-[cicdres]: /docs/resource/cicd.md (CICD and VCS resource conventions)
+[cicdres]: /docs/resource/cicd.md "CICD and VCS resource conventions"
 
 ### Pipeline run
 

docs/database/database-spans.md

@@ -366,12 +366,12 @@ instrumentation hooks or other sources.
 Otherwise:
 
 - When instrumenting higher-level APIs that build queries internally - for example,
-those that create a table or execute a stored procedure - instrumentations SHOULD
-generate a `db.query.summary` from available operation(s) and target(s) using the
-format described in this section.
+  those that create a table or execute a stored procedure - instrumentations SHOULD
+  generate a `db.query.summary` from available operation(s) and target(s) using the
+  format described in this section.
 
 - When instrumenting APIs that operate at the query level, instrumentations that
-support query parsing SHOULD generate a query summary based on the `db.query.text`.
+  support query parsing SHOULD generate a query summary based on the `db.query.text`.
 
 The summary SHOULD preserve the following parts of query in the order they were provided:
 
@@ -504,7 +504,6 @@ The instrumentation SHOULD allow users to pass a propagator to overwrite the glo
   ```
 
   Note that adding high cardinality comments, like `traceparent` and `tracestate`, to queries can impact the performance for some database systems, such as:
-  
   - Prepared statements in MySQL. See [this related issue](https://github.com/google/sqlcommenter/issues/284) for more details.
   - Oracle and SQL Server for both prepared and non-prepared statements.
 

docs/database/redis.md

@@ -9,6 +9,7 @@ linkTitle: Redis
 The Semantic Conventions for [Redis](https://redis.com/) extend and override the [Database Semantic Conventions](database-spans.md).
 
 ## Spans
+
 <!-- semconv span.db.redis.client -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->

docs/database/sql-server.md

@@ -181,7 +181,7 @@ Run the following command on the same physical connection as the SQL statement:
 -- The binary conversion may be done by the application or the driver.
 DECLARE @traceparent varbinary(55);
 SET @traceparent = CAST('00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01' AS varbinary(55));
-SET CONTEXT_INFO @traceparent; 
+SET CONTEXT_INFO @traceparent;
 ```
 
 Then run the query:

docs/exceptions/exceptions-spans.md

@@ -54,16 +54,16 @@ possible representations of stacktraces in various languages. The table is not
 meant to be a recommendation for any particular language, although SIGs are free
 to adopt them if they see fit.
 
-| Language   | Format                                                              |
-| ---------- | ------------------------------------------------------------------- |
-| C#         | the return value of [Exception.ToString()][csharp-stacktrace]       |
-| Elixir     | the return value of [Exception.format/3][elixir-stacktrace]         |
-| Erlang     | the return value of [`erl_error:format`][erlang-stacktrace]         |
-| Go         | the return value of [runtime.Stack][go-stacktrace]                  |
-| Java       | the contents of [Throwable.printStackTrace()][java-stacktrace]      |
-| Javascript | the return value of [error.stack][js-stacktrace] as returned by V8  |
-| Python     | the return value of [traceback.format_exc()][python-stacktrace]     |
-| Ruby       | the return value of [Exception.full_message][ruby-full-message]     |
+| Language   | Format                                                             |
+| ---------- | ------------------------------------------------------------------ |
+| C#         | the return value of [Exception.ToString()][csharp-stacktrace]      |
+| Elixir     | the return value of [Exception.format/3][elixir-stacktrace]        |
+| Erlang     | the return value of [`erl_error:format`][erlang-stacktrace]        |
+| Go         | the return value of [runtime.Stack][go-stacktrace]                 |
+| Java       | the contents of [Throwable.printStackTrace()][java-stacktrace]     |
+| Javascript | the return value of [error.stack][js-stacktrace] as returned by V8 |
+| Python     | the return value of [traceback.format_exc()][python-stacktrace]    |
+| Ruby       | the return value of [Exception.full_message][ruby-full-message]    |
 
 Backends can use the language specified methodology for generating a stacktrace
 combined with platform information from the

docs/faas/aws-lambda.md

@@ -74,9 +74,9 @@ unless stated otherwise.
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
-[faas]: faas-spans.md (FaaS trace conventions)
-[faasres]: /docs/resource/faas.md (FaaS resource conventions)
-[cloud]: /docs/resource/cloud.md (Cloud resource conventions)
+[faas]: faas-spans.md "FaaS trace conventions"
+[faasres]: /docs/resource/faas.md "FaaS resource conventions"
+[cloud]: /docs/resource/cloud.md "Cloud resource conventions"
 
 ### AWS X-Ray active tracing considerations
 
@@ -140,7 +140,7 @@ Example valid configuration when OpenTelemetry is reporting traces to another sy
 
 API Gateway allows a user to trigger a Lambda function in response to HTTP requests. It can be configured to be
 a pure proxy, where the information about the original HTTP request is passed to the Lambda function, or as a
-configuration for a REST API, in which case only a deserialized body payload is available.  In the case the API
+configuration for a REST API, in which case only a deserialized body payload is available. In the case the API
 gateway is configured to proxy to the Lambda function, the instrumented request handler will have access to all
 the information about the HTTP request in the form of an API Gateway Proxy Request Event.
 
@@ -185,7 +185,7 @@ See [compatibility](../non-normative/compatibility/aws.md#context-propagation) f
 
 ### SQS message
 
-For the SQS message span, the name MUST be `<event source> process`.  The parent MUST be the `CONSUMER` span
+For the SQS message span, the name MUST be `<event source> process`. The parent MUST be the `CONSUMER` span
 corresponding to the SQS event. The [message system attributes][] (not message attributes, which are provided by
 the user) SHOULD be checked for the key `AWSTraceHeader`. If it is present, an OpenTelemetry `Context` SHOULD be
 parsed from the value of the attribute using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/context/api-propagators.md) and
@@ -312,5 +312,4 @@ Note that [`cloud.resource_id`][cloud] currently cannot be populated as a resour
 because it is not available until function invocation.
 
 [environment variables]: https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#configuration-envvars-runtime
-
 [DocumentStatus]: https://opentelemetry.io/docs/specs/otel/document-status

docs/general/attribute-requirement-level.md

@@ -132,5 +132,4 @@ Here are several examples of expensive operations to be avoided by default:
 - reading response stream to find `http.response.body.size` when
   `Content-Length` header is not available
 
-[DocumentStatus]:
-  https://opentelemetry.io/docs/specs/otel/document-status
+[DocumentStatus]: https://opentelemetry.io/docs/specs/otel/document-status