diff --git a/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md b/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md
index a916ac7ded..54dc3afef8 100644
--- a/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md
+++ b/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md
@@ -205,8 +205,7 @@ policy for the embedded template to "`Never`".
 
 ## Job Termination and Cleanup
 
-When a Job completes, no more Pods are created, but the Pods are not deleted either.  Since they are terminated,
-they don't show up with `kubectl get pods`, but they will show up with `kubectl get pods -a`.  Keeping them around
+When a Job completes, no more Pods are created, but the Pods are not deleted either.  Keeping them around
 allows you to still view the logs of completed pods to check for errors, warnings, or other diagnostic output.
 The job object also remains after it is completed so that you can view its status.  It is up to the user to delete
 old jobs after noting their status.  Delete the job with `kubectl` (e.g. `kubectl delete jobs/pi` or `kubectl delete -f ./job.yaml`). When you delete the job using `kubectl`, all the pods it created are deleted too.