github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-02 00:07:50 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #121297 from calvinballing/spellcheck-markdown

Browse Source 
Fix typos in markdown
This commit is contained in:
Kubernetes Prow Robot 2023-10-25 13:18:26 +02:00 committed by GitHub
commit 4294c35fc9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
cluster/gce/gci/README.md
View File

@ -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.

2
staging/src/k8s.io/cri-api/README.md
View File

@ -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).

2
test/e2e/dra/README.md
View File

@ -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)
```

2
test/e2e/framework/README.md
View File

@ -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.

2
test/kubemark/pre-existing/README.md
View File

@ -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'.