document privileged containers as GC

Author: dshebib

content/en/docs/concepts/workloads/pods/_index.md

@@ -289,13 +289,20 @@ section.
 
 ## Privileged mode for containers
 
-{{< feature-state for_k8s_version="v1.26" state="stable" >}}
+Any container in a pod can run in privileged mode to use operating system administrative capabilities
+that would otherwise be inaccessible. This is available for both Windows and Linux.
+
+### Linux containers
 
 In Linux, any container in a Pod can enable privileged mode using the `privileged` (Linux) flag
 on the [security context](/docs/tasks/configure-pod-container/security-context/) of the
 container spec. This is useful for containers that want to use operating system administrative
 capabilities such as manipulating the network stack or accessing hardware devices.
 
+### Windows containers
+
+{{< feature-state for_k8s_version="v1.26" state="stable" >}}
+
 In Windows, you can create a [Windows HostProcess pod](/docs/tasks/configure-pod-container/create-hostprocess-pod)
 by setting the `windowsOptions.hostProcess` flag on the security context of the pod spec. All containers in these
 pods must run as Windows HostProcess containers. HostProcess pods run directly on the host and can also be used