Updates README

Author: ciroque

README.md

@@ -11,69 +11,86 @@ The NGINX K8s Loadbalancer, or _NKL_, is a Kubernetes controller that provides T
 
 ## Requirements
 
-### Who needs NKL?
+[//]: # (### Who needs NKL?)
 
-- [ ] If you find yourself living in a world where Kubernetes is running on-premise instead of a cloud provider, you might need NKL.
-- [ ] If you want exceptional, best-in-class load-balancing for your Kubernetes applications, you might need NKL.
-- [ ] If you want the ability to manage your load-balancing configuration with the same tools you use to manage your Kubernetes cluster, you might need NKL.
+[//]: # ()
+[//]: # (- [ ] If you find yourself living in a world where Kubernetes is running on-premise instead of a cloud provider, you might need NKL.)
+
+[//]: # (- [ ] If you want exceptional, best-in-class load-balancing for your Kubernetes clusters by using NGINX Plus, you might need NKL.)
+
+[//]: # (- [ ] If you want the ability to manage your load-balancing configuration with the same tools you use to manage your Kubernetes cluster, you might need NKL.)
+
+### What you will need
+
+- [ ] A Kubernetes cluster running on-premise.
+- [ ] One or more NGINX Plus hosts running outside your Kubernetes cluster (NGINX Plus hosts must have the ability to route traffic to the cluster).
+
+There is a more detailed [Installation Guide](docs/InstallationGuide.md) available in the `docs/` directory.
 
 ### Why NKL?
 
 NKL provides a simple, easy-to-manage way to automate load balancing for your Kubernetes applications by leveraging NGINX Plus hosts running outside your cluster.
 
 NKL installs easily, has a small footprint, and is easy to configure and manage.
 
-? {{review for embetterment}}: NKL does not require any specific domain knowledge for configuration, though you will have to understand NGINX configuration to get the most out of this solution. There is thorough documentation available about these specifics in the `docs/` directory.
+NKL does not require learning a custom object model, you only have to understand NGINX configuration to get the most out of this solution. 
+There is thorough documentation available with the specifics in the `docs/` directory.
 
 ### What does NKL do?
 
 tl;dr:
 
 _**NKL is a Kubernetes controller that monitors Services and Nodes in your cluster, and then sends API calls to an external NGINX Plus server to manage NGINX Plus Upstream servers automatically.**_
 
-That's all well and good, but what does that mean? Well, Kubernetes clusters require some tooling to handling routing traffic from the outside world (e.g.: the Internet, corporate network, etc.) to the cluster. 
-This is typically done with a load balancer. The load balancer is responsible for routing traffic to the appropriate Kubernetes worker node which then forwards the traffic to the appropriate Service / Pod.
+That's all well and good, but what does it mean? Kubernetes clusters require some tooling to handling routing traffic from the outside world (e.g.: the Internet, corporate network, etc.) to the cluster. 
+This is typically done with a load balancer. The load balancer is responsible for routing traffic to the appropriate worker node which then forwards the traffic to the appropriate Service / Pod.
 
 If you are using a hosted web solution -- Digital Ocean, AWS, Azure, etc. -- you can use the cloud provider's load balancer service. Those services will create a load balancer for you. 
 You can use the cloud provider's API to manage the load balancer, or you can use the cloud provider's web console.
 
-However, if you checked the first box above, you are running Kubernetes on-premise and will need to manage your own load balancer. This is where NKL comes in.
+If you are running Kubernetes on-premise and will need to manage your own load balancer, NKL can help.
 
-NKL itself does not perform load balancing. Instead, NKL allows you to manage resources within your cluster and have the load balancers automatically be updated to support those changes, with tooling you are most likely already using. 
+NKL itself does not perform load balancing. Rather, NKL allows you to manage Service resources within your cluster to update your load balancers, with tooling you are most likely already using. 
 
 ## Getting Started
 
 There are few bits of administrivia to get out of the way before you can start leveraging NKL for your load balancing needs.
 
-As noted above, NKL really shines when you have one or more Kubernetes clusters running on-premise. With this in place,
+As noted above, NKL is intended for when you have one or more Kubernetes clusters running on-premise. In addition to this,
 you need to have at least one NGINX Plus host running outside your cluster (Please refer to the [Roadmap](#Roadmap) for information about other load balancer servers). 
 
-You will not need to clone this repo to use NKL. Instead, you can install NKL using the included Manifest files (just copy the `deployments/` directory), which pulls the NKL image from the Container Registry.
+### Deployment
 
-### RBAC
+#### RBAC
 
 As with everything Kubernetes, NKL requires RBAC permissions to function properly. The necessary resources are defined in the various YAML files in `deployement/rbac/`.
 
 For convenience, two scripts are included, `apply.sh`, and `unapply.sh`. These scripts will apply or remove the RBAC resources, respectively.
 
-The permissions required by NKL are modest. NKL requires the ability to read Resources via shared informers; the resources are Services, Nodes, and ConfigMaps. 
+The permissions required by NKL are modest. NKL requires the ability to read Resources via shared informers; the resources are Services, Nodes, and ConfigMaps.
 The Services and ConfigMap are restricted to a specific namespace (default: "nkl"). The Nodes resource is cluster-wide.
 
-### Configuration
+#### Configuration
 
-NKL is configured via a ConfigMap, the default settings are found in `deployment/configmap.yaml`. Presently there is a single configuration value exposed in the ConfigMap, `nginx-hosts`. 
+NKL is configured via a ConfigMap, the default settings are found in `deployment/configmap.yaml`. Presently there is a single configuration value exposed in the ConfigMap, `nginx-hosts`.
 This contains a comma-separated list of NGINX Plus hosts that NKL will maintain.
 
 You will need to update this ConfigMap to reflect the NGINX Plus hosts you wish to manage.
 
 If you were to deploy the ConfigMap and start NKL without updating the `nginx-hosts` value, don't fear; the ConfigMap resource is monitored for changes and NKL will update the NGINX Plus hosts accordingly when the resource is changed, no restart required.
 
-### Deployment
-
 There is an extensive [Installation Guide](docs/InstallationGuide.md) available in the `docs/` directory. 
 Please refer to that for detailed instructions on how to deploy NKL and run a demo application.
 
-To get NKL up and running in ten steps or fewer, follow these instructions (NOTE, all the aforementioned prerequisites must be met for this to work):
+#### Versioning
+
+Versioning is a work in progress. The CI/CD pipeline is being developed and will be used to build and publish NKL images to the Container Registry. 
+Once in place, semantic versioning will be used for published images.
+
+#### Deployment Steps
+
+To get NKL up and running in ten steps or fewer, follow these instructions (NOTE, all the aforementioned prerequisites must be met for this to work). 
+There is a much more detailed [Installation Guide](docs/InstallationGuide.md) available in the `docs/` directory.
 
 1. Clone this repo (optional, you can simply copy the `deployments/` directory)