diff --git a/keps/sig-apps/2879-ready-pods-job-status/README.md b/keps/sig-apps/2879-ready-pods-job-status/README.md
index 14e2124cfe54..e33230dea381 100644
--- a/keps/sig-apps/2879-ready-pods-job-status/README.md
+++ b/keps/sig-apps/2879-ready-pods-job-status/README.md
@@ -39,7 +39,7 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
 - [x] (R) KEP approvers have approved the KEP status as `implementable`
 - [x] (R) Design details are appropriately documented
 - [ ] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
-  - [ ] e2e Tests for all Beta API Operations (endpoints)
+  - [x] e2e Tests for all Beta API Operations (endpoints)
   - [ ] (R) Ensure GA e2e tests for meet requirements for [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
   - [ ] (R) Minimum Two Week Window for GA e2e tests to prove flake free
 - [x] (R) Graduation criteria is in place
@@ -352,7 +352,7 @@ Pod created.
   In other words, `Job.status.ready` provides as the same behavior as
   `Job.status.running` with the advantage of it being configurable.
 
-- We considered explore different batch periods for regular pod updates versus
+- We considered exploring different batch periods for regular pod updates versus
   finished pod updates, so we can do less pod readiness updates without
   compromising how fast we can declare a job finished.