diff --git a/.htmltest.yml b/.htmltest.yml
index 29acffbd7b2f..f2b736ce0646 100644
--- a/.htmltest.yml
+++ b/.htmltest.yml
@@ -75,8 +75,8 @@ IgnoreURLs: # list of regexs of paths or URLs to be ignored
   # TODO move into content/en/blog/2023/contributing-to-otel/index.md once https://github.com/open-telemetry/opentelemetry.io/issues/3889 is implemented
   - ^https://shorturl.at/vLYZ0$
 
-  # Temporary during IA rework
-  # https://github.com/open-telemetry/opentelemetry.io/issues/6222
-  - (^/docs|..)/(faas|kubernetes)\b
-  - ^../lambda-collector/ # zh/docs/faas/lambda-manual-instrument/index.html
-  - ^../../(helm|operator)\b # es/docs/kubernetes/collector/components/index.html
+  # Temporary until semconv is updated to 1.30.0+
+  - ^https://cloud.google.com/apis/design/resource_names#full_resource_name
+  - ^https://cloud.google.com/functions/docs/concepts/exec#function_scope_versus_global_scope
+  - ^https://developer.apple.com/documentation/uikit/uiapplicationdelegate#1656902
+  - ^https://docs.docker.com/registry/spec/manifest-v2-2/#example-image-manifest
diff --git a/content/en/blog/2022/k8s-metadata/index.md b/content/en/blog/2022/k8s-metadata/index.md
index 013aae54726e..8d41d0a41def 100644
--- a/content/en/blog/2022/k8s-metadata/index.md
+++ b/content/en/blog/2022/k8s-metadata/index.md
@@ -9,7 +9,7 @@ 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/kubernetes/getting-started/) for more
+[Getting Started with Kubernetes](/docs/platforms/kubernetes/getting-started/) for more
 info. {{% /alert %}}
 
 Attaching Kubernetes resource metadata to OpenTelemetry traces is useful to
diff --git a/content/en/blog/2022/k8s-otel-expose/index.md b/content/en/blog/2022/k8s-otel-expose/index.md
index 2d0eeb9ff392..6c52ad6d8099 100644
--- a/content/en/blog/2022/k8s-otel-expose/index.md
+++ b/content/en/blog/2022/k8s-otel-expose/index.md
@@ -106,7 +106,7 @@ 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/kubernetes/operator/) [v0.58.0] on
+- 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.
diff --git a/content/en/blog/2023/contributing-to-otel/index.md b/content/en/blog/2023/contributing-to-otel/index.md
index ac910e12b9f0..d870b075facf 100644
--- a/content/en/blog/2023/contributing-to-otel/index.md
+++ b/content/en/blog/2023/contributing-to-otel/index.md
@@ -145,7 +145,7 @@ 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/kubernetes/operator/). You don't even need to be a regular
+[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
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
index c9afd18d9b6a..13437b190335 100644
--- 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,9 +156,9 @@ 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/kubernetes/operator/)
+code. Among other things, the [OTel Operator](/docs/platforms/kubernetes/operator/)
 supports injecting and
-[configuring auto-instrumentation](/docs/kubernetes/operator/automatic/#configure-automatic-instrumentation)
+[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
 Go, see
@@ -255,7 +255,7 @@ 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/kubernetes/operator/) instead, which allows you to deploy
+[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
diff --git a/content/en/blog/2023/lambda-release.md b/content/en/blog/2023/lambda-release.md
index e7af6d9fdaf8..018c404cc1c2 100644
--- a/content/en/blog/2023/lambda-release.md
+++ b/content/en/blog/2023/lambda-release.md
@@ -9,7 +9,7 @@ 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/faas/) on how to monitor Amazon Web
+layers, and associated [documentation](/docs/platforms/faas/) on how to monitor Amazon Web
 Services (AWS) Lambdas.
 
 ## OTel FaaS repackaged
@@ -42,7 +42,7 @@ The FaaS SIG has addressed the above-mentioned shortcomings:
   Collector alongside auto-instrumentation layers for JavaScript, Java, and
   Python.
 - Added official community Lambda documentation to the OTel website under the
-  new [FaaS section](/docs/faas/).
+  new [FaaS section](/docs/platforms/faas/).
 
 ## What next
 
diff --git a/content/en/blog/2023/opamp-status/index.md b/content/en/blog/2023/opamp-status/index.md
index 7366d18a70ee..51847b6a1a54 100644
--- a/content/en/blog/2023/opamp-status/index.md
+++ b/content/en/blog/2023/opamp-status/index.md
@@ -105,7 +105,7 @@ 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/kubernetes/operator/). In this
+[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/)
diff --git a/content/en/blog/2024/prom-and-otel/index.md b/content/en/blog/2024/prom-and-otel/index.md
index 5d23ad407851..786ba0818edf 100644
--- a/content/en/blog/2024/prom-and-otel/index.md
+++ b/content/en/blog/2024/prom-and-otel/index.md
@@ -607,7 +607,7 @@ There are a few more Collector components you can implement to monitor
 Kubernetes, including Kubernetes-specific ones as well as general-use
 processors, such as the batch, memory limiter, and resource processors. To learn
 more, see
