Cherry Pick URL fixes into Release 1.4 (#2479)

nginx · Aug 29, 2024 · d85a6ca · d85a6ca
1 parent 8e653d6
commit d85a6ca
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git 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
@@ -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).