Merge remote-tracking branch 'origin/main' into opentelemetrybot/semconv-integration-v1.31.0-dev

opentelemetrybot · opentelemetrybot · commit d0651075fbf2 · 2025-02-10T10:31:05.000Z
diff --git a/content/en/blog/2019/opentelemetry-governance-committee-explained/index.md b/content/en/blog/2019/opentelemetry-governance-committee-explained/index.md
@@ -77,4 +77,4 @@ feedback!
 _A version of this article was [originally posted][] on
 [medium.com/opentelemetry](https://medium.com/opentelemetry)._
 
-[originally posted]: {{% param canonical_url %}}
+[originally posted]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2021/auto-instrumentation-k8s.md b/content/en/blog/2021/auto-instrumentation-k8s.md
@@ -9,4 +9,4 @@ This article introduces OpenTelemetry Operator’s new feature that significantl
 simplifies instrumenting workloads deployed on Kubernetes. Read all the details
 from the [original post][].
 
-[original post]: {{% param canonical_url %}}
+[original post]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2021/collector.md b/content/en/blog/2021/collector.md
@@ -8,4 +8,4 @@ canonical_url: https://medium.com/opentelemetry/opentelemetry-collector-achieves
 The OpenTelemetry Collector has made its first GA release. For all the details,
 see the [original post][].
 
-[original post]: {{% param canonical_url %}}
+[original post]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2021/cpp.md b/content/en/blog/2021/cpp.md
@@ -9,4 +9,4 @@ OpenTelemetry C++ released its v1.0 stable version last month, which implements
 the OpenTelemetry distributed tracing specification! For all the details, see
 the [original post][].
 
-[original post]: {{% param canonical_url %}}
+[original post]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2021/gc-election.md b/content/en/blog/2021/gc-election.md
@@ -9,4 +9,4 @@ The OpenTelemetry project is excited to announce the 2021 OpenTelemetry
 Governance Committee (GC) election. For all the details, see the [original
 post][].
 
-[original post]: {{% param canonical_url %}}
+[original post]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2021/malabi.md b/content/en/blog/2021/malabi.md
@@ -10,4 +10,4 @@ cSpell:ignore: Malabi
 This article introduces you to Malabi, a new open source tool for trace-based
 testing. For all the details, see the [original post][].
 
-[original post]: {{% param canonical_url %}}
+[original post]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2021/otel-gc.md b/content/en/blog/2021/otel-gc.md
@@ -8,4 +8,4 @@ canonical_url: https://medium.com/opentelemetry/welcome-to-the-incoming-2021-ope
 The OpenTelemetry project just completed its 2021 election for the Governance
 Committee (GC). For all the details, see the [original post][].
 
-[original post]: {{% param canonical_url %}}
+[original post]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2021/python.md b/content/en/blog/2021/python.md
@@ -8,4 +8,4 @@ canonical_url: https://medium.com/opentelemetry/announcing-opentelemetry-python-
 Today, OpenTelemetry Python distributed tracing API/SDK released its 1.0
 version. For all the details, see the [original post][].
 
-[original post]: {{% param canonical_url %}}
+[original post]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2021/swift.md b/content/en/blog/2021/swift.md
@@ -8,4 +8,4 @@ canonical_url: https://medium.com/opentelemetry/opentelemetry-swift-1-0-beta-8f7
 Today, OpenTelemetry Swift distributed tracing API/SDK has released its 1.0
 version. For all the details, see the [original post][].
 
-[original post]: {{% param canonical_url %}}
+[original post]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2021/womens-day.md b/content/en/blog/2021/womens-day.md
@@ -9,4 +9,4 @@ Happy International Women’s Day! The OpenTelemetry project would like to exten
 our thanks to all our women contributors. For all the details, see the [original
 post][].
 
-[original post]: {{% param canonical_url %}}
+[original post]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2022/apisix/index.md b/content/en/blog/2022/apisix/index.md
@@ -395,4 +395,4 @@ _A version of this article was [originally posted][] on the Apache APISIX blog._
 
 [^1]: {{% param notes.docker-compose-v2 %}}
 
-[originally posted]: {{% param canonical_url %}}
+[originally posted]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2022/exponential-histograms/index.md b/content/en/blog/2022/exponential-histograms/index.md
@@ -278,8 +278,6 @@ documentation on [instrumentation][] or [github.com/open-telemetry][].
 
 _A version of this article was [originally posted][] on the New Relic blog._
 
-[originally posted]: {{% param canonical_url %}}
-
 [api]: /docs/specs/otel/metrics/api/
 [sdk]: /docs/specs/otel/metrics/sdk/
 [meter provider]: /docs/specs/otel/metrics/api/#meterprovider
@@ -304,3 +302,4 @@ _A version of this article was [originally posted][] on the New Relic blog._
 [environment variable]: /docs/specs/otel/metrics/sdk_exporters/otlp/
 [instrumentation]: /docs/languages
 [github.com/open-telemetry]: https://github.com/open-telemetry
+[originally posted]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2022/go-web-app-instrumentation/index.md b/content/en/blog/2022/go-web-app-instrumentation/index.md
@@ -415,4 +415,4 @@ find all files ready to use in our GitHub
 
 _A version of this article was [originally posted][] on the Aspecto blog._
 
-[originally posted]: {{% param canonical_url %}}
+[originally posted]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2022/k8s-metadata/index.md b/content/en/blog/2022/k8s-metadata/index.md
@@ -9,8 +9,8 @@ cSpell:ignore: k8sattributes k8sattributesprocessor k8sprocessor KUBE replicaset
 
 {{% alert title="Note" color="info" %}} The most up to date information for how
 to enhance telemetry with Kubernetes metadata can be found in the docs. See
-[Getting Started with Kubernetes](/docs/platforms/kubernetes/getting-started/) for more
-info. {{% /alert %}}
+[Getting Started with Kubernetes](/docs/platforms/kubernetes/getting-started/)
+for more info. {{% /alert %}}
 
 Attaching Kubernetes resource metadata to OpenTelemetry traces is useful to
 identify which resource (such as a pod) is failing or having performance
diff --git a/content/en/blog/2022/k8s-otel-expose/index.md b/content/en/blog/2022/k8s-otel-expose/index.md
@@ -106,8 +106,8 @@ in this setup are mentioned in brackets.
   [v1.2.1] installed.
 - A Kubernetes [v1.23.3] edge cluster to create a test cluster. Using
   [Kind](https://kind.sigs.k8s.io/) is recommended.
-- Installed [OpenTelemetry Operator](/docs/platforms/kubernetes/operator/) [v0.58.0] on
-  both ends.
+- Installed [OpenTelemetry Operator](/docs/platforms/kubernetes/operator/)
+  [v0.58.0] on both ends.
 - Installed [Jaeger Operator](https://www.jaegertracing.io/docs/1.37/operator/)
   [v1.37.0] on your public cluster.
 - Installed [cert-manager](https://cert-manager.io/) [v1.9.1] on your public
diff --git a/content/en/blog/2022/tail-sampling/index.md b/content/en/blog/2022/tail-sampling/index.md
@@ -227,4 +227,4 @@ for more information.
 
 _A version of this article was [originally posted][] on the New Relic blog._
 
-[originally posted]: {{% param canonical_url %}}
+[originally posted]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2022/troubleshooting-nodejs.md b/content/en/blog/2022/troubleshooting-nodejs.md
@@ -385,4 +385,4 @@ For a list of OpenTelemetry vendors, see [Vendors](/ecosystem/vendors/).
 
 _A version of this article was [originally posted][] on the Aspecto blog._
 
-[originally posted]: {{% param canonical_url %}}
+[originally posted]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2022/v1.0-trio.md b/content/en/blog/2022/v1.0-trio.md
@@ -10,4 +10,4 @@ new languages (Ruby, JavaScript, and Erlang/Elixir) have had their first 1.0
 releases, joining the existing GA releases from C++, Go, Java, .NET, Python and
 Swift. Read all the details from the [announcement][].
 
-[announcement]: {{% param canonical_url %}}
+[announcement]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2022/why-and-how-ebay-pivoted-to-opentelemetry/index.md b/content/en/blog/2022/why-and-how-ebay-pivoted-to-opentelemetry/index.md
@@ -21,8 +21,8 @@ ongoing issues in critical workflows that could potentially impact customer
 experience. The Observability landscape is an ever-changing one and recent
 developments in the OpenTelemetry world forced us to rethink our strategy in
 order to pivot to using it. eBay’s observability platform Sherlock.io provides
-developers and Site Reliability Engineers (SREs) with a robust set of
-cloud native offerings to observe the various applications that power the eBay
+developers and Site Reliability Engineers (SREs) with a robust set of cloud
+native offerings to observe the various applications that power the eBay
 ecosystem. Sherlock.io supports the three pillars of observability — metrics,
 logs and traces. The platform’s metric store is a clustered and sharded
 implementation of the Prometheus storage engine. We use the Metricbeat agent to
@@ -353,4 +353,4 @@ OpenTelemetry Collector community:
 
 _A version of this article was [originally posted][] on the eBay Tech Blog._
 
-[originally posted]: {{% param canonical_url %}}
+[originally posted]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2023/contributing-to-otel/index.md b/content/en/blog/2023/contributing-to-otel/index.md
@@ -145,11 +145,11 @@ Feeling a little more adventurous? Then why not join one of the other OTel
 (SIGs)? By joining a SIG, you can contribute to things like (but not limited to)
 SDK development, auto-instrumentation of libraries, the
 [OTel Collector](/docs/collector/), and the
-[OTel Operator](/docs/platforms/kubernetes/operator/). You don't even need to be a regular
-contributor. Sometimes, contributions come out of necessity. Like maybe you
-found a bug in the Collector. Why not take a stab at fixing it? Or maybe there's
-a feature that you and your team desperately need. Again, why not take a stab at
-implementing it?
+[OTel Operator](/docs/platforms/kubernetes/operator/). You don't even need to be
+a regular contributor. Sometimes, contributions come out of necessity. Like
+maybe you found a bug in the Collector. Why not take a stab at fixing it? Or
+maybe there's a feature that you and your team desperately need. Again, why not
+take a stab at implementing it?
 
 Now, before you go off writing code, you should make sure that you:
 
diff --git a/content/en/blog/2023/end-user-q-and-a-03.md b/content/en/blog/2023/end-user-q-and-a-03.md
@@ -156,8 +156,8 @@ others are still instrumented using the [legacy OpenTracing
 [using shims](/docs/migration/opentracing/).
 
 The OpenTelemetry Operator is being implemented to auto-instrument Java and .NET
-code. Among other things, the [OTel Operator](/docs/platforms/kubernetes/operator/)
-supports injecting and
+code. Among other things, the
+[OTel Operator](/docs/platforms/kubernetes/operator/) supports injecting and
 [configuring auto-instrumentation](/docs/platforms/kubernetes/operator/automatic/#configure-automatic-instrumentation)
 in .NET, Java, Python, and Node.js. Iris hopes that Go auto-instrumentation will
 be available in the near-future. To track progress of auto-instrumentation in
@@ -255,8 +255,9 @@ would be a bottleneck in terms of load and single point of failure. The team
 currently has one
 [OpenTelemetry Collector agent](/docs/collector/deployment/agent/) per
 Kubernetes cluster. The end goal is to replace those agents with the
-[OTel Operator](/docs/platforms/kubernetes/operator/) instead, which allows you to deploy
-and configure the OTel Collector and inject and configure auto-instrumentation.
+[OTel Operator](/docs/platforms/kubernetes/operator/) instead, which allows you
+to deploy and configure the OTel Collector and inject and configure
+auto-instrumentation.
 
 Everything is then sent to a central OTel Collector (i.e. an
 [OTel Collector gateway](/docs/collector/deployment/gateway/)) per data center,
diff --git a/content/en/blog/2023/exponential-histograms.md b/content/en/blog/2023/exponential-histograms.md
@@ -198,5 +198,4 @@ _A version of this article was [originally posted][] to the author's blog._
   /docs/specs/otel/metrics/sdk/#base2-exponential-bucket-histogram-aggregation
 [Why Histograms?]: ../why-histograms/
 [Histograms vs Summaries]: ../histograms-vs-summaries/
-
-[originally posted]: {{% param canonical_url %}}
+[originally posted]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2023/histograms-vs-summaries/index.md b/content/en/blog/2023/histograms-vs-summaries/index.md
@@ -110,4 +110,4 @@ Until then, here are some talks I found helpful:
 
 _A version of this article was [originally posted][] to the author's blog._
 
-[originally posted]: {{% param canonical_url %}}
+[originally posted]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2023/lambda-release.md b/content/en/blog/2023/lambda-release.md
@@ -9,8 +9,8 @@ cSpell:ignore: adot otel-faas socha
 The
 [Functions-as-a-Service (FaaS) SIG](https://docs.google.com/document/d/187XYoQcXQ9JxS_5v2wvZ0NEysaJ02xoOYNXj08pT0zc)
 is incredibly excited to announce that the release of OpenTelemetry Lambda
-layers, and associated [documentation](/docs/platforms/faas/) on how to monitor Amazon Web
-Services (AWS) Lambdas.
+layers, and associated [documentation](/docs/platforms/faas/) on how to monitor
+Amazon Web Services (AWS) Lambdas.
 
 ## OTel FaaS repackaged
 
diff --git a/content/en/blog/2023/opamp-status/index.md b/content/en/blog/2023/opamp-status/index.md
@@ -105,8 +105,8 @@ with a backlog of issues created to guide further development.
 ## OpAMP in Kubernetes
 
 In OTel we have dedicated support for Kubernetes as a compute platform via the
-[OpenTelemetry Operator for Kubernetes](/docs/platforms/kubernetes/operator/). In this
-context, we're also working on OpAMP support in Kubernetes which will be
+[OpenTelemetry Operator for Kubernetes](/docs/platforms/kubernetes/operator/).
+In this context, we're also working on OpAMP support in Kubernetes which will be
 available through a
 [bridge component](https://docs.google.com/document/d/1M8VLNe_sv1MIfu5bUR5OV_vrMBnAI7IJN-7-IAr37JY/)
 to be deployed by the OpenTelemetry Operator:
diff --git a/content/en/blog/2023/why-histograms/index.md b/content/en/blog/2023/why-histograms/index.md
@@ -93,4 +93,4 @@ avoid these subtle problems if they apply to you.
 
 _A version of this article was [originally posted][] to the author's blog._
 
-[originally posted]: {{% param canonical_url %}}
+[originally posted]: <{{% param canonical_url %}}>
diff --git a/content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md b/content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md
@@ -205,7 +205,7 @@ OTLP/JSON format, with a JSON object per line. The log records are nested in the
 
 ## Configure the Collector to ingest the OTLP/JSON logs
 
-{{< figure class="figure" src="otel-collector-otlpjson-pipeline.png" attr="View OTel Collector pipeline with OTelBin" attrlink="https://www.otelbin.io/s/69739d790cf279c203fc8efc86ad1a876a2fc01a" >}}
+{{< figure class="figure" src="otel-collector-otlpjson-pipeline.png" attr="View OTel Collector pipeline with OTelBin" attrlink=`https://www.otelbin.io/s/69739d790cf279c203fc8efc86ad1a876a2fc01a` >}}
 
 ```yaml
 # tested with otelcol-contrib v0.112.0
diff --git a/content/en/blog/2025/otel-mainframe-priorities-survey.md b/content/en/blog/2025/otel-mainframe-priorities-survey.md
@@ -63,6 +63,5 @@ OpenTelemetry on Mainframe SIG, join the conversation at
 _A version of this article was [originally posted] on the Open Mainframe Project
 blog._
 
-[originally posted]: {{% param canonical_url %}}
-
+[originally posted]: <{{% param canonical_url %}}>
 [survey]: https://www.surveymonkey.com/r/HGTD2KJ
diff --git a/content/en/docs/collector/building/receiver.md b/content/en/docs/collector/building/receiver.md
@@ -279,8 +279,8 @@ type Config struct {
 Now that you have access to the settings, you can provide any kind of validation
 needed for those values by implementing the `Validate` method according to the
 optional
-[ConfigValidator](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
-param vers %}}/component/config.go#L50) interface.
+[ConfigValidator](<https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% param vers %}}/component/config.go#L50>)
+interface.
 
 In this case, the `interval` value will be optional (we will look at generating
 default values later) but when defined should be at least 1 minute (1m) and the
@@ -330,18 +330,18 @@ func (cfg *Config) Validate() error {
 
 If you want to take a closer look at the structs and interfaces involved in the
 configuration aspects of a component, take a look at the
-[component/config.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
-param vers %}}/component/config.go) file inside the Collector's GitHub project.
+[component/config.go](<https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% param vers %}}/component/config.go>)
+file inside the Collector's GitHub project.
 
 ## Implementing the receiver.Factory interface
 
 The `tailtracer` receiver has to provide a `receiver.Factory` implementation,
 and although you will find a `receiver.Factory` interface (you can find its
 definition in the
-[receiver/receiver.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
-param vers %}}/receiver/receiver.go#L58) file within the Collector's project),
-the right way to provide the implementation is by using the functions available
-within the `go.opentelemetry.io/collector/receiver` package.
+[receiver/receiver.go](<https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% param vers %}}/receiver/receiver.go#L58>)
+file within the Collector's project), the right way to provide the
+implementation is by using the functions available within the
+`go.opentelemetry.io/collector/receiver` package.
 
 Create a file named `factory.go`:
 
@@ -595,9 +595,9 @@ func NewFactory() receiver.Factory {
 ## Implementing the receiver component
 
 All the receiver APIs are currently declared in the
-[receiver/receiver.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
-param vers %}}/receiver/receiver.go) file within the Collector's project, open
-the file and take a minute to browse through all the interfaces.
+[receiver/receiver.go](<https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% param vers %}}/receiver/receiver.go>)
+file within the Collector's project, open the file and take a minute to browse
+through all the interfaces.
 
 Notice that `receiver.Traces` (and its siblings `receiver.Metrics` and
 `receiver.Logs`) at this point in time, doesn't describe any specific methods
@@ -1393,8 +1393,7 @@ creating a trace.
 You will start with a type called `ptrace.ResourceSpans` which represents the
 resource and all the operations that it either originated or received while
 participating in a trace. You can find its definition within the
-[/pdata/internal/data/protogen/trace/v1/trace.pb.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
-param vers %}}/pdata/internal/data/protogen/trace/v1/trace.pb.go).
+[/pdata/internal/data/protogen/trace/v1/trace.pb.go](<https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% param vers %}}/pdata/internal/data/protogen/trace/v1/trace.pb.go>).
 
 `ptrace.Traces` has a method named `ResourceSpans()` which returns an instance
 of a helper type called `ptrace.ResourceSpansSlice`. The
@@ -1454,8 +1453,8 @@ pair format represented by the `pcommon.Map` type.
 
 You can check the definition of the `pcommon.Map` type and the related helper
 functions to create attribute values using the supported formats in the
-[/pdata/pcommon/map.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
-param vers %}}/pdata/pcommon/map.go) file within the Collector's GitHub project.
+[/pdata/pcommon/map.go](<https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% param vers %}}/pdata/pcommon/map.go>)
+file within the Collector's GitHub project.
 
 Key/value pairs provide a lot of flexibility to help model your `Resource` data,
 so the OTel specification has some guidelines in place to help organize and
@@ -1517,9 +1516,8 @@ convention to represent that information on its `Resource`.
 
 All the resource semantic convention attribute names and well known-values are
 kept within the
-[/semconv/v1.9.0/generated_resource.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
-param vers %}}/semconv/v1.9.0/generated_resource.go) file within the Collector's
-GitHub project.
+[/semconv/v1.9.0/generated_resource.go](<https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% param vers %}}/semconv/v1.9.0/generated_resource.go>)
+file within the Collector's GitHub project.
 
 Let's create a function to read the field values from an `BackendSystem`
 instance and write them as attributes into a `pcommon.Resource` instance. Open
diff --git a/content/en/docs/contributing/issues.md b/content/en/docs/contributing/issues.md
@@ -33,9 +33,8 @@ One of the best ways to help make OTel docs better is to fix an existing issue.
    > process.
    {.mt-3}
 
-   <!-- prettier-ignore -->
-   [good first issue]: {{% param _issue %}}%22good+first+issue%22
-   [help wanted]: {{% param _issue %}}%3A%22help+wanted%22
+   [good first issue]: <{{% param _issue %}}%22good+first+issue%22>
+   [help wanted]: <{{% param _issue %}}%3A%22help+wanted%22>
    [org]: https://github.com/open-telemetry
 
    {{% /alert %}}
diff --git a/content/en/docs/contributing/pull-requests.md b/content/en/docs/contributing/pull-requests.md
@@ -68,14 +68,14 @@ A([fa:fa-user New<br>Contributor]) --- id1[(open-telemetry/opentelemetry.io<br>G
 subgraph tasks[Changes using GitHub]
 direction TB
     0[ ] -.-
-    1[1. Edit this page] --> 2[2. Use GitHub markdown<br>editor to make changes]
-    2 --> 3[3. fill in Propose file change]
+    1[1\. Edit this page] --> 2[2\. Use GitHub markdown<br>editor to make changes]
+    2 --> 3[3\. Fill in Propose file change]
 
 end
 subgraph tasks2[ ]
 direction TB
-4[4. select Propose file change] --> 5[5. select Create pull request] --> 6[6. fill in Open a pull request]
-6 --> 7[7. select Create pull request]
+4[4\. Select Propose file change] --> 5[5\. Select Create pull request] --> 6[6\. Fill in Open a pull request]
+6 --> 7[7\. Select Create pull request]
 end
 
 id1 --> tasks --> tasks2
@@ -289,15 +289,15 @@ Figure 4 shows the steps to open a PR from your fork to
 flowchart LR
 subgraph first[ ]
 direction TB
-1[1. Go to opentelemetry.io repository] --> 2[2. Select New Pull Request]
-2 --> 3[3. Select compare across forks]
-3 --> 4[4. Select your fork from<br>head repository drop-down menu]
+1[1\. Go to opentelemetry.io repository] --> 2[2\. Select New Pull Request]
+2 --> 3[3\. Select compare across forks]
+3 --> 4[4\. Select your fork from<br>head repository drop-down menu]
 end
 subgraph second [ ]
 direction TB
-5[5. Select your branch from<br>the compare drop-down menu] --> 6[6. Select Create Pull Request]
-6 --> 7[7. Add a description<br>to your PR]
-7 --> 8[8. Select Create pull request]
+5[5\. Select your branch from<br>the compare drop-down menu] --> 6[6\. Select Create Pull Request]
+6 --> 7[7\. Add a description<br>to your PR]
+7 --> 8[8\. Select Create pull request]
 end
 
 first --> second
diff --git a/content/en/docs/contributing/style-guide.md b/content/en/docs/contributing/style-guide.md
diff --git a/content/en/docs/demo/forking.md b/content/en/docs/demo/forking.md
diff --git a/content/en/docs/languages/cpp/exporters.md b/content/en/docs/languages/cpp/exporters.md
diff --git a/content/en/docs/languages/java/intro.md b/content/en/docs/languages/java/intro.md
diff --git a/content/en/docs/languages/js/exporters.md b/content/en/docs/languages/js/exporters.md
diff --git a/content/en/docs/languages/python/exporters.md b/content/en/docs/languages/python/exporters.md
diff --git a/content/ja/docs/contributing/prerequisites.md b/content/ja/docs/contributing/prerequisites.md
diff --git a/content/ja/docs/demo/feature-flags.md b/content/ja/docs/demo/feature-flags.md
diff --git a/content/ja/docs/demo/forking.md b/content/ja/docs/demo/forking.md
diff --git a/data/registry/instrumentation-java-http4k.yml b/data/registry/instrumentation-java-http4k.yml
diff --git a/package.json b/package.json

Original file line number	Diff line number	Diff line change
`@@ -395,4 +395,4 @@ _A version of this article was [originally posted][] on the Apache APISIX blog._`
`395`	`395`
`396`	`396`	`[^1]: {{% param notes.docker-compose-v2 %}}`
`397`	`397`
`398`		`-[originally posted]: {{% param canonical_url %}}`
	`398`	`+[originally posted]: <{{% param canonical_url %}}>`
Original file line number	Diff line number	Diff line change
`@@ -415,4 +415,4 @@ find all files ready to use in our GitHub`
`415`	`415`
`416`	`416`	`_A version of this article was [originally posted][] on the Aspecto blog._`
`417`	`417`
`418`		`-[originally posted]: {{% param canonical_url %}}`
	`418`	`+[originally posted]: <{{% param canonical_url %}}>`
Original file line number	Diff line number	Diff line change
`@@ -227,4 +227,4 @@ for more information.`
`227`	`227`
`228`	`228`	`_A version of this article was [originally posted][] on the New Relic blog._`
`229`	`229`
`230`		`-[originally posted]: {{% param canonical_url %}}`
	`230`	`+[originally posted]: <{{% param canonical_url %}}>`
Original file line number	Diff line number	Diff line change
`@@ -385,4 +385,4 @@ For a list of OpenTelemetry vendors, see [Vendors](/ecosystem/vendors/).`
`385`	`385`
`386`	`386`	`_A version of this article was [originally posted][] on the Aspecto blog._`
`387`	`387`
`388`		`-[originally posted]: {{% param canonical_url %}}`
	`388`	`+[originally posted]: <{{% param canonical_url %}}>`
Original file line number	Diff line number	Diff line change
`@@ -110,4 +110,4 @@ Until then, here are some talks I found helpful:`
`110`	`110`
`111`	`111`	`_A version of this article was [originally posted][] to the author's blog._`
`112`	`112`
`113`		`-[originally posted]: {{% param canonical_url %}}`
	`113`	`+[originally posted]: <{{% param canonical_url %}}>`
Original file line number	Diff line number	Diff line change
`@@ -93,4 +93,4 @@ avoid these subtle problems if they apply to you.`
`93`	`93`
`94`	`94`	`_A version of this article was [originally posted][] to the author's blog._`
`95`	`95`
`96`		`-[originally posted]: {{% param canonical_url %}}`
	`96`	`+[originally posted]: <{{% param canonical_url %}}>`