Merge branch 'main' of https://github.com/open-telemetry/opentelemetry.io into refactor-java-api

Author: jack-berg

.cspell/en-words.txt

@@ -8,6 +8,7 @@ adservice
 alibaba
 Alolita
 APAC
+apidocs
 appdynamics
 appender
 appenders

.cspell/pt-palavras.txt

@@ -1,3 +1,5 @@
 desserializa
 autoinstrumentação
 autoconsistentes
+serialização
+verbosidade

.htmltest.yml

@@ -8,6 +8,8 @@ CheckMailto: false
 TestFilesConcurrently: true
 IgnoreDirs:
   - ^blog/(\d+/)?page/\d+
+  # TODO drop after https://github.com/open-telemetry/opentelemetry.io/issues/5267 is fixed:
+  - zh/docs/contributing/pr-checks
 IgnoreInternalURLs: # list of paths
 IgnoreURLs: # list of regexs of paths or URLs to be ignored
   - ^((/..)?/docs/languages/\w+|\.\.)/(api|examples|registry)/$

.prettierignore

@@ -7,6 +7,7 @@
 !/layouts/shortcodes
 /layouts/shortcodes/*
 !/layouts/shortcodes/docs
+/layouts/shortcodes/pt
 
 /content/ja
 /content/zh

content/en/api-docs.md

@@ -1,7 +1,6 @@
 ---
 title: API Documentation
 linkTitle: Docs
-cSpell:ignore: apidocs
 ---
 
 {{% blocks/section color="white" %}}

content/en/blog/2023/otel-arrow/index.md

@@ -24,8 +24,8 @@ repository that supports this protocol. This protocol, designed to complement
 the OTLP protocol in situations with substantial telemetry data volumes, has
 been under discussion and development for two years. It represents a
 collaborative effort between [F5](https://f5.com),
-[ServiceNow Cloud Observability](https://www.servicenow.com/products/observability.html)
-, and numerous technical leaders from the OpenTelemetry community (see
+[ServiceNow Cloud Observability](https://www.servicenow.com/products/observability.html),
+and numerous technical leaders from the OpenTelemetry community (see
 [donation](https://github.com/open-telemetry/community/issues/1332)). The
 compression benefits are significant, demonstrating a **40% improvement
 compression efficiency** for the majority of workloads and even greater

content/en/blog/2024/otel-arrow-production/index.md

@@ -20,9 +20,8 @@ is a
 that manages OTel for you in your Kubernetes cluster to make life a little
 easier. It does the following:
 
-- Manages deployment of the
-  [OpenTelemetry Collector](http://localhost:1313/docs/collector/), supported by
-  the
+- Manages deployment of the [OpenTelemetry Collector](/docs/collector/),
+  supported by the
   [`OpenTelemetryCollector`](https://github.com/open-telemetry/opentelemetry-operator?tab=readme-ov-file#getting-started)
   [custom resource (CR)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/).
 - Manages the configuration of a fleet of OpenTelemetry Collectors via
@@ -42,8 +41,7 @@ cool things, so I thought it might be helpful to share some little OTel Operator
 goodies that I’ve picked up along the way, in the form of a Q&A.
 
 Please note that this post assumes that you have some familiarity with
-OpenTelemetry, the
-[OpenTelemetry Collector](http://localhost:1313/docs/collector/), the
+OpenTelemetry, the [OpenTelemetry Collector](/docs/collector/), the
 [OpenTelemetry Operator](https://github.com/open-telemetry/opentelemetry-operator)
 (including the
 [Target Allocator](https://adri-v.medium.com/prometheus-opentelemetry-better-together-41dc637f2292)),