#3 - some documentation improvements highlighted by @anjaliguptaz (#29)

README.md

@@ -31,8 +31,10 @@ The sort of HealthChecks one could run with Active-Monitor are:
 - verify KIAM agent by running aws sts get-caller-identity on all available nodes
 
 ## Dependencies
+* [Go Language tools](golang.org)
 * Kubernetes command line tool (kubectl)
 * Access to Kubernetes Cluster as specified in `~/.kube/config`
+  * Easiest option is to install [minikube](https://minikube.sigs.k8s.io/docs/start/) and ensure that `kubectl version` returns client and server info
 * [Argo Workflows Controller](https://github.com/argoproj/argo)
 
 ## Installation Guide
@@ -151,9 +153,9 @@ Then visit: [http://localhost:2112/metrics](http://localhost:2112/metrics)
 
 Active-Monitor, by default, exports following Promethus metrics:
 
-- `healthcheck_success_count` - The total number of successful monitor resources
-- `healthcheck_error_count` - The total number of errored monitor resources
-- `healthcheck_runtime_seconds` - Time taken for the workflow to complete
+- `healthcheck_success_count` - The total number of successful healthcheck resources
+- `healthcheck_error_count` - The total number of erred healthcheck resources
+- `healthcheck_runtime_seconds` - Time taken for the healthcheck's workflow to complete
 
 Active-Monitor also supports custom metrics. For this to work, your workflow should export a global parameter. The parameter will be programmatically available in the completed workflow object under: `workflow.status.outputs.parameters`.