message: Fix tiller-proxy dev docs
diff: @@ -51,7 +51,7 @@ eval $(minikube docker-env)
  Note: By default, Kubeapps will try to fetch the latest version of the image so in order to make this workflow work in Minikube you will need to update the imagePullPolicy first:
  ```
  -kubectl patch deployment kubeapps-tiller-proxy -n kubeapps --type=json -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/imagePullPolicy", "value": "IfNotPresent"}]'
  +kubectl patch deployment kubeapps-internal-tiller-proxy -n kubeapps --type=json -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/imagePullPolicy", "value": "IfNotPresent"}]'
  ```
  The easiest way to create the `tiller-proxy` image is execute the Makefile task to do so:
  @@ -63,13 +63,13 @@ VERSION=dev make kubeapps/tiller-proxy
  This will generate an image `kubeapps/tiller-proxy:dev` that you can use in the current deployment:
  ```
  -kubectl set image -n kubeapps deployment kubeapps-tiller-proxy proxy=kubeapps/tiller-proxy:dev
  +kubectl set image -n kubeapps deployment kubeapps-internal-tiller-proxy proxy=kubeapps/tiller-proxy:dev
  ```
  For further redeploys you can change the version to deploy a different tag or rebuild the same image and restart the pod executing:
  ```
  -kubectl delete pod -n kubeapps -l app=kubeapps-tiller-proxy
  +kubectl delete pod -n kubeapps -l app=kubeapps-internal-tiller-proxy
  ```
  Note: If you using a cloud provider to develop the service you will need to retag the image and push it to a public registry.
  