Skip to content

Commit 86926e1

Browse files
committed
lab1 edits based on PR comments
1 parent e4ce7e4 commit 86926e1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

labs/lab1/readme.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ In this lab, you will be logging into NGINX One Console and exploring various co
1111
By the end of the lab you will be able to:
1212

1313
- [Understand NGINX One Console product](#nginx-one-console-introduction)
14-
- [Access and navigate the NGINX One Console](#access-and-navigate-the-nginx-one-console)
14+
- [Access and navigate NGINX One Console](#access-and-navigate-nginx-one-console)
1515
- [Create and manage data plane keys that would be used to manage NGINX instances](#create-and-manage-data-plane-keys-that-would-be-used-to-manage-nginx-instances)
1616

1717
## Prerequisites
@@ -46,7 +46,7 @@ NGINX One Console offers the following key benefits:
4646

4747
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.
4848

49-
### Access and navigate the NGINX One console
49+
### Access and navigate NGINX One console
5050

5151
1. Login into the F5 Distributed Cloud console using your account credentials. The login page can be found at: https://console.ves.volterra.io/login/start
5252

0 commit comments

Comments
 (0)