Docs troubleshoot fixes

PR-URL: hasura/graphql-engine-mono#11220
GitOrigin-RevId: 06b883f4555a345a4df95a6469867a19cddf5a2b

Author: seanparkross

docs/docs/observability/troubleshoot/index.mdx

@@ -42,7 +42,7 @@ issues.
 
 To fully understand and utilize traces, refer to the following resources:
 
-- [Hasura OpenTelemetry Docs](observability/opentelemetry/graphql-engine/#available-traces)
+- [Hasura OpenTelemetry Docs](/observability/opentelemetry/graphql-engine/#available-traces)
 - [Using OpenTelemetry Traces with Hasura](https://hasura.io/blog/using-opentelemetry-traces-observe-hasura-powered-applications)
 
 Traces provide valuable insights into the flow of requests and performance bottlenecks. They typically list spans with

docs/docs/observability/troubleshoot/logs.mdx

@@ -31,7 +31,7 @@ HASURA_GRAPHQL_ENABLED_LOG_TYPES
 ```
 
 You can find detailed information about different log types supported by Hasura in the
-[Hasura Documentation](deployment/logging/#configurable-log-types). Grafana provides a filter that allows you to filter
+[Hasura Documentation](/deployment/logging/#configurable-log-types). Grafana provides a filter that allows you to filter
 different log types.
 
 <Thumbnail src="/img/observability/troubleshoot/errorsuccesslogs.jpeg" alt="traces" />