From 502ca5438b670a9990d18b5a2789059e63f31dea Mon Sep 17 00:00:00 2001 From: Saylor Berman Date: Tue, 18 Mar 2025 08:10:39 -0600 Subject: [PATCH] Fix NGF header link A header link was not written correctly and didn't actually link to the section. --- content/ngf/how-to/data-plane-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ngf/how-to/data-plane-configuration.md b/content/ngf/how-to/data-plane-configuration.md index 90d2070f2..d74555049 100644 --- a/content/ngf/how-to/data-plane-configuration.md +++ b/content/ngf/how-to/data-plane-configuration.md @@ -15,7 +15,7 @@ NGINX Gateway Fabric can dynamically update the global data plane configuration The data plane configuration is stored in the NginxProxy custom resource, which is a cluster-scoped resource that is attached to the `nginx` GatewayClass. -By default, the NginxProxy resource is not created when installing NGINX Gateway Fabric. However, you can set configuration options in the `nginx.config` Helm values, and the resource will be created and attached when NGINX Gateway Fabric is installed using Helm. You can also [manually create and attach](#manually-creating-the-configuration) the resource after NGINX Gateway Fabric is already installed. +By default, the NginxProxy resource is not created when installing NGINX Gateway Fabric. However, you can set configuration options in the `nginx.config` Helm values, and the resource will be created and attached when NGINX Gateway Fabric is installed using Helm. You can also [manually create and attach](#manually-create-the-configuration) the resource after NGINX Gateway Fabric is already installed. When installed using the Helm chart, the NginxProxy resource is named `-proxy-config`.