Merge pull request #20326 from rmohta/patch-1

Moved Desired and Current headers to rs section

Author: k8s-ci-robot

content/en/docs/concepts/workloads/controllers/deployment.md

@@ -89,9 +89,8 @@ In this example:
     ```
     When you inspect the Deployments in your cluster, the following fields are displayed:
 
-      * `NAME` lists the names of the Deployments in the cluster.
-      * `DESIRED` displays the desired number of _replicas_ of the application, which you define when you create the Deployment. This is the _desired state_.
-      * `CURRENT` displays how many replicas are currently running.
+      * `NAME` lists the names of the Deployments in the namespace.
+      * `READY` displays how many replicas of the application are available to your users. It follows the pattern ready/desired.
       * `UP-TO-DATE` displays the number of replicas that have been updated to achieve the desired state.
       * `AVAILABLE` displays how many replicas of the application are available to your users.
       * `AGE` displays the amount of time that the application has been running.
@@ -116,6 +115,14 @@ In this example:
     NAME                          DESIRED   CURRENT   READY   AGE
     nginx-deployment-75675f5897   3         3         3       18s
     ```
+    ReplicaSet output shows the following fields:
+    
+      * `NAME` lists the names of the ReplicaSets in the namespace.
+      * `DESIRED` displays the desired number of _replicas_ of the application, which you define when you create the Deployment. This is the _desired state_.
+      * `CURRENT` displays how many replicas are currently running.
+      * `READY` displays how many replicas of the application are available to your users.
+      * `AGE` displays the amount of time that the application has been running.
+      
     Notice that the name of the ReplicaSet is always formatted as `[DEPLOYMENT-NAME]-[RANDOM-STRING]`. The random string is
     	randomly generated and uses the pod-template-hash as a seed.