Apply suggestions from code review

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

Author: mjang

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

@@ -29,15 +29,15 @@ If you already have accessed F5 Distributed Cloud and have NGINX instances avail
 
 Confirm an F5 Distributed Cloud tenant has been provisioned for you. Log in to MyF5 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.
 
-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 E-Mail in bold is the 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.
 
-Navigate 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.
+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.
 
 ### Confirm access to NGINX One Console in the F5 Distributed Cloud
 
 Once you've logged in with your password, you should be able to see and select the NGINX One tile. 
 
-1. Select the **NGINX One** tile<!-- Style note: this is the UI in DC -->
+1. Select the **NGINX One** tile
 1. Select **Visit Service**
 
 ### Install an instance of NGINX
@@ -66,9 +66,9 @@ 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 will show you how to configure E-Mail alerts.
+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 F5 Distributed Cloud generates alerts from all its services including NGINX One. 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.
+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.
 
 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).
@@ -77,40 +77,39 @@ This page describes basic steps to set up an email alert. For authoritative docu
 
 To configure security-related alerts, follow these steps:
 
-1. Navigate to the F5 Distributed Cloud Console at https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io. 
+1. Go to the F5 Distributed Cloud Console at https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io. 
 1. Select **Audit Logs & Alerts**
 1. Select **Manage > Alert Receiver**
 1. Configure the **Alert Receivers**
    1. Enter the name of your choice.
    1. (Optional) Specify a label and description.
-1. Under **Receiver**, select Email and enter your email address.
+1. Under **Receiver**, select **Email** and enter your email address.
 1. Select **Add Alert Receiver**
-1. Your Email receiver should now appear on the list of Alert Receivers.
-1. Under the Actions column, select Verify Email.
+1. Your email receiver should now appear on the list of Alert Receivers.
+1. Under the **Actions** column, select **Verify Email**.
 1. Select **Send email** to confirm.
 1. You should receive a verification code in the email provided. Copy that code.
-1. Under the Actions column, select **Enter verification code**.
+1. Under the **Actions** column, select **Enter verification code**.
 1. Paste the code and select **Verify receiver**.
 
 ## Configure Alert Policy
 
 Next, configure the policy that identifies when you'll get an alert. 
 
-1. Navigate to **Alerts Management > Alert Policies**.
+1. Go to **Alerts Management > Alert Policies**.
 1. Select **Add Alert Policy**.
    1. Enter the name of your choice.
    1. (Optional) Specify a label and description.
-1. Under Alert Reciever Configuration > Alert Receivers, select the Alert Receiver you just created.
-1. Under Policy Rules select Configure.
-1. Select Add Item.
-1. Under Select Alerts (TBD).
-1. Set the Action as Send and select Apply.
+1. Under **Alert Reciever Configuration > Alert Receivers,** select the **Alert Receiver** you just created.
+1. Under **Policy Rules** select **Configure**.
+1. Select **Add Item**.
+1. Under **Select Alerts** (TBD).
+1. Set the **Action as Send** and select **Apply**.
 
 Now set a second alert related to Common Vulnerabilities and Exposures (CVEs).
 
-1. Select Add Item
-1. Under Select Alerts {adding additional Alert type for CVE)
-1. Set the Action as Send and select Apply
+1. Select **Add Item**
+1. Under **Select Alerts**, set the **Action** as **Send** and select **Apply**
 1. Select **Save and Exit**
 
 You've now set up F5 Distributed Cloud to send you security-related alerts from NGINX One Console.
@@ -127,5 +126,5 @@ You will now receive an email any time the NGINX One Console recognizes one of y
 
 ## Next steps
 
-Now that you have NGINX instances connected to the Console, consider reviewing our [use cases]({{< ref "/nginx-one/" >}}) to see how you can easily manage your NGINX instances, draft new configurations, and more.
+Now that you have NGINX instances connected to the NGINX One Console, consider reviewing our [use cases]({{< ref "/nginx-one/" >}}) to see how you can easily manage your NGINX instances, draft new configurations, and more.
 Additionally, you can review how to add additional Alert Receivers such as [SMS](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-email-sms), [Slack](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-slack), [PagerDuty](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-pagerduty), or with a [webhook](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-webhook).