From d18e073e2875a9aa85b00c1ae488f128f1884a91 Mon Sep 17 00:00:00 2001
From: nginx-aoife <50101789+nginx-aoife@users.noreply.github.com>
Date: Wed, 28 Aug 2024 15:39:10 +0100
Subject: [PATCH] Fix broken URLs in documentation (#2474)

Fix broken URLs
---
 site/content/how-to/monitoring/troubleshooting.md | 2 +-
 site/content/overview/resource-validation.md      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/site/content/how-to/monitoring/troubleshooting.md b/site/content/how-to/monitoring/troubleshooting.md
index c168c16a86..4d4b266ad8 100644
--- a/site/content/how-to/monitoring/troubleshooting.md
+++ b/site/content/how-to/monitoring/troubleshooting.md
@@ -426,7 +426,7 @@ If you `describe` your HTTPRoute and see the following error:
 The Service associated with your HTTPRoute is configured with a IP Family different than the one specified in the NginxProxy configuration.
 To **resolve** this, you can do one of the following:
 
-- Update the NginxProxy configuration with the proper [`ipFamily`](({{< relref "reference/api.md" >}})) field. You can edit the NginxProxy configuration using `kubectl edit`. For example:
+- Update the NginxProxy configuration with the proper [`ipFamily`]({{< relref "reference/api.md" >}}) field. You can edit the NginxProxy configuration using `kubectl edit`. For example:
 
   ```shell
   kubectl edit -n nginx-gateway nginxproxies.gateway.nginx.org ngf-proxy-config
diff --git a/site/content/overview/resource-validation.md b/site/content/overview/resource-validation.md
index 533b64bb84..0111b7f724 100644
--- a/site/content/overview/resource-validation.md
+++ b/site/content/overview/resource-validation.md
@@ -52,7 +52,7 @@ More information on CEL in Kubernetes can be found [here](https://kubernetes.io/
 
 This step catches the following cases of invalid values:
 
-- Valid values from the Gateway API perspective but not supported by NGINX Gateway Fabric yet. For example, a feature in an HTTPRoute routing rule. For the list of supported features see [Gateway API Compatibility](gateway-api-compatibility.md) doc.
+- Valid values from the Gateway API perspective but not supported by NGINX Gateway Fabric yet. For example, a feature in an HTTPRoute routing rule. For the list of supported features see [Gateway API Compatibility]({{< relref "/gateway-api-compatibility.md" >}}) doc.
 - Valid values from the Gateway API perspective, but invalid for NGINX, because NGINX has stricter validation requirements for certain fields. These values will cause NGINX to fail to reload or operate erroneously.
 - Invalid values (both from the Gateway API and NGINX perspectives) that were not rejected because Step 1 was bypassed. Similar to the previous case, these values will cause NGINX to fail to reload or operate erroneously.
 - Malicious values that inject unrestricted NGINX config into the NGINX configuration (similar to an SQL injection attack).