Update keps/sig-windows/1981-windows-privileged-container-support/REA…

…DME.md

Co-authored-by: James Sturtevant <jsturtevant@gmail.com>

keps/sig-windows/1981-windows-privileged-container-support/README.md

@@ -327,7 +327,7 @@ Additionally, privileged containers may impact other pod security policies (PSPs
    </td>
    <td>no
    </td>
-   <td>Windows does not have configurable PID/IPC namespaces (unlike Linux). Job objects run in the host 'silo' and will have access to other other host processes. Because on Windows this setting is per-container instead of being Pod-wide and also because future plans include the improvements to schedule pods container both normal and 'privileged'/HostProcess containers in the same Pod we will not enforce setting this pod security flag for HostProcess containers.
+   <td>Windows does not have configurable PID/IPC namespaces (unlike Linux). Job objects run in the host 'silo' and will have access to other host processes. Because on Windows this setting is per-container instead of being Pod-wide and also because future plans include the improvements to schedule pods container both normal and 'privileged'/HostProcess containers in the same Pod we will not enforce setting this pod security flag for HostProcess containers.
    </td>
    <td>N/A
    </td>