diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 99e3094c18..8601ddae5d 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -152,7 +152,8 @@ different Kubernetes components.
 | `ProbeTerminationGracePeriod` | `false` | Alpha | 1.21 | |
 | `ProcMountType` | `false` | Alpha | 1.12 | |
 | `QOSReserved` | `false` | Alpha | 1.11 | |
-| `RemainingItemCount` | `false` | Alpha | 1.15 | |
+| `RemainingItemCount` | `false` | Alpha | 1.15 | 1.15 |
+| `RemainingItemCount` | `true` | Beta | 1.16 | |
 | `RemoveSelfLink` | `false` | Alpha | 1.16 | 1.19 |
 | `RemoveSelfLink` | `true` | Beta | 1.20 | |
 | `RotateKubeletServerCertificate` | `false` | Alpha | 1.7 | 1.11 |
diff --git a/content/en/docs/reference/using-api/api-concepts.md b/content/en/docs/reference/using-api/api-concepts.md
index da41e7c4c9..d87e4c25de 100644
--- a/content/en/docs/reference/using-api/api-concepts.md
+++ b/content/en/docs/reference/using-api/api-concepts.md
@@ -192,7 +192,21 @@ For example, if there are 1,253 pods on the cluster and the client wants to rece
    }
    ```
 
-Note that the `resourceVersion` of the list remains constant across each request, indicating the server is showing us a consistent snapshot of the pods. Pods that are created, updated, or deleted after version `10245` would not be shown unless the user makes a list request without the `continue` token.  This allows clients to break large requests into smaller chunks and then perform a watch operation on the full set without missing any updates.
+Note that the `resourceVersion` of the list remains constant across each request, 
+indicating the server is showing us a consistent snapshot of the pods. Pods that 
+are created, updated, or deleted after version `10245` would not be shown unless 
+the user makes a list request without the `continue` token.  This allows clients 
+to break large requests into smaller chunks and then perform a watch operation 
+on the full set without missing any updates. 
+
+`remainingItemCount` is the number of subsequent items in the list which are not 
+included in this list response. If the list request contained label or field selectors, 
+then the number of remaining items is unknown and the API server does not include 
+a `remainingItemCount` field in its response. If the list is complete (either 
+because it is not chunking or because this is the last chunk), then there are no 
+more remaining items and the API server does not include a `remainingItemCount` 
+field in its response. The intended use of the `remainingItemCount` is estimating 
+the size of a collection.
 
 
 ## Receiving resources as Tables