Skip to content
This repository was archived by the owner on Apr 18, 2024. It is now read-only.

Commit 93e6908

Browse files
committed
Typo fix
1 parent 7981905 commit 93e6908

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ This will create all the required elements in a compartment in the target OCI te
8484
The output of the Apply command will contain a URL to access Cloudera Manager. This is the public IP of the Utility Host, which runs the deployment.
8585

8686
## Monitoring Cluster Build
87-
Because all tasks are done in CloudInit, there are two ways to monitor the deployment. Firstly you can login go the Cloudera Manager URL once it is up and running a few minutes after the Apply command finishes. Alternatively you can SSH into the Utility node, and monitor the log file "/var/log/cloudera-OCI-initialize.log" which contains detailed output from the deployment.
87+
Because all tasks are done in CloudInit, there are two ways to monitor the deployment. Firstly you can login to the Cloudera Manager URL once it is up and running a few minutes after the Apply command finishes. Alternatively you can SSH into the Utility node, and monitor the log file "/var/log/cloudera-OCI-initialize.log" which contains detailed output from the deployment.
8888

8989
## Destroy the Deployment
9090

0 commit comments

Comments
 (0)