Apply suggestions from code review

Co-authored-by: Saylor Berman <[email protected]>

Author: salonichf5

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

@@ -7,21 +7,21 @@ product: NGF
 docs: DOCS-0000
 ---
 
-This guide provides step-by-step instructions for upgrading NGINX Gateway Fabric from version 1.6.x to 2.0.x, highlighting key architectural changes, expected downtime, and important considerations for custom resource definitions.
+This guide provides step-by-step instructions for upgrading NGINX Gateway Fabric from version 1.x to 2.0, highlighting key architectural changes, expected downtime, and important considerations for custom resource definitions.
 
 ---
 
-### Upgrade from v1.6.x to v2.0.x
+### Upgrade from v1.x to v2.0
 
-To upgrade NGINX Gateway Fabric from version 1.6.2 to the latest version 2.0.0, you must uninstall the existing CRDs and perform a fresh installation with the new CRDs. This upgrade involves uninstalling the existing NGINX Gateway Fabric deployment making it a breaking change and will lead to application downtime during the process.
+To upgrade NGINX Gateway Fabric from version 1.6.2 to the latest version 2.0.0, you must uninstall the existing NGINX Gateway Fabric CRDs and deployment, and perform a fresh installation. This will cause brief downtime during the upgrade process.
 
-{{<note>}} You do not need to uninstall the Gateway API CRDs during the upgrade. These standard Kubernetes resources are compatible with the new NGINX Gateway Fabric version. {{</note>}}
+{{<note>}} You do not need to uninstall the Gateway API CRDs during the upgrade. These resources are compatible with the new NGINX Gateway Fabric version. {{</note>}}
 
 #### Uninstalling previous NGINX Gateway Fabric v1.6.x
 
 To remove the previous version 1.6.x of NGINX Gateway Fabric, follow these steps:
 
-1. Run the following command to uninstall NGINX Gateway Fabric from the `nginx-gateway` namespace:
+1. Run the following command to uninstall NGINX Gateway Fabric from the `nginx-gateway` namespace, updating `ngf` to your release name if different:
 
 ```shell
 helm uninstall ngf -n nginx-gateway