From fb8eb1a3c93d210f4be39e90556dd13fd777020a Mon Sep 17 00:00:00 2001
From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
Date: Thu, 14 Dec 2023 14:23:37 +0000
Subject: [PATCH] word-fix (#18921)

---
 .../hardened-desktop/enhanced-container-isolation/_index.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/desktop/hardened-desktop/enhanced-container-isolation/_index.md b/content/desktop/hardened-desktop/enhanced-container-isolation/_index.md
index 2398faa072..d567e1ff2e 100644
--- a/content/desktop/hardened-desktop/enhanced-container-isolation/_index.md
+++ b/content/desktop/hardened-desktop/enhanced-container-isolation/_index.md
@@ -136,7 +136,7 @@ The following output displays:
 
 This indicates that the container's root user (0) maps to unprivileged user
 (100000) in the Docker Desktop VM, and that the mapping extends for a range of
-64K user-IDs. With If a container process were to escape the container, it would
+64K user-IDs. If a container process were to escape the container, it would
 find itself without privileges at the VM level. The user-ID mapping varies with
 each new container, as each container gets an exclusive range of host User-IDs
 for isolation. User-ID mapping is automatically managed by Docker Desktop. For