diff --git a/contributors/design-proposals/apps/stateful-apps.md b/contributors/design-proposals/apps/stateful-apps.md
index 5f965b77d..9a6cbf99e 100644
--- a/contributors/design-proposals/apps/stateful-apps.md
+++ b/contributors/design-proposals/apps/stateful-apps.md
@@ -346,7 +346,7 @@ Requested features:
 
 * Jobs can be used to perform a run-once initialization of the cluster
 * Init containers can be used to prime PVs and config with the identity of the pod.
-* Templates and how fields are overriden in the resulting object should have broad alignment
+* Templates and how fields are overridden in the resulting object should have broad alignment
 * DaemonSet defines the core model for how new controllers sit alongside replication controller and
   how upgrades can be implemented outside of Deployment objects.
 
diff --git a/contributors/design-proposals/auth/runas-groupid.md b/contributors/design-proposals/auth/runas-groupid.md
index d114f9aa4..b05b29507 100644
--- a/contributors/design-proposals/auth/runas-groupid.md
+++ b/contributors/design-proposals/auth/runas-groupid.md
@@ -11,7 +11,7 @@ As a Kubernetes User, we should be able to specify both user id and group id for
 inside a pod on a per Container basis, similar to how docker allows that using docker run options `-u, 
 --user="" Username or UID (format: <name|uid>[:<group|gid>]) format`.
 
-PodSecurityContext allows Kubernetes users to specify RunAsUser which can be overriden by RunAsUser
+PodSecurityContext allows Kubernetes users to specify RunAsUser which can be overridden by RunAsUser
 in SecurityContext on a per Container basis. There is no equivalent field for specifying the primary
 Group of the running container.