update the docker commands for the images

Author: jmrodri

README.md

@@ -48,8 +48,8 @@ this is a big hammer, you could instead just tell the CVO your operator should b
 Build and push your newly built image to a repo:
 ```
 $ make images
-$ docker registry.svc.ci.openshift.org/ocp/4.2:cluster-svcat-apiserver-operator jmrodri/ocp-cluster-svcat-apiserver-operator:xx
-$ docker push jmrodri/ocp-cluster-svcat-apiserver-operator
+$ docker tag registry.svc.ci.openshift.org/ocp/4.2:cluster-svcat-apiserver-operator docker.io/jmrodri/ocp-cluster-svcat-apiserver-operator:latest
+$ docker push docker.io/jmrodri/ocp-cluster-svcat-apiserver-operator:latest
 ```
 and then update the manifest to specify your operator  image:
 ```
@@ -62,7 +62,7 @@ locate the image and change the image and pull policy:
 ```
 to
 ```
-        image: docker.io/jmrodri/ocp-cluster-svcat-apiserver-operator:xx
+        image: docker.io/jmrodri/ocp-cluster-svcat-apiserver-operator:latest
         imagePullPolicy: Always
 ```
 This will cause your dev operator image to be pulled down and deployed.  When you want to deploy a newly built image just scale your operator to zero and right back to one: