fix language and leveling for docs

Author: salonichf5

content/ngf/how-to/_index.md

@@ -1,5 +1,5 @@
 ---
 title: "How-to guides"
 url: /nginx-gateway-fabric/how-to/
-weight: 400
+weight: 500
 ---

content/ngf/reference/_index.md

@@ -1,5 +1,5 @@
 ---
 title: "Reference"
-weight: 500
+weight: 600
 url: /nginx-gateway-fabric/reference/
 ---

content/ngf/releases.md

@@ -1,7 +1,7 @@
 ---
 title: Releases
 description: "NGINX Gateway Fabric releases."
-weight: 700
+weight: 800
 toc: true
 type: reference
 product: NGF

content/ngf/support.md

@@ -1,6 +1,6 @@
 ---
 title: Support
-weight: 600
+weight: 700
 toc: true
 type: reference
 product: NGF

content/ngf/installation/installing-ngf/upgrading-ngf.md renamed to content/ngf/upgrading-ngf.md

@@ -2,7 +2,7 @@
 title: Upgrade NGINX Gateway Fabric to version 2.x
 weight: 400
 toc: true
-type: how-to
+type: upgrade-ngf
 product: NGF
 docs: DOCS-0000
 ---
@@ -20,7 +20,7 @@ To upgrade NGINX Gateway Fabric from version 1.x to the new architecture in vers
 
 To remove the previous version 1.x of NGINX Gateway Fabric, follow these steps:
 
-First, run the following command to uninstall NGINX Gateway Fabric from the `nginx-gateway` namespace, and update the release name to `ngf` to your release name if it is different:
+First, run the following command to uninstall NGINX Gateway Fabric from the `nginx-gateway` namespace, and update `ngf` to your release name if it is different:
 
 ```shell
 helm uninstall ngf -n nginx-gateway 
@@ -87,15 +87,15 @@ NGINX configurations are generated by the control plane and securely delivered t
 
 Each data plane pod runs NGINX alongside the Agent, which applies config updates and handles reloads without shared volumes or signals. This design ensures dynamic, per-Gateway traffic management and operational isolation.
 
-New fields have been added to the `NginxProxy` resource to configure infrastructure-related settings for data plane deployments. You can modify the `NginxProxy` resource at either the Gateway or GatewayClass level. These new fields provide the flexibility to customize deployment and service configurations.
+New fields have been added to the `NginxProxy` resource to configure infrastructure-related settings for data plane deployments. The `NginxProxy` resource is now a namespaced-scoped resource, instead of a cluster-scoped resource, and can be modified at either the Gateway or GatewayClass level. These new fields provide the flexibility to customize deployment and service configurations.
 
 For detailed instructions on how to modify these settings, refer to the [Configure infrastructure-related settings]({{< ref "/ngf/how-to/data-plane-configuration.md#configure-infrastructure-related-settings" >}}) guide.
 
 
 ### Key links for the version 2.x update
 
 - To read more on [modifying data plane configuration]({{< ref "/ngf/how-to/data-plane-configuration.md" >}}).
-- To learn more about [deploying a Gateway for data plane instances]({{< ref "/ngf/installation/installing-ngf/deploy-data-plane.md" >}})
+- To learn more about [deploying a Gateway for data plane instances]({{< ref "/ngf/installation/installing-ngf/deploy-data-plane.md" >}}).
 - To adding secure [authentication to control plane and data planes]({{< ref "/ngf/installation/installing-ngf/control-plane-certs.md" >}}).
 - To read more about [architecture changes]({{< ref "/ngf/overview/gateway-architecture.md" >}}).
 - For detailed [API reference]({{< ref "/ngf/reference/api.md" >}}).