diff --git a/cluster/gce/gci/README.md b/cluster/gce/gci/README.md
index 9cec32c2b55..17c02fb03fb 100644
--- a/cluster/gce/gci/README.md
+++ b/cluster/gce/gci/README.md
@@ -79,7 +79,7 @@ following guidelines are proposed for image choice in E2E testing.
     'image' should be used to specify the image.
 
   * To integrate continuously with other container
-    related technologies like runc, containerd, docker and kubernertes, the
+    related technologies like runc, containerd, docker and kubernetes, the
     latest LTS or stable images are preferred. 'image_family' should be used to
     specify the image.
 
diff --git a/staging/src/k8s.io/cri-api/README.md b/staging/src/k8s.io/cri-api/README.md
index 4f80589abfe..cd2c75017d2 100644
--- a/staging/src/k8s.io/cri-api/README.md
+++ b/staging/src/k8s.io/cri-api/README.md
@@ -245,7 +245,7 @@ You can reach the maintainers of this repository at:
 Participation in the Kubernetes community is governed by the [Kubernetes
 Code of Conduct](code-of-conduct.md).
 
-### Contibution Guidelines
+### Contribution Guidelines
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for more information. Please note that [kubernetes/cri-api](https://github.com/kubernetes/cri-api)
 is a readonly mirror repository, all development is done at [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes).
diff --git a/test/e2e/dra/README.md b/test/e2e/dra/README.md
index e22110755d4..5b1ca93865d 100644
--- a/test/e2e/dra/README.md
+++ b/test/e2e/dra/README.md
@@ -26,7 +26,7 @@ release 0.20, build kind from latest main branch sources or use Kind release bin
 
 ### Build kind node image
 
-After building Kubernetes, in Kubernetes source code tree biuld new node image:
+After building Kubernetes, in Kubernetes source code tree build new node image:
 ```bash
 $ kind build node-image --image dra/node:latest $(pwd)
 ```
diff --git a/test/e2e/framework/README.md b/test/e2e/framework/README.md
index f8ed1eff260..2f5e79677fc 100644
--- a/test/e2e/framework/README.md
+++ b/test/e2e/framework/README.md
@@ -4,7 +4,7 @@ The Kubernetes E2E framework simplifies writing Ginkgo tests suites. It's main
 usage is for these tests suites in the Kubernetes repository itself:
 - test/e2e: runs as client for a Kubernetes cluster. The e2e.test binary is
   used for conformance testing.
-- test/e2e_node: runs on the same node as a kublet instance. Used for testing
+- test/e2e_node: runs on the same node as a kubelet instance. Used for testing
   kubelet.
 - test/e2e_kubeadm: test suite for kubeadm.
 
diff --git a/test/kubemark/pre-existing/README.md b/test/kubemark/pre-existing/README.md
index 94a405e96b4..1e6531728dd 100644
--- a/test/kubemark/pre-existing/README.md
+++ b/test/kubemark/pre-existing/README.md
@@ -32,7 +32,7 @@ master.
 ## Requirements
 
 To use the pre-existing provider, the expectation is that there's a kubemark
-master that is rechable at $MASTER_IP. The machine that the kubemark master is
+master that is reachable at $MASTER_IP. The machine that the kubemark master is
 on has to be ssh able from the host that's executing the kubemark scripts. And
 the user on that machine has to be 'kubernetes'.