feat(ansible): address documentation comments

- word choice in advanced_options
- refer to correct environment key in getAnsibleVerbosity()

Author: djzager

doc/ansible/dev/advanced_options.md

@@ -115,8 +115,8 @@ From this data, we can see that the environment variable will be
 ## Ansible Verbosity
 
 Setting the verbosity at which `ansible-runner` is run controls how verbose the
-output of `ansible-playbook` will be. The normal rules for verbosity apply here
-where higher values means more verbose output. Acceptable values range from 0
+output of `ansible-playbook` will be. The normal rules for verbosity apply
+here, where higher values mean more output. Acceptable values range from 0
 (only the most severe messages are output) to 7 (all debugging messages are
 output).
 

pkg/ansible/watches/watches.go

@@ -256,7 +256,7 @@ func verifyAnsiblePath(playbook string, role string) error {
 }
 
 // if the WORKER_* environment variable is set, use that value.
-// Otherwise, use the value from the CLI. This is definitely
+// Otherwise, use defValue. This is definitely
 // counter-intuitive but it allows the operator admin adjust the
 // number of workers based on their cluster resources. While the
 // author may use the CLI option to specify a suggested
@@ -282,8 +282,8 @@ func getMaxWorkers(gvk schema.GroupVersionKind, defValue int) int {
 	return maxWorkers
 }
 
-// if the WORKER_* environment variable is set, use that value.
-// Otherwise, use the value from the CLI.
+// if the ANSIBLE_VERBOSITY_* environment variable is set, use that value.
+// Otherwise, use defValue.
 func getAnsibleVerbosity(gvk schema.GroupVersionKind, defValue int) int {
 	envVar := strings.ToUpper(strings.Replace(
 		fmt.Sprintf("ANSIBLE_VERBOSITY_%s_%s", gvk.Kind, gvk.Group),