Further update docs to reflect changes kubectl run

docs/user-guide/debugging-services.md

@@ -57,9 +57,10 @@ spec:
     - sleep
     - "1000000"
 EOF
-pods/busybox-sleep
+pod "busybox-sleep" created
 ```
 
+Note that `kubectl` commands will print the type and name of the resource created or mutated, which can then be used in subsequent commands. 
 Now, when you need to run a command (even an interactive shell) in a `Pod`-like
 context, use:
 

docs/user-guide/docker-cli-to-kubectl.md

@@ -26,6 +26,13 @@ With kubectl:
 # start the pod running nginx
 $ kubectl run --image=nginx nginx-app --port=80 --env="DOMAIN=cluster"
 deployment "nginx-app" created
+```
+
+`kubectl run` creates a Deployment named "nginx" on Kubernetes cluster >= v1.2. If you are running older versions, it creates replication controllers instead.
+If you want to obtain the old behavior, use `--generator=run/v1` to create replication controllers. See [`kubectl run`](/docs/user-guide/kubectl/kubectl_run/) for more details. 
+Note that `kubectl` commands will print the type and name of the resource created or mutated, which can then be used in subsequent commands. Now, we can expose a new Service with the deployment created above:
+
+```shell
 # expose a port through with a service
 $ kubectl expose deployment nginx-app --port=80 --name=nginx-http
 service "nginx-http" exposed

docs/user-guide/pods/single-container.md

@@ -35,6 +35,7 @@ $ kubectl run NAME
 
 Where:
 
+* `kubectl run` creates a Deployment named "nginx" on Kubernetes cluster >= v1.2. If you are running older versions, it creates replication controllers instead. If you want to obtain the old behavior, use `--generator=run/v1` to create replication controllers. See [`kubectl run`](/docs/user-guide/kubectl/kubectl_run/) for more details. 
 * `NAME` (required) is the name of the container to create. This value is also
   applied as the name of the Deployment, and as the prefix of the
   pod name. For example: