diff --git a/docs/contributor/ladder.md b/docs/contributor/ladder.md
index 5ffde51b..253710fb 100644
--- a/docs/contributor/ladder.md
+++ b/docs/contributor/ladder.md
@@ -35,7 +35,7 @@ Description: A Contributor contributes directly to the project and adds value to
   * Report and sometimes resolve issues
   * Occasionally submit PRs
   * Contribute to the documentation
-  * Show up at meetings, takes notes
+  * Show up at meetings, take notes
   * Answer questions from other community members
   * Submit feedback on issues and PRs
   * Test releases and patches and submit reviews
diff --git a/docs/developers/scheduling.md b/docs/developers/scheduling.md
index 71053273..f58fa4d2 100644
--- a/docs/developers/scheduling.md
+++ b/docs/developers/scheduling.md
@@ -4,12 +4,11 @@ title: Scheduler Policy
 
 ## Summary
 
-Current in a cluster with many GPU nodes, nodes are not `binpack` or `spread` when making scheduling decisions, nor are GPU cards `binpack` or `spread` when using vGPU.
+Currently in a cluster with many GPU nodes, nodes are not `binpack` or `spread` when making scheduling decisions, nor are GPU cards `binpack` or `spread` when using vGPU.
 
 ## Proposal
 
-We add a `node-scheduler-policy` and `gpu-scheduler-policy` to config, then scheduler to use this policy can impl node `binpack` or `spread` or GPU `binpack` or `spread`. and
-use can set Pod annotation to change this default policy, use `hami.io/node-scheduler-policy` and `hami.io/gpu-scheduler-policy` to overlay scheduler config.
+We add a `node-scheduler-policy` and `gpu-scheduler-policy` to config, then the scheduler can use this policy to implement node `binpack` or `spread` or GPU `binpack` or `spread`. Users can also set Pod annotation to change this default policy, use `hami.io/node-scheduler-policy` and `hami.io/gpu-scheduler-policy` to overlay scheduler config.
 
 ### User Stories