Bump prettier from 3.5.3 to 3.6.0 (#7170)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com>
Co-authored-by: Fabrizio Ferri-Benedetti <algernon@fastmail.com>

Author: 3 people

README.md

@@ -56,11 +56,9 @@ accessing the doc, get in touch in the `#otel-comms` channel on [Slack][].
 Here is a list of community roles with current and previous members:
 
 - Approvers: [@open-telemetry/docs-approvers][]
-
   - [Michael Hausenblas](https://github.com/mhausenblas), Amazon
 
 - Maintainers: [@open-telemetry/docs-maintainers][]
-
   - [Austin Parker](https://github.com/austinlparker), Honeycomb
   - [Fabrizio Ferri-Benedetti](https://github.com/theletterf), Elastic
   - [Patrice Chalin](https://github.com/chalin), CNCF
@@ -69,11 +67,9 @@ Here is a list of community roles with current and previous members:
   - [Tiffany Hrabusa](https://github.com/tiffany76), Grafana Labs
 
 - Emeritus approvers:
-
   - [Paul Bruce](https://github.com/paulsbruce)
 
 - Emeritus maintainers:
-
   - [Steve Flanders](https://github.com/flands)
   - [Morgan McLean](https://github.com/mtwo)
   - [jparsana](https://github.com/jparsana)

content/en/blog/2024/llm-observability.md

@@ -55,7 +55,6 @@ costs. Here are the key signals to monitor:
   variety of parameters (like `temperature` and `top_p`) that can drastically
   affect both the response quality and the cost. Specific aspects to monitor
   are:
-
   - **Temperature**: Indicates the level of creativity or randomness desired
     from the model's outputs. Varying this parameter can significantly impact
     the nature of the generated content.
@@ -73,7 +72,6 @@ costs. Here are the key signals to monitor:
 
 - **Response Metadata**: Given the API-based interaction with LLMs, tracking the
   specifics of the response is key for cost management and quality assessment:
-
   - **Tokens**: Directly impacts cost and is a measure of response length and
     complexity.
 

content/en/blog/2024/year-in-review.md

@@ -59,7 +59,6 @@ Key IA updates include:
   documentation][java-reorg], introducing substantial improvements to the
   structure and clarity of the content. The bulk of this effort is reflected in
   these PRs:
-
   - [Refactor Java SDK and configuration #4966][#4966]
   - [Refactor Java instrumentation #5276][#5276]
   - [Move performance to Java agent, merge Javadoc into API page #5590][#5590]
@@ -158,13 +157,11 @@ Did you know that:
   the fourth most active contributor. Go bots!
 - The record for the PR with the most comments this year—and of all time is held
   by:
-
   - [Generative AI updates blog post (#5575)][#5575], with 150 comments!
 
   <!-- prettier-ignore -->
   A close second goes to:
   {.mt-3}
-
   - [Portuguese translation of Go instrumentation][#5380], with 146 comments
 
 [#5380]: https://github.com/open-telemetry/opentelemetry.io/pull/5380

content/en/docs/collector/building/connector/index.md

@@ -234,7 +234,6 @@ function. The `connector.NewFactory` function instantiates and returns a
     and metrics to metrics.
 
     Parameters for the `createTracesToMetricsConnector`: {.h4}
-
     - `context.Context`: the reference to the collector’s `context.Context` so
       your trace receiver can properly manage its execution context.
     - `connector.CreateSettings`: the reference to some of the collector’s

content/en/docs/collector/resiliency.md

@@ -81,7 +81,6 @@ restarts, you can enable persistent storage for the sending queue using the
   after the Collector restarts. Guarantees might not be as strong as dedicated
   message queues.
 - Configuration:
-
   1.  Define the `file_storage` extension.
   2.  Reference the storage ID in the exporter's `sending_queue` configuration.
 
@@ -132,7 +131,6 @@ backend, you can introduce a dedicated message queue like Kafka.
   failure, topic misconfiguration, data expiration) or failure of the producer
   to send to Kafka without adequate local buffering.
 - Configuration:
-
   - _Agent Collector Config (Producer):_
 
     ```yaml

content/en/docs/contributing/issues.md

@@ -41,7 +41,6 @@ One of the best ways to help make OTel docs better is to fix an existing issue.
    {{% alert title="First time contributing?" color="primary alert--first-timer" %}}
 
    Select an issue with the following labels:
-
    - [Good first issue](<{{% param _issue %}}%22good+first+issue%22>)
    - [Help wanted](<{{% param _issue %}}%3A%22help+wanted%22>)
 

content/en/docs/contributing/pull-requests.md

@@ -348,10 +348,8 @@ _Figure 4. Steps to open a PR from your fork to_
 1. From the **compare** drop-down menu, select your branch.
 1. Select **Create Pull Request**.
 1. Add a description for your pull request:
-
    - **Title** (50 characters or less): Summarize the intent of the change.
    - **Description**: Describe the change in more detail.
-
      - If there is a related GitHub issue, include `Fixes #12345` or
        `Closes #12345` in the description so that GitHub's automation closes the
        mentioned issue after merging the PR. If there are other related PRs,

content/en/docs/demo/requirements/application.md

@@ -10,23 +10,19 @@ added:
 
 1. Every supported language that has a GA Traces or Metrics SDK must have at
    least 1 service example.
-
    - Mobile support (Swift) is not an initial priority and not included in the
      above requirement.
 
 2. Application processes must be language independent.
-
    - gRPC is preferred where available and HTTP is to be used where it is not.
 
 3. Services should be architected to be modular components that can be switched
    out.
-
    - Individual services can and should be encouraged to have multiple language
      options available.
 
 4. The architecture must allow for the possible integration of platform generic
    components like a database, queue, or blob storage.
-
    - There is no requirement for a particular component type - at least 1
      generic component should be present in general.
 

content/en/docs/languages/java/getting-started.md

@@ -161,7 +161,6 @@ agent][] in a number of ways, the steps below use environment variables.
    ```
 
    {{% alert title="Important" color="warning" %}}
-
    - Replace `PATH/TO` above, with your path to the JAR.
    - Set `OTEL_METRIC_EXPORT_INTERVAL` to a value well below the default, as we
      illustrate above, **only during testing** to help you more quickly ensure

content/en/docs/languages/python/exporters.md

@@ -159,7 +159,6 @@ The available values and their corresponding settings for this environment
 variable are:
 
 - `CUMULATIVE`
-
   - `Counter`: `CUMULATIVE`
   - `UpDownCounter`: `CUMULATIVE`
   - `Histogram`: `CUMULATIVE`
@@ -168,7 +167,6 @@ variable are:
   - `ObservableGauge`: `CUMULATIVE`
 
 - `DELTA`
-
   - `Counter`: `DELTA`
   - `UpDownCounter`: `CUMULATIVE`
   - `Histogram`: `DELTA`