Update content/en/blog/_posts/xxxx-xx-xx-Fine-grained-SupplementalGroups-control/index.md

Author: everpeace

content/en/blog/_posts/xxxx-xx-xx-Fine-grained-SupplementalGroups-control/index.md

@@ -55,7 +55,7 @@ Thus, the group membership defined in `/etc/group` in the container image for th
 
 ### What's wrong with it?
 
-The _implicitly_ merged group information from `/etc/group` in the container image may cause some concerns particularly in accessing volumes (see [kubernetes/kubernetes#112879](https://issue.k8s.io/112879) for details) because file permission is controlled by uid/gid in Linux. Even worse, the implicit gids from `/etc/group` can not be detected/validated by any policy engines becuase there is no clue for the implicit group information in the manifest. This can also be concern for Kubernetes security.
+The _implicitly_ merged group information from `/etc/group` in the container image may cause some concerns particularly in accessing volumes (see [kubernetes/kubernetes#112879](https://issue.k8s.io/112879) for details) because file permission is controlled by uid/gid in Linux. Even worse, the implicit gids from `/etc/group` can not be detected/validated by any policy engines because there is no clue for the implicit group information in the manifest. This can also be a concern for Kubernetes security.
 
 ## Fine-grined SupplementalGroups control in a Pod: `SupplementaryGroupsPolicy`