diff --git a/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/features-benefits.md b/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/features-benefits.md
index ac55982f881b..494e2d4a745e 100644
--- a/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/features-benefits.md
+++ b/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/features-benefits.md
@@ -235,10 +235,10 @@ Desktop Linux VM (e.g., 100000->165535).
 
 Moreover, each container gets an exclusive range of real user-IDs in the Linux
 VM (e.g., container 0 could get mapped to 100000->165535, container 2 to
-165536->231071, container 3 to 231072->296607, and so on). Same applies to
+165536->231071, container 3 to 231072->296607, and so on). The same applies to
 group-IDs. In addition, if a container is stopped and restarted, there is no
-guarantee it will receive the same mapping as before. This by design and further
-improves security.
+guarantee it will receive the same mapping as before. This is by design and
+further improves security.
 
 However the above presents a problem when mounting Docker volumes into
 containers, as the files written to such volumes will have the real