Apply suggestions from code review

Co-authored-by: Travis Martin <[email protected]>

Author: mjang

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 IPs:
+ Ensure that any firewall rules you have in place for your NGINX hosts allow network traffic to port `443` for all of the following IPs:
 
 - `3.135.72.139`
 - `3.133.232.50`

content/nginx-one/secure-your-fleet/secure.md

@@ -6,7 +6,9 @@ nd-content-type: how-to
 nd-product: NGINX One
 ---
 
-With this page, you'll learn how to set up alerts in F5 Distributed Cloud. Once configured, you'll see the CVEs and insecure configurations associated with your NGINX fleet. These instructions are intended for those responsible for keeping their NGINX infrastructure and application traffic secure. It assumes you know how to:
+Set up alerts in F5 Distributed Cloud to track CVEs and insecure configurations across your NGINX fleet.
+
+These instructions are for those responsible for keeping their NGINX infrastructure and application traffic secure. Before you begin, make sure you know how to:
 
 - Install Linux programs or run Docker containers
 
@@ -27,11 +29,22 @@ If you already have accessed F5 Distributed Cloud and have NGINX instances avail
 
 ### Confirm access to the F5 Distributed Cloud
 
-Confirm an F5 Distributed Cloud tenant has been provisioned for you. Log in to the [MyF5](https://my.f5.com) customer portal and review your subscriptions. You should see within one of your subscriptions "Distributed Cloud". This could be in either an NGINX subscription or a Distributed Cloud. If the above does not appear in any of your subscriptions, reach out to either your F5 Account Team or Customer Success Manager.
+Make sure your F5 Distributed Cloud tenant is provisioned before continuing.
+
+Log in to the [MyF5](https://my.f5.com) customer portal and check your subscriptions. Look for **Distributed Cloud** under one of your subscriptions. It might appear under an NGINX subscription or a dedicated Distributed Cloud subscription.
+
+If you don’t see Distributed Cloud listed, contact your F5 account team or Customer Success Manager.
+
+Once your tenant is provisioned, you or someone in your organization should receive an email from `[email protected]` prompting you to set a password. The **account name** shown in bold in the email is your tenant name.
 
-With access, you or someone in your organization should have an email from [email protected] asking you to update your password when the tenant was created. The account name referenced in the email in bold is the tenant name.
+To access the F5 Distributed Cloud Console, go to: `https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/`
 
-Go to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/ to access F5 Distributed Cloud. If you have never logged in, select the **Forgot Password?** option in the log in screen. Alternatively, if someone within your organization has access, ask them to add you as a user within your tenant with a role providing permissions for NGINX One.
+If you haven’t logged in before:
+- Select **Forgot password?** on the login screen.
+
+If someone in your organization already has access:
+- Ask them to add you as a user in your tenant.
+- Make sure the role they assign gives you the right permissions.
 
 ### Confirm access to NGINX One Console in the F5 Distributed Cloud
 
@@ -42,13 +55,14 @@ Once you've logged in with your password, you should be able to see and select t
 
 ### Install an instance of NGINX
 
-Ensure you have an instance of [NGINX Open Source or NGINX Plus]({{< ref "/nginx/admin-guide/installing-nginx/" >}}) installed and available. This guide provides instructions for connecting an instance installed in a Linux environment (VM or bare metal hardware) where you have command line access.
-Alternatively, we also have instructions for [Deploying NGINX and NGINX Plus with Docker]({{< ref "/nginx/admin-guide/installing-nginx/installing-nginx-docker.md" >}}) with NGINX and the NGINX Agent installed. That deployment can connect with environment variables.
+Ensure you have an instance of [NGINX Open Source or NGINX Plus]({{< ref "/nginx/admin-guide/installing-nginx/" >}}) installed and available. This guide shows you how to connect an instance installed on a Linux system (VM or bare metal hardware) where you have command line access.
+Alternatively, you can [deploy NGINX Open Source or NGINX Plus with Docker]({{< ref "/nginx/admin-guide/installing-nginx/installing-nginx-docker.md" >}}). This method includes the NGINX Agent and uses environment variables to connect the deployment.
 
 ## Connect at least one NGINX instance to the NGINX One Console
 
-If you already have connected instances to the NGINX One Console, you can start to [Configure an active alert policy]({{< ref "/nginx-one/secure-your-fleet/secure.md#configure-an-active-alert-policy" >}}).
-Otherwise, you need to add an instance, generate a data plane key, and install NGINX Agent. We assume this is the first time you are connecting an instance.
+If you've already connected instances to the NGINX One Console, you can [configure an active alert policy]({{< ref "/nginx-one/secure-your-fleet/secure.md#configure-an-active-alert-policy" >}}).
+
+If not, you’ll need to add an instance, generate a data plane key, and install NGINX Agent. This guide assumes you're connecting an instance for the first time.
 
 ### Add an instance
 
@@ -66,9 +80,13 @@ You can also install NGINX Agent from our repositories and configure it manually
 
 ## Configure an active alert policy
 
-The NGINX One Console monitors all connected NGINX instances for CVEs and insecure configurations. Using the F5 Distributed Cloud's Alert Policies, you can receive alerts for these risks in a manner of your choosing; for the purposes of this guide, we show you how to configure email alerts.
+The NGINX One Console monitors all connected NGINX instances for CVEs and insecure configurations.
+
+With F5 Distributed Cloud alert policies, you can choose how to receive alerts for these risks. This guide shows how to set up email alerts.
+
+F5 Distributed Cloud generates alerts from all its services, including the NGINX One Console.
 
-The F5 Distributed Cloud generates alerts from all its services including NGINX One Console. You can configure rules to send those alerts to a receiver of your choice. These instructions walk you through how to configure an email notification when we see new CVEs or detect security issues with your NGINX instances.
+You can create rules to send those alerts to the receiver of your choice. This guide shows how to set up email notifications for new CVEs or other security issues detected in your NGINX instances.
 
 This page describes basic steps to set up an email alert. For authoritative documentation, see
 [Alerts - Email & SMS](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-email-sms).
@@ -132,7 +150,7 @@ Now to make sure your new policy works, add your new policies to the list of **A
 1. Select the **Add Select Active Alert Policies** button.	
 1. Select **Add Item**
 
-You've now set up F5 Distributed Cloud to send you alerts from NGINX One Console, to your email address. When the alert policy identifies an alert, it sends you an email from **[email protected]**.
+You've now set up F5 Distributed Cloud to send you alerts from the NGINX One Console to your email. When an alert is triggered, you'll receive a message from **[email protected]**.
 
 ## Summary