Remove trace of "kubectl stop"

Remove doc and use of "kubectl stop" since it's deprecated.

docs/devel/flaky-tests.md

@@ -87,10 +87,10 @@ done
 grep "Exited ([^0])" output.txt
 ```
 
-Eventually you will have sufficient runs for your purposes. At that point you can stop and delete the replication controller by running:
+Eventually you will have sufficient runs for your purposes. At that point you can delete the replication controller by running:
 
 ```sh
-kubectl stop replicationcontroller flakecontroller
+kubectl delete replicationcontroller flakecontroller
 ```
 
 If you do a final check for flakes with `docker ps -a`, ignore tasks that exited -1, since that's what happens when you stop the replication controller.

docs/getting-started-guides/coreos/bare_metal_offline.md

@@ -699,7 +699,7 @@ List Kubernetes
 
 Kill all pods:
 
-    for i in `kubectl get pods | awk '{print $1}'`; do kubectl stop pod $i; done
+    for i in `kubectl get pods | awk '{print $1}'`; do kubectl delete pod $i; done
 
 
 <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->

docs/getting-started-guides/logging.md

@@ -123,10 +123,10 @@ root       479  0.0  0.0   4348   812 ?        S    00:05   0:00 sleep 1
 root       480  0.0  0.0  15572  2212 ?        R    00:05   0:00 ps aux
 ```
 
-What happens if for any reason the image in this pod is killed off and then restarted by Kubernetes? Will we still see the log lines from the previous invocation of the container followed by the log lines for the started container? Or will we lose the log lines from the original container’s execution and only see the log lines for the new container? Let’s find out. First let’s stop the currently running counter.
+What happens if for any reason the image in this pod is killed off and then restarted by Kubernetes? Will we still see the log lines from the previous invocation of the container followed by the log lines for the started container? Or will we lose the log lines from the original container’s execution and only see the log lines for the new container? Let’s find out. First let’s delete the currently running counter.
 
 ```console
-$ kubectl stop pod counter
+$ kubectl delete pod counter
 pods/counter
 ```
 

docs/user-guide/simple-nginx.md

@@ -59,10 +59,10 @@ You can also see the replication controller that was created:
 kubectl get rc
 ```
 
-To stop the two replicated containers, stop the replication controller:
+To stop the two replicated containers, delete the replication controller:
 
 ```bash
-kubectl stop rc my-nginx
+kubectl delete rc my-nginx
 ```
 
 ### Exposing your pods to the internet.