update per production UI

Clarify steps

Author: mjang

content/includes/nginx-one/how-to/generate-data-plane-key.md

@@ -7,15 +7,13 @@ files:
 
 A data plane key is a security token that ensures only trusted NGINX instances can register and communicate with NGINX One.
 
-To generate a data plane key:
+To generate a data plane key, select **Manage > Instances > Add Instance**:
 
 - **For a new key:** In the **Add Instance** pane, select **Generate Data Plane Key**.
 - **To reuse an existing key:** If you already have a data plane key and want to use it again, select **Use existing key**. Then, enter the key's value in the **Data Plane Key** box.
 
 {{<call-out "caution" "Data plane key guidelines" "fas fa-key" >}}
 Data plane keys are displayed only once and cannot be retrieved later. Be sure to copy and store this key securely.
 
-Data plane keys expire after one year. You can change this expiration date later by [editing the key]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md#change-expiration-date" >}}).
-
-If you [Revoke a data plane key]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md#revoke-data-plane-key" >}}) you disconnect all instances registered with that key.
+Data plane keys expire after one year. You can change this expiration date later by [editing the key]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md#change-expiration-date" >}}). If you [revoke a data plane key]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md#revoke-data-plane-key" >}}) you disconnect all instances registered with that key.
 {{</call-out>}}

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

@@ -5,14 +5,16 @@ files:
   - content/nginx-one/getting-started.md
 ---
 
-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.
+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" >}}
-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 IPs:
+ 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:
 
 - `3.135.72.139`
 - `3.133.232.50`
 - `52.14.85.249`
+
+NGINX Agent must be able to establish a connection to NGINX One Console's Agent endpoint (`agent.connect.nginx.com`). 
 {{</call-out>}}
 
 To install NGINX Agent on an NGINX instance:

content/nginx-one/_index.md

@@ -40,9 +40,9 @@ F5 NGINX One Console makes it easy to manage NGINX instances across locations an
     {{<card title="Manage your NGINX instances" titleUrl="/nginx-one/nginx-configs/" >}}
       Manage one instance or groups of instances. Monitor certificates. Set up metrics.
     {{</card>}}
-    {{<card title="Secure with NGINX App Protect" titleUrl="/nginx-one/nap-integration/" >}}
-      Manage one instance or groups of instances. Monitor certificates. Set up metrics.
-    {{</card>}}
+    {{<card title="Connect Kubernetes deployments" titleUrl="/nginx-one/k8s/">}}
+      Monitor deployments for CVEs and certificates
+    {{</ card >}}
   {{</card-section>}}
 {{</card-layout>}}
 
@@ -53,9 +53,6 @@ F5 NGINX One Console makes it easy to manage NGINX instances across locations an
     {{<card title="Secure with NGINX App Protect" titleUrl="/nginx-one/nap-integration/" >}}
       Set up security policies by instance and group
     {{</card>}}
-    {{<card title="Connect Kubernetes deployments" titleUrl="/nginx-one/k8s/">}}
-      Monitor deployments for CVEs and certificates
-    {{</ card >}}
     {{<card title="Organize users with RBAC" titleUrl="/nginx-one/rbac/" >}}
       Assign responsibilities with role-based access control 
     {{</card>}}

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

@@ -27,7 +27,7 @@ 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 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.
+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.
 
 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.
 
@@ -48,7 +48,7 @@ Alternatively, we also have instructions for [Deploying NGINX and NGINX Plus wit
 ## 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 generate a data plane key, add an instance, and install NGINX Agent. We assume this is the first time you are connecting an instance.
+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.
 
 ### Add an instance
 
@@ -85,8 +85,8 @@ To configure security-related alerts, follow these steps:
    1. (Optional) Specify a label and description.
 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**.
+   Your alert receiver should now appear on the list of Alert Receivers.
+1. Select the **Actions** ellipsis (...) for your receiver. 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**.
@@ -105,13 +105,15 @@ Next, configure the policy that identifies when you'll get an alert.
 1. Select **Add Item**.
 1. Under **Select Alerts** select a filter. If you're interested in all NGINX alerts, select **Matching RegEx of Alertname**. In the text box that appears, enter **NGINX**.
 1. Set the **Action as Send** and select **Apply**.
-1. Select **Apply** again, and then select **Apply Alert Policy**.
 
 Now set a second alert related to Common Vulnerabilities and Exposures (CVEs).
 
 1. Select **Add Item**
+1. Under **Select Alerts** select a filter. If you're interested in all CVEs, select **Matching RegEx of Alertname**. In the text box that appears, enter **CVE**.
 1. Under **Select Alerts**, set the **Action** as **Send** and select **Apply**
-1. Select **Save and Exit**
+   You should now see two alerts under **Policy Rules**.
+1. Select **Apply** to save thse policies.
+1. Select **Add Alert Policy**.
 
 You've now set up F5 Distributed Cloud to send you security-related alerts from NGINX One Console.