Address review comments

Author: defanator

content/includes/nginx-one/how-to/install-nginx-agent.md

@@ -8,7 +8,7 @@ files:
 After entering your data plane key, you'll see a `curl` command to install NGINX Agent, similar to the one below. Copy and run this command on each NGINX instance. Once installed, NGINX Agent typically registers with NGINX One within a few seconds.
 
 {{<call-out "important" "Connecting to NGINX One" >}}
- Ensure that any firewall rules you have in place for your NGINX hosts allows network traffic to port `443` for all of the following IP ranges:
+ Ensure that any firewall rules you have in place for your NGINX hosts allows network traffic to port `443` for all of the following IP address ranges:
 
 - `3.135.72.139/32`
 - `3.133.232.50/32`

content/nginx-one/changelog.md

@@ -34,8 +34,8 @@ Stay up-to-date with what's new and improved in the F5 NGINX One Console.
 
 ### IPv6 endpoints for NGINX Agent and NGINX Plus usage reporting
 
-Your instances running in dualstack or IPv6-only environments are now able to communicate with NGINX One APIs via IPv6.
-Please check the [Getting Started Guide]({{< ref "/nginx-one/getting-started.md#install-nginx-agent" >}}) for IP ranges required to be enabled in your firewalls.
+Your instances which run in dual-stack or IPv6-only environments can now communicate with NGINX One Console APIs through IPv6 addresses.
+See the [Getting Started Guide]({{< ref "/nginx-one/getting-started.md#install-nginx-agent" >}}) for the IP address ranges you need to allow in your firewalls.
 
 ## July 15, 2025
 

content/nginx-one/getting-started.md

@@ -126,7 +126,7 @@ Depending on whether this is your first time using NGINX One Console or you've u
 After entering your data plane key, you'll see a `curl` command similar to the one below. Copy and run this command on each NGINX instance to install NGINX Agent. Once installed, NGINX Agent typically registers with NGINX One within a few seconds.
 
 {{<call-out "important" "Connecting to NGINX One" >}}
-NGINX Agent must be able to establish a connection to NGINX One Console's Agent endpoint (`agent.connect.nginx.com`). Ensure that any firewall rules you have in place for your NGINX hosts allows network traffic to port `443` for all of the following IP ranges:
+NGINX Agent must be able to establish a connection to NGINX One Console's Agent endpoint (`agent.connect.nginx.com`). Ensure that any firewall rules you have in place for your NGINX hosts allows network traffic to port `443` for all of the following IP address ranges:
 
 - `3.135.72.139/32`
 - `3.133.232.50/32`

content/solutions/about-subscription-licenses.md

@@ -100,7 +100,7 @@ To ensure NGINX Plus R33 or later can send usage reports, follow these steps bas
 
 ### For internet-connected environments
 
-1. Allow outbound HTTPS traffic on TCP port `443` to communicate with F5's licensing endpoint (`product.connect.nginx.com`). Ensure that the following IP ranges are allowed:
+1. Allow outbound HTTPS traffic on TCP port `443` to communicate with F5's licensing endpoint (`product.connect.nginx.com`). Ensure that the following IP address ranges are allowed:
 
    - `3.135.72.139/32`
    - `3.133.232.50/32`

content/solutions/r33-pre-release-guidance-for-automatic-upgrades.md

@@ -73,7 +73,7 @@ To ensure NGINX Plus R33 can report telemetry data, follow these steps based on
 #### For internet-connected environments:
 
 1. **Open port 443**:
-   Allow outbound HTTPS traffic on TCP port 443 to communicate with F5's licensing endpoint (`product.connect.nginx.com`). Ensure that the following IP ranges are allowed:
+   Allow outbound HTTPS traffic on TCP port 443 to communicate with F5's licensing endpoint (`product.connect.nginx.com`). Ensure that the following IP address ranges are allowed:
 
    - `3.135.72.139/32`
    - `3.133.232.50/32`