-[Important Components for Kubernetes](/docs/kubernetes/collector/components/).
+[Important Components for Kubernetes](/docs/platforms/kubernetes/collector/components/).
 
 After you’ve configured the components in your Collector config file, you need
 to enable them within the [pipelines](/docs/collector/configuration/#pipelines)
diff --git a/content/en/blog/2025/otel-collector-k8s-discovery.md b/content/en/blog/2025/otel-collector-k8s-discovery.md
index 09f19757b9f4..fdf5118c343d 100644
--- a/content/en/blog/2025/otel-collector-k8s-discovery.md
+++ b/content/en/blog/2025/otel-collector-k8s-discovery.md
@@ -70,9 +70,10 @@ So, what if, as a Collector user, you could simply enable automatic discovery
 and then let your cluster users tell the Collector how their workloads should be
 monitored by annotating their pods properly? That sounds awesome, and it’s not
 actually something new. OpenTelemetry already supports auto-instrumentation
-through the [Kubernetes operator](/docs/kubernetes/operator/automatic/),
-allowing users to instrument their applications automatically just by annotating
-their pods. In addition, this is a feature that other monitoring agents in the
+through the
+[Kubernetes operator](/docs/platforms/kubernetes/operator/automatic/), allowing
+users to instrument their applications automatically just by annotating their
+pods. In addition, this is a feature that other monitoring agents in the
 observability industry already support, and users are familiar with it.
 
 All this motivation led the OpenTelemetry community
diff --git a/content/en/docs/collector/installation.md b/content/en/docs/collector/installation.md
index e87c74221a62..11f20673a560 100644
--- a/content/en/docs/collector/installation.md
+++ b/content/en/docs/collector/installation.md
@@ -89,7 +89,7 @@ handling, `Service` configuration based on the OpenTelemetry configuration,
 automatic sidecar injection into deployments, and more.
 
 For guidance on how to use the Collector with Kubernetes, see
-[Kubernetes Getting Started](/docs/kubernetes/getting-started/).
+[Kubernetes Getting Started](/docs/platforms/kubernetes/getting-started/).
 
 ## Nomad
 
@@ -274,8 +274,8 @@ make otelcorecol
 
 [data collection]: /docs/concepts/components/#collector
 [deployment methods]: ../deployment/
-[opentelemetry helm charts]: /docs/kubernetes/helm/
-[opentelemetry operator]: /docs/kubernetes/operator/
+[opentelemetry helm charts]: /docs/platforms/kubernetes/helm/
+[opentelemetry operator]: /docs/platforms/kubernetes/operator/
 [getting started with opentelemetry on hashicorp nomad]:
   https://github.com/hashicorp/nomad-open-telemetry-getting-started
 [releases]:
diff --git a/content/en/docs/collector/scaling.md b/content/en/docs/collector/scaling.md
index c6335eb9ca2e..646fe18b3348 100644
--- a/content/en/docs/collector/scaling.md
+++ b/content/en/docs/collector/scaling.md
@@ -139,9 +139,9 @@ load balancer. Using a Sidecar also makes sense to avoid bringing down a crucial
 component for all pods in a node when one DaemonSet pod fails.
 
 The sidecar pattern consists in adding a container into the workload pod. The
-[OpenTelemetry Operator](/docs/kubernetes/operator/) can automatically add that
-for you. To accomplish that, you’ll need an OpenTelemetry Collector CR and
-you’ll need to annotate your PodSpec or Pod telling the operator to inject a
+[OpenTelemetry Operator](/docs/platforms/kubernetes/operator/) can automatically
+add that for you. To accomplish that, you’ll need an OpenTelemetry Collector CR
+and you’ll need to annotate your PodSpec or Pod telling the operator to inject a
 sidecar:
 
 ```yaml
@@ -244,9 +244,9 @@ Collector. For instance, each Collector could be responsible for one Kubernetes
 namespace or specific labels on the workloads.
 
 Another way of scaling the Prometheus receiver is to use the
-[Target Allocator](/docs/kubernetes/operator/target-allocator/): it’s an extra
-binary that can be deployed as part of the OpenTelemetry Operator and will
-distribute Prometheus scrape targets for a given configuration across the
+[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/): it’s
+an extra binary that can be deployed as part of the OpenTelemetry Operator and
+will distribute Prometheus scrape targets for a given configuration across the
 cluster of Collectors. You can use a Custom Resource (CR) like the following to
 make use of the Target Allocator:
 
diff --git a/content/en/docs/concepts/components.md b/content/en/docs/concepts/components.md
index 8565f89d0c27..f2e58185e988 100644
--- a/content/en/docs/concepts/components.md
+++ b/content/en/docs/concepts/components.md
@@ -126,7 +126,7 @@ The OpenTelemetry Operator is an implementation of a Kubernetes Operator. The
 operator manages the OpenTelemetry Collector and auto-instrumentation of the
 workloads using OpenTelemetry.
 
-For more information, see [K8s Operator](/docs/kubernetes/operator/).
+For more information, see [K8s Operator](/docs/platforms/kubernetes/operator/).
 
 ## Function as a Service assets
 
@@ -136,4 +136,4 @@ provides pre-built Lambda layers able to auto-instrument your application as
 well as the option of a standalone Collector Lambda layer that can be used when
 instrumenting applications manually or automatically.
 
-For more information, see [Functions as a Service](/docs/faas/).
+For more information, see [Functions as a Service](/docs/platforms/faas/).
diff --git a/content/en/docs/contributing/localization.md b/content/en/docs/contributing/localization.md
index 86370e8f4fe9..4b5bc7d616e2 100644
--- a/content/en/docs/contributing/localization.md
+++ b/content/en/docs/contributing/localization.md
@@ -140,7 +140,7 @@ command:
 
 ```console
 $ npm run check:i18n
-1       1       content/en/docs/kubernetes/_index.md - content/zh/docs/kubernetes/_index.md
+1       1       content/en/docs/platforms/kubernetes/_index.md - content/zh/docs/platforms/kubernetes/_index.md
 ...
 ```
 
@@ -158,11 +158,11 @@ of the corresponding English language pages by using the `-d` flag and providing
 the paths to your localized pages, or omit the paths to see all. For example:
 
 ```console
-$ npm run check:i18n -- -d content/zh/docs/kubernetes
-diff --git a/content/en/docs/kubernetes/_index.md b/content/en/docs/kubernetes/_index.md
+$ npm run check:i18n -- -d content/zh/docs/platforms/kubernetes
+diff --git a/content/en/docs/platforms/kubernetes/_index.md b/content/en/docs/platforms/kubernetes/_index.md
 index 3592df5d..c7980653 100644
---- a/content/en/docs/kubernetes/_index.md
-+++ b/content/en/docs/kubernetes/_index.md
+--- a/content/en/docs/platforms/kubernetes/_index.md
++++ b/content/en/docs/platforms/kubernetes/_index.md
 @@ -1,7 +1,7 @@
  ---
  title: OpenTelemetry with Kubernetes
diff --git a/content/en/docs/demo/kubernetes-deployment.md b/content/en/docs/demo/kubernetes-deployment.md
index dbaddf428ee1..d093f4402076 100644
--- a/content/en/docs/demo/kubernetes-deployment.md
+++ b/content/en/docs/demo/kubernetes-deployment.md
@@ -5,8 +5,9 @@ aliases: [kubernetes_deployment]
 cSpell:ignore: loadgen otlphttp spanmetrics
 ---
 
-We provide a [OpenTelemetry Demo Helm chart](/docs/kubernetes/helm/demo/) to
-help deploy the demo to an existing Kubernetes cluster.
+We provide a
+[OpenTelemetry Demo Helm chart](/docs/platforms/kubernetes/helm/demo/) to help
+deploy the demo to an existing Kubernetes cluster.
 
 [Helm](https://helm.sh) must be installed to use the charts. Please refer to
 Helm's [documentation](https://helm.sh/docs/) to get started.
diff --git a/content/en/docs/getting-started/ops.md b/content/en/docs/getting-started/ops.md
index ac60198d37fa..a84df094f28e 100644
--- a/content/en/docs/getting-started/ops.md
+++ b/content/en/docs/getting-started/ops.md
@@ -17,7 +17,7 @@ following:
 - [What is OpenTelemetry?](../../what-is-opentelemetry/)
 - [How can I instrument applications without touching their code?](../../concepts/instrumentation/zero-code/)
 - [How can I set up a collector?](../../collector/)
-- [How can I get automation for Kubernetes with the OpenTelemetry Operator?](../../kubernetes/operator/)
+- [How can I get automation for Kubernetes with the OpenTelemetry Operator?](../../platforms/kubernetes/operator/)
 
 If you are looking for a set of applications to try things out, you will find
 our official [OpenTelemetry demo](/ecosystem/demo/) useful.
diff --git a/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md b/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md
index 881737925fe4..0a8c27cfcc23 100644
--- a/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md
+++ b/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md
@@ -4,11 +4,12 @@ cSpell:ignore: bleh targetallocator
 ---
 
 If you’ve enabled
-[Target Allocator](/docs/kubernetes/operator/target-allocator/) service
-discovery on the [OpenTelemetry Operator](/docs/kubernetes/operator/), and the
-Target Allocator is failing to discover scrape targets, there are a few
-troubleshooting steps that you can take to help you understand what’s going on
-and restore normal operation.
+[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/)
+service discovery on the
+[OpenTelemetry Operator](/docs/platforms/kubernetes/operator/), and the Target
+Allocator is failing to discover scrape targets, there are a few troubleshooting
+steps that you can take to help you understand what’s going on and restore
+normal operation.
 
 ## Troubleshooting steps
 
diff --git a/content/en/docs/languages/_index.md b/content/en/docs/languages/_index.md
index 53cb505fbf2a..7fecb732c1e4 100644
--- a/content/en/docs/languages/_index.md
+++ b/content/en/docs/languages/_index.md
@@ -54,6 +54,6 @@ The list above is aliased to [`/api`](/api).
 
 {{% /alert %}}
 
-[zero-code]: /docs/kubernetes/operator/automatic/
+[zero-code]: /docs/platforms/kubernetes/operator/automatic/
 [instrumentation]: /docs/concepts/instrumentation/
-[otel-op]: /docs/kubernetes/operator/
+[otel-op]: /docs/platforms/kubernetes/operator/
diff --git a/content/en/docs/languages/js/serverless.md b/content/en/docs/languages/js/serverless.md
index c418b95e00c3..ad7f80b5a494 100644
--- a/content/en/docs/languages/js/serverless.md
+++ b/content/en/docs/languages/js/serverless.md
@@ -13,7 +13,7 @@ OpenTelemetry instrumentation libraries.
 {{% alert title="Note" color="info" %}}
 
 You can also automatically instrument your AWS Lambda functions by using the
-[community provided Lambda layers](/docs/faas/lambda-auto-instrument/).
+[community provided Lambda layers](/docs/platforms/faas/lambda-auto-instrument/).
 
 {{% /alert %}}
 
diff --git a/content/en/docs/platforms/faas/_index.md b/content/en/docs/platforms/faas/_index.md
index 257744b59962..7b160a91eedd 100644
--- a/content/en/docs/platforms/faas/_index.md
+++ b/content/en/docs/platforms/faas/_index.md
@@ -4,7 +4,7 @@ linkTitle: FaaS
 description: >-
   OpenTelemetry supports various methods of monitoring Function-as-a-Service
   provided by different cloud vendors
-redirects: [{ from: /docs/faas/*, to: ':splat' }] # cSpell:disable-line
+redirects: [{ from: /docs/platforms/faas/*, to: ':splat' }] # cSpell:disable-line
 ---
 
 Functions as a Service (FaaS) is an important serverless compute platform for
diff --git a/content/en/docs/platforms/kubernetes/_index.md b/content/en/docs/platforms/kubernetes/_index.md
index e5142351173f..d3e8579869b7 100644
--- a/content/en/docs/platforms/kubernetes/_index.md
+++ b/content/en/docs/platforms/kubernetes/_index.md
@@ -1,7 +1,7 @@
 ---
 title: OpenTelemetry with Kubernetes
 linkTitle: Kubernetes
-redirects: [{ from: /docs/kubernetes/*, to: ':splat' }]
+redirects: [{ from: /docs/platforms/kubernetes/*, to: ':splat' }]
 ---
 
 [Kubernetes](https://kubernetes.io/) is an open source system for automated
diff --git a/content/en/docs/platforms/kubernetes/helm/_index.md b/content/en/docs/platforms/kubernetes/helm/_index.md
index 29cc1ec86d82..23bedd3981b2 100644
--- a/content/en/docs/platforms/kubernetes/helm/_index.md
+++ b/content/en/docs/platforms/kubernetes/helm/_index.md
@@ -10,7 +10,7 @@ linkTitle: Helm Charts
 If you chose to use Helm, you can use
 [OpenTelemetry Helm Charts](https://github.com/open-telemetry/opentelemetry-helm-charts)
 to manage installs of the [OpenTelemetry Collector](/docs/collector),
-[OpenTelemetry Operator](/docs/kubernetes/operator), and
+[OpenTelemetry Operator](/docs/platforms/kubernetes/operator), and
 [OpenTelemetry Demo](/docs/demo).
 
 Add the OpenTelemetry Helm repository with:
diff --git a/content/en/docs/platforms/kubernetes/helm/collector.md b/content/en/docs/platforms/kubernetes/helm/collector.md
index 6e83e8da3e90..3e39e3abbb31 100644
--- a/content/en/docs/platforms/kubernetes/helm/collector.md
+++ b/content/en/docs/platforms/kubernetes/helm/collector.md
@@ -170,8 +170,8 @@ This feature is disabled by default. It has the following requirements in order
 to be safely enabled:
 
 - It requires the
-  [Filelog receiver](/docs/kubernetes/collector/components/#filelog-receiver) be
-  included in the Collector image, such as the
+  [Filelog receiver](/docs/platforms/kubernetes/collector/components/#filelog-receiver)
+  be included in the Collector image, such as the
   [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
 - Although not a strict requirement, it is recommended this preset be used with
   `mode=daemonset`. The `filelogreceiver` will only be able to collect logs on
@@ -238,7 +238,7 @@ Due to RBAC considerations, this feature is disabled by default. It has the
 following requirements:
 
 - It requires the
-  [Kubernetes Attributes processor](/docs/kubernetes/collector/components/#kubernetes-attributes-processor)
+  [Kubernetes Attributes processor](/docs/platforms/kubernetes/collector/components/#kubernetes-attributes-processor)
   be included in the Collector image, such as the
   [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
 
@@ -263,7 +263,7 @@ container metrics from the API server on a kubelet.
 This feature is disabled by default. It has the following requirements:
 
 - It requires the
-  [Kubeletstats receiver](/docs/kubernetes/collector/components/#kubeletstats-receiver)
+  [Kubeletstats receiver](/docs/platforms/kubernetes/collector/components/#kubeletstats-receiver)
   be included in the Collector image, such as the
   [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
 - Although not a strict requirement, it is recommended this preset be used with
@@ -293,7 +293,7 @@ collected by Kube State Metrics.
 This feature is disabled by default. It has the following requirements:
 
 - It requires the
-  [Kubernetes Cluster receiver](/docs/kubernetes/collector/components/#kubernetes-cluster-receiver)
+  [Kubernetes Cluster receiver](/docs/platforms/kubernetes/collector/components/#kubernetes-cluster-receiver)
   be included in the Collector image, such as the
   [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
 - Although not a strict requirement, it is recommended this preset be used with
@@ -321,7 +321,7 @@ The OpenTelemetry Collector can be configured to collect Kubernetes events.
 This feature is disabled by default. It has the following requirements:
 
 - It requires the
-  [Kubernetes Objects receiver](/docs/kubernetes/collector/components/#kubernetes-objects-receiver)
+  [Kubernetes Objects receiver](/docs/platforms/kubernetes/collector/components/#kubernetes-objects-receiver)
   be included in the Collector image, such as the
   [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
 - Although not a strict requirement, it is recommended this preset be used with
@@ -351,7 +351,7 @@ Kubernetes nodes.
 This feature is disabled by default. It has the following requirements:
 
 - It requires the
-  [Host Metrics receiver](/docs/kubernetes/collector/components/#host-metrics-receiver)
+  [Host Metrics receiver](/docs/platforms/kubernetes/collector/components/#host-metrics-receiver)
   be included in the Collector image, such as the
   [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
 - Although not a strict requirement, it is recommended this preset be used with
diff --git a/content/en/docs/platforms/kubernetes/helm/operator.md b/content/en/docs/platforms/kubernetes/helm/operator.md
index aed4886dfffe..ce32ed38a957 100644
--- a/content/en/docs/platforms/kubernetes/helm/operator.md
+++ b/content/en/docs/platforms/kubernetes/helm/operator.md
@@ -5,14 +5,14 @@ linkTitle: Operator Chart
 
 ## Introduction
 
-The [OpenTelemetry Operator](/docs/kubernetes/operator) is a Kubernetes operator
-that manages [OpenTelemetry Collectors](/docs/collector) and
+The [OpenTelemetry Operator](/docs/platforms/kubernetes/operator) is a
+Kubernetes operator that manages [OpenTelemetry Collectors](/docs/collector) and
 auto-instrumentation of workloads. One of the ways to install the OpenTelemetry
 Operator is via the
 [OpenTelemetry Operator Helm Chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-operator).
 
 For detailed use of the OpenTelemetry Operator visit its
-[docs](/docs/kubernetes/operator).
+[docs](/docs/platforms/kubernetes/operator).
 
 ### Installing the Chart
 
diff --git a/content/en/docs/platforms/kubernetes/operator/_index.md b/content/en/docs/platforms/kubernetes/operator/_index.md
index d853d32dd3a8..67206e7bb172 100644
--- a/content/en/docs/platforms/kubernetes/operator/_index.md
+++ b/content/en/docs/platforms/kubernetes/operator/_index.md
@@ -8,11 +8,11 @@ description:
 aliases:
   - /docs/operator
   - /docs/k8s-operator
-  - /docs/kubernetes-operator
+  - /docs/platforms/kubernetes-operator
 redirects:
   - { from: /docs/operator/*, to: ':splat' }
   - { from: /docs/k8s-operator/*, to: ':splat' }
-  - { from: /docs/kubernetes-operator/*, to: ':splat' }
+  - { from: /docs/platforms/kubernetes-operator/*, to: ':splat' }
 ---
 
 ## Introduction
diff --git a/content/en/docs/platforms/kubernetes/operator/troubleshooting/automatic.md b/content/en/docs/platforms/kubernetes/operator/troubleshooting/automatic.md
index 577a4782e8d7..9b29d78a25e3 100644
--- a/content/en/docs/platforms/kubernetes/operator/troubleshooting/automatic.md
+++ b/content/en/docs/platforms/kubernetes/operator/troubleshooting/automatic.md
@@ -3,10 +3,11 @@ title: Auto-instrumentation
 cSpell:ignore: PYTHONPATH
 ---
 
-If you're using the [OpenTelemetry Operator](/docs/kubernetes/operator)'s
-capability to inject [auto-instrumentation](/docs/kubernetes/operator/automatic)
-and you're not seeing any traces or metrics, follow these troubleshooting steps
-to understand what’s going on.
+If you're using the
+[OpenTelemetry Operator](/docs/platforms/kubernetes/operator)'s capability to
+inject [auto-instrumentation](/docs/platforms/kubernetes/operator/automatic) and
+you're not seeing any traces or metrics, follow these troubleshooting steps to
+understand what’s going on.
 
 ## Troubleshooting steps
 
@@ -322,7 +323,7 @@ namespace of your choosing.
 
 Finally, make sure that you are using the right Collector port. Normally, you
 can choose either `4317` (gRPC) or `4318` (HTTP); however, for
-[Python auto-instrumentation, you can only use `4318`](/docs/kubernetes/operator/automatic/#python).
+[Python auto-instrumentation, you can only use `4318`](/docs/platforms/kubernetes/operator/automatic/#python).
 
 ### Check configuration sources
 
diff --git a/content/en/docs/platforms/kubernetes/operator/troubleshooting/target-allocator.md b/content/en/docs/platforms/kubernetes/operator/troubleshooting/target-allocator.md
index b3556851fb50..5a7c386e8f4f 100644
--- a/content/en/docs/platforms/kubernetes/operator/troubleshooting/target-allocator.md
+++ b/content/en/docs/platforms/kubernetes/operator/troubleshooting/target-allocator.md
@@ -4,11 +4,12 @@ cSpell:ignore: bleh targetallocator
 ---
 
 If you’ve enabled
-[Target Allocator](/docs/kubernetes/operator/target-allocator/) service
-discovery on the [OpenTelemetry Operator](/docs/kubernetes/operator/), and the
-Target Allocator is failing to discover scrape targets, there are a few
-troubleshooting steps that you can take to help you understand what’s going on
-and restore normal operation.
+[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/)
+service discovery on the
+[OpenTelemetry Operator](/docs/platforms/kubernetes/operator/), and the Target
+Allocator is failing to discover scrape targets, there are a few troubleshooting
+steps that you can take to help you understand what’s going on and restore
+normal operation.
 
 ## Troubleshooting steps
 
diff --git a/content/en/docs/what-is-opentelemetry.md b/content/en/docs/what-is-opentelemetry.md
index bcb28175bbed..8db26af2c6f0 100644
--- a/content/en/docs/what-is-opentelemetry.md
+++ b/content/en/docs/what-is-opentelemetry.md
@@ -77,9 +77,9 @@ OpenTelemetry consists of the following major components:
 - The [OpenTelemetry Collector](/docs/collector), a proxy that receives,
   processes, and exports telemetry data
 - Various other tools, such as the
-  [OpenTelemetry Operator for Kubernetes](/docs/kubernetes/operator/),
-  [OpenTelemetry Helm Charts](/docs/kubernetes/helm/), and
-  [community assets for FaaS](/docs/faas/)
+  [OpenTelemetry Operator for Kubernetes](/docs/platforms/kubernetes/operator/),
+  [OpenTelemetry Helm Charts](/docs/platforms/kubernetes/helm/), and
+  [community assets for FaaS](/docs/platforms/faas/)
 
 OpenTelemetry is used by a wide variety of
 [libraries, services and apps](/ecosystem/integrations/) that have OpenTelemetry
diff --git a/content/en/docs/zero-code/_index.md b/content/en/docs/zero-code/_index.md
index b7859e14fd5c..b13df00b1541 100644
--- a/content/en/docs/zero-code/_index.md
+++ b/content/en/docs/zero-code/_index.md
@@ -10,6 +10,7 @@ If you are using Kubernetes, you can use the [OpenTelemetry Operator for
 Kubernetes][otel-op] to [inject zero-code instrumentation] for .NET, Java,
 Node.js, Python, or Go into your application.
 
-[inject zero-code instrumentation]: /docs/kubernetes/operator/automatic/
+[inject zero-code instrumentation]:
+  /docs/platforms/kubernetes/operator/automatic/
 [zero-code instrumentation]: /docs/concepts/instrumentation/zero-code/
-[otel-op]: /docs/kubernetes/operator/
+[otel-op]: /docs/platforms/kubernetes/operator/
diff --git a/content/en/docs/zero-code/net/_index.md b/content/en/docs/zero-code/net/_index.md
index b34f15a3eb58..e3ca6b329b3f 100644
--- a/content/en/docs/zero-code/net/_index.md
+++ b/content/en/docs/zero-code/net/_index.md
@@ -230,7 +230,7 @@ For an example of Docker container instrumentation, see
 on GitHub.
 
 You can also use the
-[OpenTelemetry Operator for Kubernetes](/docs/kubernetes/operator/).
+[OpenTelemetry Operator for Kubernetes](/docs/platforms/kubernetes/operator/).
 
 ## Configuring the agent
 
diff --git a/content/en/docs/zero-code/python/operator.md b/content/en/docs/zero-code/python/operator.md
index ac784f621461..98b592602dd4 100644
--- a/content/en/docs/zero-code/python/operator.md
+++ b/content/en/docs/zero-code/python/operator.md
@@ -10,7 +10,7 @@ If you run your Python service in Kubernetes, you can take advantage of the
 [OpenTelemetry Operator](https://github.com/open-telemetry/opentelemetry-operator)
 to inject auto-instrumentation without having to modify each of your services
 directly.
-[See the OpenTelemetry Operator Auto-instrumentation docs for more details.](/docs/kubernetes/operator/automatic/)
+[See the OpenTelemetry Operator Auto-instrumentation docs for more details.](/docs/platforms/kubernetes/operator/automatic/)
 
 ### Python-specific topics
 
@@ -29,7 +29,7 @@ Python auto-instrumentation.
 
 Since operator v0.113.0 it is possible to build an image with both glibc and
 musl based auto-instrumentation and
-[configure it at runtime](/docs/kubernetes/operator/automatic/#annotations-python-musl).
+[configure it at runtime](/docs/platforms/kubernetes/operator/automatic/#annotations-python-musl).
 
 #### Django applications
 
diff --git a/content/es/docs/concepts/components.md b/content/es/docs/concepts/components.md
index 9a548119bfb6..99ce156e92b7 100644
--- a/content/es/docs/concepts/components.md
+++ b/content/es/docs/concepts/components.md
@@ -132,7 +132,8 @@ El Operador de OpenTelemetry es una implementación de un Operador de Kubernetes
 El operador gestiona el Collector de OpenTelemetry y la auto-instrumentación de
 las aplicaciones usando OpenTelemetry.
 
-Para más información, consulta el [Operador K8s](/docs/kubernetes/operator/).
+Para más información, consulta el
+[Operador K8s](/docs/platforms/kubernetes/operator/).
 
 ## Elementos de Función como Servicio
 
@@ -143,4 +144,4 @@ auto-instrumentar tu aplicación, así como la opción de una capa Lambda de
 Collector independiente que puede usarse al instrumentar aplicaciones manual o
 automáticamente.
 
-Para más información, consulta [Funciones como Servicio](/docs/faas/).
+Para más información, consulta [Funciones como Servicio](/docs/platforms/faas/).
diff --git a/content/es/docs/getting-started/ops.md b/content/es/docs/getting-started/ops.md
index 5253eb75a729..b8e7317315fb 100644
--- a/content/es/docs/getting-started/ops.md
+++ b/content/es/docs/getting-started/ops.md
@@ -17,7 +17,7 @@ las aplicaciones sin tocar su código, te recomendamos aprender lo siguiente:
 - [¿Qué es OpenTelemetry?](../../what-is-opentelemetry/)
 - [¿Cómo puedo instrumentar aplicaciones sin tocar su código?](../../concepts/instrumentation/zero-code/)
 - [¿Cómo puedo configurar un colector?](../../collector/)
-- [¿Cómo puedo automatizar Kubernetes con el OpenTelemetry Operator?](../../kubernetes/operator/)
+- [¿Cómo puedo automatizar Kubernetes con el OpenTelemetry Operator?](../../platforms/kubernetes/operator/)
 
 Si estás buscando un conjunto de aplicaciones para hacer pruebas, encontrarás
 útil nuestra [demo oficial de OpenTelemetry](/ecosystem/demo/).
diff --git a/content/es/docs/kubernetes/collector/components.md b/content/es/docs/kubernetes/collector/components.md
index 9450df8925f5..a38ebbf7c110 100644
--- a/content/es/docs/kubernetes/collector/components.md
+++ b/content/es/docs/kubernetes/collector/components.md
@@ -1,7 +1,7 @@
 ---
 title: Componentes clave para Kubernetes
 linkTitle: Componentes
-default_lang_commit: 3815d1481fe753df10ea3dc26cbe64dba0230579
+default_lang_commit: 3815d1481fe753df10ea3dc26cbe64dba0230579 # with patched links
 # prettier-ignore
 cSpell:ignore: alertmanagers asignador containerd crio filelog gotime horizontalpodautoscalers hostfs hostmetrics iostream k8sattributes kubelet kubeletstats logtag paginación replicasets replicationcontrollers resourcequotas statefulsets varlibdockercontainers varlogpods
 ---
@@ -59,8 +59,9 @@ predeterminada, los datos que pasan por el procesador se asocian a un pod a
 través de la dirección IP de la solicitud entrante, pero se pueden configurar
 diferentes reglas. Dado que el procesador utiliza la API de Kubernetes, requiere
 permisos especiales (consulta el ejemplo a continuación). Si está utilizando el
-[gráfico Helm de OpenTelemetry Collector](../../helm/collector/), puede usar el
-[ajuste preestablecido `kubernetesAttributes`](../../helm/collector/#kubernetes-attributes-preset)
+[gráfico Helm de OpenTelemetry Collector](../../../platforms/kubernetes/helm/collector/),
+puede usar el
+[ajuste preestablecido `kubernetesAttributes`](../../../platforms/kubernetes/helm/collector/#kubernetes-attributes-preset)
 para comenzar.
 
 Los siguientes atributos se agregan de forma predeterminada:
@@ -200,10 +201,10 @@ nodo.
 Existen diferentes métodos de autenticación, pero normalmente una cuenta de
 servicio se utiliza. La cuenta de servicio también necesitará los permisos
 adecuados para extraer datos de el Kubelet (ver más abajo). Si estás usando el
-[Gráfico de timón de OpenTelemetry Collector](../../helm/collector/) puede
-utilizar el
-[`kubeletMetrics` preset](../../helm/collector/#kubelet-metrics-preset) para
-empezar.
+[Gráfico de timón de OpenTelemetry Collector](../../../platforms/kubernetes/helm/collector/)
+puede utilizar el
+[`kubeletMetrics` preset](../../../platforms/kubernetes/helm/collector/#kubelet-metrics-preset)
+para empezar.
 
 De forma predeterminada, se recopilan métricas para pods y nodos, pero también
 se puede configurar el receptor para recopilar las métricas del contenedor y el
@@ -279,9 +280,9 @@ El receptor de Filelog está compuesto por operadores que se encadenan entre sí
 para procesar un registro. Cada operador realiza una responsabilidad simple,
 como analizar una marca de tiempo o JSON. Configurar un receptor de Filelog no
 es trivial. Si está usando el
-[diagrama de Helm de OpenTelemetry Collector](../../helm/collector/) puede usar
-el
-[ajuste preestablecido `logsCollection`](../../helm/collector/#logs-collection-preset)
+[diagrama de Helm de OpenTelemetry Collector](../../../platforms/kubernetes/helm/collector/)
+puede usar el
+[ajuste preestablecido `logsCollection`](../../../platforms/kubernetes/helm/collector/#logs-collection-preset)
 para comenzar.
 
 Dado que los logs de Kubernetes normalmente se ajustan a un conjunto de formatos
@@ -431,8 +432,10 @@ Existen diferentes métodos de autenticación, pero normalmente se utiliza una
 cuenta de servicio. La cuenta de servicio también necesita los permisos
 adecuados para extraer datos del servidor API de Kubernetes (consulte a
 continuación). Si estás utilizando el gráfico Helm de OpenTelemetry Collector
-(../../helm/collector/), puedes utilizar el valor preestablecido
-[`clusterMetrics`](../../helm/collector/#cluster-metrics-preset) para comenzar.
+(../../../platforms/kubernetes/helm/collector/), puedes utilizar el valor
+preestablecido
+[`clusterMetrics`](../../../platforms/kubernetes/helm/collector/#cluster-metrics-preset)
+para comenzar.
 
 Para las condiciones del nodo, el receptor solo recopila `Ready` de manera
 predeterminada, pero puede configurarse para recopilar más. El receptor también
@@ -561,9 +564,9 @@ receptor en todo el clúster para recopilar todos los datos.
 Actualmente, solo se puede usar una cuenta de servicio para la autenticación. La
 cuenta de servicio también necesita los permisos adecuados para extraer datos
 del servidor de API de Kubernetes (ver a continuación). Si estás usando el
-[gráfico Helm de OpenTelemetry Collector](../../helm/collector/) y desea
-ingresar eventos, puedes usar el
-[ajuste preestablecido `kubernetesEvents`](../../helm/collector/#cluster-metrics-preset)
+[gráfico Helm de OpenTelemetry Collector](../../../platforms/kubernetes/helm/collector/)
+y desea ingresar eventos, puedes usar el
+[ajuste preestablecido `kubernetesEvents`](../../../platforms/kubernetes/helm/collector/#cluster-metrics-preset)
 para comenzar.
 
 Para los objetos que se configuran para extraer, el receptor usa la API de
@@ -725,9 +728,9 @@ usarlo:
 
 Para facilitar la configuración del receptor Prometheus, el operador
 OpenTelemetry incluye un componente opcional llamado
-[Asignador de destino](../../operator/target-allocator). Este componente se
-puede utilizar para indicarle a un recopilador qué puntos finales de Prometheus
-debe rastrear.
+[Asignador de destino](../../../platforms/kubernetes/operator/target-allocator).
+Este componente se puede utilizar para indicarle a un recopilador qué puntos
+finales de Prometheus debe rastrear.
 
 Para obtener más información sobre el diseño del receptor, consulta
 [Diseño](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/prometheusreceiver/DESIGN.md).
@@ -747,8 +750,9 @@ ambos, puede que valga la pena deshabilitar estas métricas duplicadas.
 
 En Kubernetes, el receptor necesita acceso al volumen `hostfs` para funcionar
 correctamente. Si estás utilizando el
-[gráfico Helm de OpenTelemetry Collector](../../helm/collector/), usa el
-[ajuste preestablecido `hostMetrics`](../../helm/collector/#host-metrics-preset)
+[gráfico Helm de OpenTelemetry Collector](../../../platforms/kubernetes/helm/collector/),
+usa el
+[ajuste preestablecido `hostMetrics`](../../../platforms/kubernetes/helm/collector/#host-metrics-preset)
 para comenzar.
 
 Los scrapers disponibles son:
diff --git a/content/es/docs/languages/_index.md b/content/es/docs/languages/_index.md
index 7a361239f385..1d7dd7230d09 100644
--- a/content/es/docs/languages/_index.md
+++ b/content/es/docs/languages/_index.md
@@ -55,6 +55,6 @@ Puedes encontrar una lista de referencias de API disponibles en </api-docs>.
 
 {{% /alert %}}
 
-[zero-code]: /docs/kubernetes/operator/automatic/
+[zero-code]: /docs/platforms/kubernetes/operator/automatic/
 [instrumentación]: /docs/concepts/instrumentation/
-[otel-op]: /docs/kubernetes/operator/
+[otel-op]: /docs/platforms/kubernetes/operator/
diff --git a/content/es/docs/what-is-opentelemetry.md b/content/es/docs/what-is-opentelemetry.md
index a5927d4e5dcc..7b3a96e5c204 100644
--- a/content/es/docs/what-is-opentelemetry.md
+++ b/content/es/docs/what-is-opentelemetry.md
@@ -80,9 +80,9 @@ OpenTelemetry consta de los siguientes componentes principales:
 - El [OpenTelemetry Collector](/docs/collector), un proxy que recibe, procesa y
   exporta datos de telemetría.
 - Numerosas herramientas, como el
-  [OpenTelemetry Operator para Kubernetes](/docs/kubernetes/operator/),
-  [OpenTelemetry Helm Charts](/docs/kubernetes/helm/) y
-  [recursos para la comunidad para FaaS](/docs/faas/).
+  [OpenTelemetry Operator para Kubernetes](/docs/platforms/kubernetes/operator/),
+  [OpenTelemetry Helm Charts](/docs/platforms/kubernetes/helm/) y
+  [recursos para la comunidad para FaaS](/docs/platforms/faas/).
 
 OpenTelemetry es utilizado por una amplia variedad de
 [librerías, servicios y aplicaciones](/ecosystem/integrations/) que integran
diff --git a/content/fr/docs/what-is-opentelemetry.md b/content/fr/docs/what-is-opentelemetry.md
index 8e644cf7683b..cb90a4e6b67f 100644
--- a/content/fr/docs/what-is-opentelemetry.md
+++ b/content/fr/docs/what-is-opentelemetry.md
@@ -81,9 +81,9 @@ OpenTelemetry se compose des principaux composants suivants :
 - Le [Collector OpenTelemetry](/docs/collector), un proxy qui reçoit, modifie et
   exporte les données de télémétrie
 - Divers autres outils, tels que
-  l'[Opérateur Kubernetes pour OpenTelemetry](/docs/kubernetes/operator/), les
-  [Helm Charts pour OpenTelemetry](/docs/kubernetes/helm/) et des
-  [ressources communautaires pour les FaaS](/docs/faas/)
+  l'[Opérateur Kubernetes pour OpenTelemetry](/docs/platforms/kubernetes/operator/),
+  les [Helm Charts pour OpenTelemetry](/docs/platforms/kubernetes/helm/) et des
+  [ressources communautaires pour les FaaS](/docs/platforms/faas/)
 
 OpenTelemetry est utilisé par une grande variété de
 [bibliothèques, services et applications](/ecosystem/integrations/) qui
diff --git a/content/ja/docs/collector/installation.md b/content/ja/docs/collector/installation.md
index 1cf725bbc4f4..0dc0b8331873 100644
--- a/content/ja/docs/collector/installation.md
+++ b/content/ja/docs/collector/installation.md
@@ -80,7 +80,7 @@ kubectl apply -f https://raw.githubusercontent.com/open-telemetry/opentelemetry-
 また、[OpenTelemetry Operator][] を使って、OpenTelemetryコレクターインスタンスのプロビジョニングとメンテナンスを行えます。
 この機能には、自動アップグレード処理、OpenTelemetry コンフィギュレーションに基づいた `Service` コンフィギュレーション、デプロイメントへの自動サイドカーインジェクションなどがあります。
 
-Kubernetesでコレクターを使用する方法については、[Kubernetesで始める](/docs/kubernetes/getting-started/)を参照してください。
+Kubernetesでコレクターを使用する方法については、[Kubernetesで始める](/docs/platforms/kubernetes/getting-started/)を参照してください。
 
 ## Nomad
 
@@ -289,7 +289,7 @@ make otelcorecol
 
 [data collection]: /docs/concepts/components/#collector
 [deployment methods]: ../deployment/
-[opentelemetry helm charts]: /docs/kubernetes/helm/
-[opentelemetry operator]: /docs/kubernetes/operator/
+[opentelemetry helm charts]: /docs/platforms/kubernetes/helm/
+[opentelemetry operator]: /docs/platforms/kubernetes/operator/
 [getting started with opentelemetry on hashicorp nomad]: https://github.com/hashicorp/nomad-open-telemetry-getting-started
 [releases]: https://github.com/open-telemetry/opentelemetry-collector-releases/releases
diff --git a/content/ja/docs/concepts/components.md b/content/ja/docs/concepts/components.md
index 2c56a4fc9165..0a4ae521433e 100644
--- a/content/ja/docs/concepts/components.md
+++ b/content/ja/docs/concepts/components.md
@@ -99,11 +99,11 @@ OpenTelemetryの各言語固有の実装は、いくつかの[ヘッドサンプ
 OpenTelemetryオペレーターはKubernetesオペレーターの実装です。
 オペレーターはOpenTelemetryコレクターを管理し、OpenTelemetryを使用してワークロードの自動計装を行います。
 
-詳細は、[K8sオペレーター](/docs/kubernetes/operator/)のページを参照してください。
+詳細は、[K8sオペレーター](/docs/platforms/kubernetes/operator/)のページを参照してください。
 
 ## Function as a Serviceアセット {#function-as-a-service-assets}
 
 OpenTelemetryは、さまざまなクラウドベンダーが提供する Function-as-a-Service を監視するさまざまな方法をサポートしています。
 OpenTelemetryコミュニティは、現在、アプリケーションを自動計装できるビルド済みのLambdaレイヤーと、アプリケーションを手動または自動で計装する際に使用できるスタンドアロンのコレクターLambdaレイヤーのオプションを提供しています。
 
-詳細は、[Functions as a Service](/docs/faas/)のページを参照してください。
+詳細は、[Functions as a Service](/docs/platforms/faas/)のページを参照してください。
diff --git a/content/ja/docs/getting-started/ops.md b/content/ja/docs/getting-started/ops.md
index cb6d541e6a7c..7c51817e1d74 100644
--- a/content/ja/docs/getting-started/ops.md
+++ b/content/ja/docs/getting-started/ops.md
@@ -16,6 +16,6 @@ OpenTelemetryが役に立ちます！
 - [OpenTelemetryとは](../../what-is-opentelemetry/)
 - [アプリケーションのコードに触れることなく計装する方法](../../concepts/instrumentation/zero-code/)
 - [コレクターの設定方法](../../collector/)
-- [OpenTelemetry Operatorを使ってKubernetes向けの自動化をする方法](../../kubernetes/operator/)
+- [OpenTelemetry Operatorを使ってKubernetes向けの自動化をする方法](../../platforms/kubernetes/operator/)
 
 もしあなたが、試行錯誤のためのアプリケーション一式を探しているなら、公式の[OpenTelemetryデモ](/ecosystem/demo/)が役に立つでしょう。
diff --git a/content/ja/docs/what-is-opentelemetry.md b/content/ja/docs/what-is-opentelemetry.md
index c226e1345429..e18158b4dd37 100644
--- a/content/ja/docs/what-is-opentelemetry.md
+++ b/content/ja/docs/what-is-opentelemetry.md
@@ -48,7 +48,7 @@ OpenTelemetryは以下の主要コンポーネントで構成されています
 - 共通ライブラリやフレームワークの計装を実装する[ライブラリエコシステム](/ecosystem/registry)
 - コード変更の必要なくテレメトリーデータを生成する自動計装コンポーネント
 - テレメトリーデータの受信、処理、送信のためのプロキシとなる[OpenTelemetryコレクター](/docs/collector)
-- [OpenTelemetry Operator for Kubernetes](/docs/kubernetes/operator/)、[OpenTelemetry Helm Charts](/docs/kubernetes/helm/)、[FaaS向けコミュニティアセット](/docs/faas/)といったその他さまざまなツール
+- [OpenTelemetry Operator for Kubernetes](/docs/platforms/kubernetes/operator/)、[OpenTelemetry Helm Charts](/docs/platforms/kubernetes/helm/)、[FaaS向けコミュニティアセット](/docs/platforms/faas/)といったその他さまざまなツール
 
 OpenTelemetryは、デフォルトでオブザーバビリティを提供するために、OpenTelemetryが統合されたさまざまな[ライブラリ、サービス、アプリ](/ecosystem/integrations/)によって使用されています。
 
diff --git a/content/pt/docs/concepts/components.md b/content/pt/docs/concepts/components.md
index 669d7de84aaa..cacacd5811a2 100644
--- a/content/pt/docs/concepts/components.md
+++ b/content/pt/docs/concepts/components.md
@@ -129,7 +129,7 @@ gerencia o OpenTelemetry Collector e a instrumentação sem código das cargas d
 trabalho que utilizam OpenTelemetry.
 
 Para mais informações, consulte
-[Kubernetes Operator](/docs/kubernetes/operator/).
+[Kubernetes Operator](/docs/platforms/kubernetes/operator/).
 
 ## Função como Serviço {#function-as-a-service-assets}
 
@@ -140,4 +140,4 @@ instrumentação sem código na sua aplicação, bem como a opção de uma camad
 Lambda do Coletor independente, que pode ser usada ao instrumentar aplicações
 manualmente ou automaticamente.
 
-Para mais informações, consulte [Função como Serviço](/docs/faas/).
+Para mais informações, consulte [Função como Serviço](/docs/platforms/faas/).
diff --git a/content/pt/docs/getting-started/ops.md b/content/pt/docs/getting-started/ops.md
index 43541f0ffd15..fc23dcffc474 100644
--- a/content/pt/docs/getting-started/ops.md
+++ b/content/pt/docs/getting-started/ops.md
@@ -18,7 +18,7 @@ seguinte:
 - [O que é o OpenTelemetry?](../../what-is-opentelemetry/)
 - [Como instrumentar aplicativos sem alterar seu código?](../../concepts/instrumentation/zero-code/)
 - [Como configurar um Collector?](../../collector/)
-- [Como ter automação no Kubernetes com o OpenTelemetry Operator?](../../kubernetes/operator/)
+- [Como ter automação no Kubernetes com o OpenTelemetry Operator?](../../platforms/kubernetes/operator/)
 
 Se você está procurando um conjunto de aplicativos para experimentar, você
 encontrará nossa [demonstração oficial do OpenTelemetry](/ecosystem/demo/) útil.
diff --git a/content/pt/docs/languages/_index.md b/content/pt/docs/languages/_index.md
index 2ff6a33cf783..392405a9e095 100644
--- a/content/pt/docs/languages/_index.md
+++ b/content/pt/docs/languages/_index.md
@@ -55,6 +55,6 @@ A lista acima é um alias para [`/api`](/api).
 
 {{% /alert %}}
 
-[implementação automática]: /docs/kubernetes/operator/automatic/
+[implementação automática]: /docs/platforms/kubernetes/operator/automatic/
 [instrumentação]: /docs/concepts/instrumentation/
-[otel-op]: /docs/kubernetes/operator/
+[otel-op]: /docs/platforms/kubernetes/operator/
diff --git a/content/pt/docs/what-is-opentelemetry.md b/content/pt/docs/what-is-opentelemetry.md
index c0146ba55e9b..b7bf2f83c2e9 100644
--- a/content/pt/docs/what-is-opentelemetry.md
+++ b/content/pt/docs/what-is-opentelemetry.md
@@ -79,9 +79,9 @@ O OpenTelemetry consiste dos seguintes componentes:
 - O [OpenTelemetry Collector](/docs/collector), um _proxy_ intermediário que
   recebe, processa e exporta dados de telemetria
 - Várias outras ferramentas, como o
-  [OpenTelemetry Operator para Kubernetes](/docs/kubernetes/operator/),
-  [OpenTelemetry Helm Charts](/docs/kubernetes/helm/), e
-  [recursos da comunidade para FaaS](/docs/faas/)
+  [OpenTelemetry Operator para Kubernetes](/docs/platforms/kubernetes/operator/),
+  [OpenTelemetry Helm Charts](/docs/platforms/kubernetes/helm/), e
+  [recursos da comunidade para FaaS](/docs/platforms/faas/)
 
 O OpenTelemetry é utilizado por diversas
 [bibliotecas, serviços e aplicativos](/ecosystem/integrations/) que o integram
diff --git a/content/zh/docs/concepts/components.md b/content/zh/docs/concepts/components.md
index 01dfc25a8885..17668e6c6606 100644
--- a/content/zh/docs/concepts/components.md
+++ b/content/zh/docs/concepts/components.md
@@ -100,7 +100,7 @@ OpenTelemetry 的特定语言实现提供了从环境变量 `OTEL_RESOURCE_ATTRI
 OpenTelemetry Operator 是 Kubernetes Operator 的一种实现。
 Operator 管理 OpenTelemetry Collector 以及使用 OpenTelemetry 对工作负载进行自动插桩。
 
-更多信息，请参见 [K8s Operator](/docs/kubernetes/operator/)。
+更多信息，请参见 [K8s Operator](/docs/platforms/kubernetes/operator/)。
 
 ## 函数即服务资产 {#function-as-a-service-assets}
 
@@ -108,4 +108,4 @@ OpenTelemetry 支持多种由不同云服务商提供的函数即服务的监控
 OpenTelemetry 社区目前提供预构建的 Lambda 层，能够自动对你的应用进行插桩，
 另外在手动或自动对应用进行插桩时可以使用的独立 Collector Lambda 层选项。
 
-更多信息，请参见[函数即服务](/docs/faas/)。
+更多信息，请参见[函数即服务](/docs/platforms/faas/)。
diff --git a/content/zh/docs/faas/lambda-manual-instrument.md b/content/zh/docs/faas/lambda-manual-instrument.md
index c9c63bd638e5..82bf13d6972f 100644
--- a/content/zh/docs/faas/lambda-manual-instrument.md
+++ b/content/zh/docs/faas/lambda-manual-instrument.md
@@ -2,7 +2,7 @@
 title: Lambda 手动插桩
 weight: 11
 description: 使用 OpenTelemetry 手动插桩 Lambda
-default_lang_commit: 06837fe15457a584f6a9e09579be0f0400593d57
+default_lang_commit: 06837fe15457a584f6a9e09579be0f0400593d57 # with links patched
 ---
 
 对于在 Lambda 自动插桩文档中未涵盖的语言，社区尚未提供独立的插桩器。
@@ -11,7 +11,7 @@ default_lang_commit: 06837fe15457a584f6a9e09579be0f0400593d57
 
 ### 添加 OTel Collector Lambda 层的 ARN
 
-参见 [Collector Lambda 层指导](../lambda-collector/)将层添加到你的应用程序并配置
+参见 [Collector Lambda 层指导](../../platforms/faas/lambda-collector/?i18n-patch)将层添加到你的应用程序并配置
 Collector。我们建议首先添加此层。
 
 ### 使用 OTel 插桩 Lambda
diff --git a/content/zh/docs/getting-started/ops.md b/content/zh/docs/getting-started/ops.md
index 0e68da59469d..4471371d6071 100644
--- a/content/zh/docs/getting-started/ops.md
+++ b/content/zh/docs/getting-started/ops.md
@@ -15,6 +15,6 @@ OpenTelemetry 可以帮到你！为了实现在不修改应用程序代码的情
 - [什么是 OpenTelemetry？](../../what-is-opentelemetry/)
 - [如何在不修改代码的情况下为应用程序添加观测性？](../../concepts/instrumentation/zero-code/)
 - [如何设置 Collector？](../../collector/)
-- [如何使用 OpenTelemetry Operator 在 Kubernetes 中实现自动化？](../../kubernetes/operator/)
+- [如何使用 OpenTelemetry Operator 在 Kubernetes 中实现自动化？](../../platforms/kubernetes/operator/)
 
 如果你想要实际体验这些功能，我们的[官方演示库提供了一套完整的应用](/ecosystem/demo/)，非常适合实践学习。
diff --git a/content/zh/docs/what-is-opentelemetry.md b/content/zh/docs/what-is-opentelemetry.md
index 025ae8655d1e..97bc04e3d329 100644
--- a/content/zh/docs/what-is-opentelemetry.md
+++ b/content/zh/docs/what-is-opentelemetry.md
@@ -53,9 +53,9 @@ OpenTelemetry 包括以下主要组件：
 - 可自动生成遥测数据的自动仪表化组件，无需更改代码
 - [OpenTelemetry Collector](/docs/collector)：接收、处理和导出遥测数据的代理
 - 各种其他工具，
-  如[用于 Kubernetes 的 OpenTelemetry Operator](/docs/kubernetes/operator/)、
-  [OpenTelemetry Helm Charts](/docs/kubernetes/helm/) 和
-  [FaaS 的社区资产](/docs/faas/)
+  如[用于 Kubernetes 的 OpenTelemetry Operator](/docs/platforms/kubernetes/operator/)、
+  [OpenTelemetry Helm Charts](/docs/platforms/kubernetes/helm/) 和
+  [FaaS 的社区资产](/docs/platforms/faas/)
 
 OpenTelemetry 广泛应用于许多已集成 OpenTelemetry
 提供默认可观测性的[库、服务和应用](/ecosystem/integrations/)。
diff --git a/static/refcache.json b/static/refcache.json
index 8dc21449f426..05ea0a5aaef4 100644
--- a/static/refcache.json
+++ b/static/refcache.json
@@ -375,10 +375,6 @@
     "StatusCode": 200,
     "LastSeen": "2024-08-09T10:46:12.856737-04:00"
   },
-  "https://cloud.google.com/apis/design/resource_names#full_resource_name": {
-    "StatusCode": 206,
-    "LastSeen": "2025-02-06T01:59:59.999Z"
-  },
   "https://cloud.google.com/appengine/docs/flexible/go/using-websockets-and-session-affinity": {
     "StatusCode": 200,
     "LastSeen": "2024-08-09T10:47:49.544888-04:00"
@@ -407,10 +403,6 @@
     "StatusCode": 200,
     "LastSeen": "2025-02-02T10:58:53.703278-05:00"
   },
-  "https://cloud.google.com/functions/docs/concepts/exec#function_scope_versus_global_scope": {
-    "StatusCode": 200,
-    "LastSeen": "2025-02-06T02:02:59.999Z"
-  },
   "https://cloud.google.com/functions/docs/env-var#runtime_environment_variables_set_automatically": {
     "StatusCode": 200,
     "LastSeen": "2025-02-06T01:43:12.345Z"
@@ -759,10 +751,6 @@
     "StatusCode": 200,
     "LastSeen": "2025-01-06T11:23:41.892135-05:00"
   },
-  "https://developer.apple.com/documentation/uikit/uiapplicationdelegate#1656902": {
-    "StatusCode": 200,
-    "LastSeen": "2025-02-06T02:04:59.999Z"
-  },
   "https://developer.apple.com/documentation/uikit/uidevice/1620059-identifierforvendor": {
     "StatusCode": 200,
     "LastSeen": "2025-01-06T11:23:38.683032-05:00"
@@ -1131,10 +1119,6 @@
     "StatusCode": 200,
     "LastSeen": "2025-02-06T02:05:12.345Z"
   },
-  "https://docs.docker.com/registry/spec/manifest-v2-2/#example-image-manifest": {
-    "StatusCode": 206,
-    "LastSeen": "2025-02-06T02:05:59.999Z"
-  },
   "https://docs.expo.dev/get-started/introduction/": {
     "StatusCode": 206,
     "LastSeen": "2025-01-07T10:55:21.674477-05:00"