Merge pull request #39324 from reylejano/followup-PR-38673

Updated concepts/workloads/pods/_index.html as followup to PR 38673

Author: k8s-ci-robot

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

@@ -296,22 +296,22 @@ Your {{< glossary_tooltip text="container runtime" term_id="container-runtime" >
 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
+### Linux priviledged 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
+### Windows priviledged 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
 to perform administrative tasks as is done with Linux privileged containers. In order to use this feature, the
-`WindowsHostProcessContainers`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) must be enabled.
+`WindowsHostProcessContainers` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) must be enabled.
 
 
 ## Static Pods