diff --git a/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md b/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md
index df4595c97..c7ab22493 100644
--- a/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md
+++ b/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md
@@ -73,7 +73,7 @@ const (
     // Deletes the object from the key-value store, the garbage collector will delete the dependents in the background.
     DeletePropagationBackground DeletePropagationPolicy = "DeletePropagationBackground"
     // The object exists in the key-value store until the garbage collector deletes all the dependents whose ownerReference.blockOwnerDeletion=true from the key-value store.
-    // API sever will put the "DeletingDependents" finalizer on the object, and sets its deletionTimestamp.
+    // API server will put the "DeletingDependents" finalizer on the object, and sets its deletionTimestamp.
     // This policy is cascading, i.e., the dependents will be deleted with GarbageCollectionSynchronous.
     DeletePropagationForeground DeletePropagationPolicy = "DeletePropagationForeground"
 )
diff --git a/contributors/design-proposals/resource-management/gpu-support.md b/contributors/design-proposals/resource-management/gpu-support.md
index 2e74f4c38..9c58cd8ec 100644
--- a/contributors/design-proposals/resource-management/gpu-support.md
+++ b/contributors/design-proposals/resource-management/gpu-support.md
@@ -125,7 +125,7 @@ the container by the dockertools library.
 
 ### Event flow
 
-This is what happens before and after an user schedules a GPU pod.
+This is what happens before and after a user schedules a GPU pod.
 
 1. Administrator installs a number of Kubernetes nodes with GPUs. The correct
 kernel modules and device nodes under `/dev/` are present.