lab1 edits based on PR comments

Author: sdutta9

labs/lab1/readme.md

@@ -2,7 +2,7 @@
 
 ## Introduction
 
-In this lab, you will be logging into NGINX One Console and exploring various components within NGINX One console. This lab requires that you have access to F5 Distributed Cloud to work with NGINX one console. As part of this lab, you will explore the Nginx One console product, as a quick Overview of what it is and how to access it.
+In this lab, you will be logging into NGINX One Console and exploring various components within it. This lab requires that you have access to F5 Distributed Cloud to work with the One Console. As part of this lab, you will explore the NGINX One console product, as a quick Overview of what it is and how to access it.
 
 <br/>
 
@@ -20,7 +20,7 @@ By the end of the lab you will be able to:
 - You must have enabled NGINX One service on F5 Distributed Cloud(XC)
 - See `Lab0` for instructions on setting up your system for this Workshop
 - Familiarity with basic Linux concepts and commands
-- Familiarity with basic Nginx concepts and commands
+- Familiarity with basic NGINX concepts and commands
 
 <br/>
 
@@ -44,7 +44,7 @@ NGINX One Console offers the following key benefits:
 
 ![NGINX Agent](media/nginx-agent-icon.png)
 
-The Nginx One Console requires `nginx-agent`, an open source software module written by Nginx that connects and communicates with Nginx One.  This nginx-agent must be installed and running on every Nginx instance that you wish to manage with Nginx One.  You will use the publicly available Nginx with Agent images from Docker Hub for your Nginx OSS containers.  In addition, as part of your Docker Compose file, your NGINX Plus containers already have the required `NGINX Agent` installed for you.  Nginx-agent can also be installed using regular Linux package managers like `apt` and `yum`.  Refer to the References Section for links to the Nginx Agent installation guides.
+The NGINX One Console requires `NGINX Agent`, an open source software module written by NGINX that connects and communicates with NGINX One.  This NGINX Agent must be installed and running on every NGINX instance that you wish to manage with NGINX One.  You will use the publicly available NGINX with Agent images from Docker Hub for your NGINX OSS containers.  In addition, as part of your Docker Compose file, your NGINX Plus containers already have the required `NGINX Agent` installed for you.  NGINX Agent can also be installed using regular Linux package managers like `apt` and `yum`.  Refer to the References Section for links to the NGINX Agent installation guides.
 
 ### Access and navigate the NGINX One console
 
@@ -56,11 +56,11 @@ The Nginx One Console requires `nginx-agent`, an open source software module wri
 
     ![XC HomeScreen](media/lab1_none-tile.png)
 
-1. Click on the `NGINX One` tile from the home screen. The NGINX One "welcome" screen will appear. Make sure the Nginx One Console status shows `green - Enabled` as highlighted in below screenshot.  Click on `Visit Service`.  If it is not enabled, you must request access from your F5 Distributed Cloud admin.
+1. Click on the `NGINX One` tile from the home screen. The NGINX One "welcome" screen will appear. Make sure the NGINX One Console status shows `green - Enabled` as highlighted in below screenshot.  Click on `Visit Service`.  If it is not enabled, you must request access from your F5 Distributed Cloud admin.
 
     ![N One Visit Service](media/lab1_none-service.png)
 
-1. By default, this will bring you to the Nginx Console `Overview Dashboard` page. As no NGINX Instances are being managed by NGINX One you are seeing the blank dashboard as shown in below screenshot.
+1. By default, this will bring you to the NGINX One Console `Overview Dashboard` page. As no NGINX Instances are being managed by NGINX One you are seeing the blank dashboard as shown in below screenshot.
 
     ![Empty Dashboard](media/lab1_none-empty-overview-dashboard.png)
 
@@ -72,15 +72,15 @@ The Nginx One Console requires `nginx-agent`, an open source software module wri
 
 ### Create and manage data plane keys that would be used to manage NGINX instances
 
-1. Within the Nginx One Console, click on `Manage > Data Plane Keys`. This would show all the Data Plane keys that you currently have.
+1. Within the NGINX One Console, click on `Manage > Data Plane Keys`. This would show all the Data Plane keys that you currently have.
 
     ![Dataplane key](media/lab1_none-dataplane-key-overview.png)
 
 1. Click on `Add Data Plane Key` to create a new Dataplane key. This should open an `Add Data Plane Key` window. Provide a name of your choice for the new key. By default, the expiration date is set for a year. You can modify the expiration data as per your preference or keep the defaults for this workshop. Click on `Generate` to create your new key.
 
     ![New Dataplane key](media/lab1_none-dataplane-key-new.png)
 
-    Once the key is generated, copy the value of this key to the clipboard using the `Copy` icon on the right side.  **NOTE:**  This Dataplane Key is only shown here and NGINX One doesn't save this value. Save this value locally as you would be using it to register new NGINX Instances.  You can Register as many Nginx Instances as you like with the same Dataplane Key.  If you lose the value of the key then you need to generate a new one again.
+    Once the key is generated, copy the value of this key to the clipboard using the `Copy` icon on the right side.  **NOTE:**  This Dataplane Key is only shown here and NGINX One doesn't save this value. Save this value locally as you would be using it to register new NGINX Instances.  You can Register as many NGINX Instances as you like with the same Dataplane Key.  If you lose the value of the key then you need to generate a new one again.
 
     ![New Dataplane key save](media/lab1_none-dataplane-key-save.png)
 
@@ -97,7 +97,7 @@ The Nginx One Console requires `nginx-agent`, an open source software module wri
 
 ### (Optional Exercise): Delete a data plane key
 
-1. Active keys cannot be directly deleted. Any active key first needs to be revoked and then only it can be deleted.
+1. Active keys cannot be directly deleted. The key must first be revoked and then can be deleted.
 
 1. You can delete a revoked data plane key by opening the Data Plane Keys Page and then navigating to the `Revoked Keys` tab. This view should list all the revoked keys.
 
@@ -116,8 +116,8 @@ This ends lab1.
 
 ## References:
 
-- [Nginx One Console](https://docs.nginx.com/nginx-one/)
-- [Nginx Agent](https://docs.nginx.com/nginx-agent/overview/)
+- [NGINX One Console](https://docs.nginx.com/nginx-one/)
+- [NGINX Agent](https://docs.nginx.com/nginx-agent/overview/)
 
 <br/>