summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorQingsong Fan <fanqingsong@ghostcloud.cn>2018-03-21 15:35:29 +0800
committerQingsong Fan <fanqingsong@ghostcloud.cn>2018-03-21 15:35:29 +0800
commit1858ef9b03a8ea53cc87582444d0fe566af8b111 (patch)
tree2786f7cec023cf3d0b0d1fe03c69cd404a214e98
parentcee5f0bf724a0aba657cb4a934e53cfe7ca5f3bc (diff)
fix some typo
-rw-r--r--contributors/design-proposals/api-machinery/synchronous-garbage-collection.md2
-rw-r--r--contributors/design-proposals/resource-management/gpu-support.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md b/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md
index df4595c9..c7ab2249 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 2e74f4c3..9c58cd8e 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.