Small improvements

README.md

@@ -15,7 +15,7 @@ a single TCP port, or an HTTP(S) endpoint. As a result, our use case just isn't
 We wrote health-checker so that we could run a daemon on the server that reports the true health of the server by
 attempting to open a TCP connection to more than one port when it receives an inbound HTTP request on the given listener.
 
-Using the `--script` -option, the `health-checker` can be extended to check many other targets. One concrete exeample is monitoring
+Using the `--script` -option, the `health-checker` can be extended to check many other targets. One concrete example is monitoring
 `ZooKeeper` node status during rolling deployment. Just polling the `ZooKeeper`'s TCP client port doesn't necessarily guarantee
 that the node has (re-)joined the cluster. Using the `health-check` with a custom script target, we can 
 [monitor ZooKeeper](https://zookeeper.apache.org/doc/r3.4.8/zookeeperAdmin.html#sc_monitoring) using the 

server/server.go

@@ -61,11 +61,15 @@ func runChecks(opts *options.Options) *httpResponse {
 	for _, script := range opts.Scripts {
 		waitGroup.Add(1)
 		go func(script options.Script) {
+
+			defer waitGroup.Done()
+
 			logger.Infof("Executing '%v' with a timeout of %v seconds...", script, opts.ScriptTimeout)
 
 			timeout := time.Second * time.Duration(opts.ScriptTimeout)
 
 			ctx, cancel := context.WithTimeout(context.Background(), timeout)
+
 			defer cancel()
 
 			cmd := exec.CommandContext(ctx, script.Name, script.Args...)
@@ -79,8 +83,6 @@ func runChecks(opts *options.Options) *httpResponse {
 			} else {
 				logger.Infof("Script %v successful", script)
 			}
-
-			waitGroup.Done()
 		}(script)
 	}