Fixed broken documentation links

Author: rcastley

content/en/ninja-workshops/1-automatic-discovery/2-petclinic-kubernetes/6-profiling-db-query/1-profiling.md

@@ -55,7 +55,7 @@ We can see the various settings you can control, such as the `splunk.profiler.di
 
 Another parameter you may want to change is `splunk.profiler.call.stack.interval`. This is how often the system captures a CPU Stack trace. You may want to reduce this interval setting if you have short spans like the ones we have in our Pet Clinic application. For the demo application, we did not change the default interval value, so Spans may not always have a CPU Call Stack related to them.
 
-You can find how to set these parameters [here](https://docs.splunk.com/observability/en/gdi/get-data-in/application/java/configuration/advanced-java-otel-configuration.html#profiling-configuration-java). In the example below, we see how to set a higher collection rate for call stacks in the `deployment.yaml`, by setting this value in the JAVA_OPTIONS config section.
+You can find how to set these parameters [here](https://help.splunk.com/en/splunk-observability-cloud/manage-data/available-data-sources/supported-integrations-in-splunk-observability-cloud/apm-instrumentation/instrument-a-java-application/configure-the-java-agent#profiling-configuration-java). In the example below, we see how to set a higher collection rate for call stacks in the `deployment.yaml`, by setting this value in the JAVA_OPTIONS config section.
 
 ``` yaml
 env: 

content/en/ninja-workshops/1-automatic-discovery/2-petclinic-kubernetes/7-log-observer-connect/_index.md

@@ -14,4 +14,4 @@ The **Splunk OpenTelemetry Collector** automatically collects logs from the Spri
 
 **Splunk Log Observer** is then used to view the logs, automatically correlating log information with services and traces.
 
-This feature is called [**Related Content**](https://docs.splunk.com/observability/en/metrics-and-metadata/relatedcontent.html).
+This feature is called [**Related Content**](https://help.splunk.com/en/splunk-observability-cloud/data-tools/related-content).

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/2-gateway/2-2-configure-agent.md

@@ -6,7 +6,7 @@ weight: 2
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-**Add the `otlphttp` exporter**: The [**OTLP/HTTP Exporter**](https://docs.splunk.com/observability/en/gdi/opentelemetry/components/otlphttp-exporter.html) is used to send data from the agent to the gateway using the **OTLP/HTTP** protocol.
+**Add the `otlphttp` exporter**: The [**OTLP/HTTP Exporter**](https://help.splunk.com/en/splunk-observability-cloud/manage-data/splunk-distribution-of-the-opentelemetry-collector/get-started-with-the-splunk-distribution-of-the-opentelemetry-collector/collector-components/exporters/otlphttp-exporter) is used to send data from the agent to the gateway using the **OTLP/HTTP** protocol.
 
 1. Switch to your **Agent terminal** window.
 2. Validate that the newly generated `gateway-logs.out`, `gateway-metrics.out`, and `gateway-traces.out` are present in the directory.