Update miscellany

Author: ciroque

README.md

@@ -63,7 +63,7 @@ If you are running Kubernetes on-premise and will need to manage your own load b
 
 NLK itself does not perform load balancing. Rather, NLK allows you to manage Service resources within your cluster to update your load balancers, with tooling you are most likely already using. 
 
-<img src="docs/media/nkl-blog-diagram-v1.png" width="768" />
+<img src="docs/media/nlk-blog-diagram-v1.png" width="768" />
 
 ## Getting Started
 
@@ -81,7 +81,7 @@ As with everything Kubernetes, NLK requires RBAC permissions to function properl
 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 NLK are modest. NLK 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.
+The Services and ConfigMap are restricted to a specific namespace (default: "nlk"). The Nodes resource is cluster-wide.
 
 #### Configuration
 
@@ -127,7 +127,7 @@ There is a much more detailed [Installation Reference](docs/README.md) available
 
 6. Check the logs
 
-```kubectl -n nkl get pods | grep deployment | cut -f1 -d" "  | xargs kubectl logs -n nkl --follow $1```
+```kubectl -n nlk get pods | grep deployment | cut -f1 -d" "  | xargs kubectl logs -n nlk --follow $1```
 
 At this point NLK should be up and running. Now would be a great time to go over to the [Installation Reference](docs/README.md) 
 and follow the instructions to deploy a demo application.

docs/DESIGN.md

@@ -44,8 +44,8 @@ adding each `core.ServerUpdateEvent` to the "nlk-synchronizer" queue.
 ### Translator
 
 The Translator is responsible for converting the `core.Event` event into an `nginxClient.UpstreamServer` event.
-This involves filtering out the `core.Event` instances that are not of interest to the controller by accepting only Port names starting with the NklPrefix value (currently _nlk-_).
-The event is then fanned-out based on the defined Ports, one event per defined Port. Each port is then augmented with the Ingress name (the name configured in the Port definition with the NklPrefix value removed), 
+This involves filtering out the `core.Event` instances that are not of interest to the controller by accepting only Port names starting with the NlkPrefix value (currently _nlk-_).
+The event is then fanned-out based on the defined Ports, one event per defined Port. Each port is then augmented with the Ingress name (the name configured in the Port definition with the NlkPrefix value removed), 
 and the list of the Node's IP addresses.
 
 The Translator passes the list of events to the Synchronizer by calling the `AddEvents` method.