summaryrefslogtreecommitdiff
path: root/contributors
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2022-09-19 08:17:18 -0700
committerGitHub <noreply@github.com>2022-09-19 08:17:18 -0700
commit3868a8536636d0a93e3755810f15d9b57098531f (patch)
tree72d04b033285b59618ad10ece0842de2426677e1 /contributors
parente1bef6b4c1140971c1dde6b6f8b42c57f6309990 (diff)
parent284ba22f05121d256b71cef09eb14a6f77fc60df (diff)
Merge pull request #6883 from oscr/the-the
grammar: removed doubles of the word "the"
Diffstat (limited to 'contributors')
-rw-r--r--contributors/devel/sig-node/e2e-node-tests.md2
-rw-r--r--contributors/devel/sig-testing/writing-good-conformance-tests.md2
-rw-r--r--contributors/guide/non-code-contributions.md2
3 files changed, 3 insertions, 3 deletions
diff --git a/contributors/devel/sig-node/e2e-node-tests.md b/contributors/devel/sig-node/e2e-node-tests.md
index f212957c..bbfbdee7 100644
--- a/contributors/devel/sig-node/e2e-node-tests.md
+++ b/contributors/devel/sig-node/e2e-node-tests.md
@@ -340,7 +340,7 @@ Some topology manager tests require minimal knowledge of the host topology in or
The required information is to which NUMA node in the system are the SRIOV device attached to.
The test code tries to autodetect the information it needs, skipping the relevant tests if the autodetection fails.
-You can override the autodetection adding annotations to the the config map like this example:
+You can override the autodetection adding annotations to the config map like this example:
```yaml
metadata:
annotations:
diff --git a/contributors/devel/sig-testing/writing-good-conformance-tests.md b/contributors/devel/sig-testing/writing-good-conformance-tests.md
index dbddf4b0..6830b660 100644
--- a/contributors/devel/sig-testing/writing-good-conformance-tests.md
+++ b/contributors/devel/sig-testing/writing-good-conformance-tests.md
@@ -7,7 +7,7 @@ way.
Conformance tests are promoted from existing e2e tests which have
been proven to be stable and "non-flaky".
-Please read the the ["Writing good e2e tests"](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/writing-good-e2e-tests.md) guide as a supplement to this document.
+Please read the ["Writing good e2e tests"](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/writing-good-e2e-tests.md) guide as a supplement to this document.
### Requirements ###
diff --git a/contributors/guide/non-code-contributions.md b/contributors/guide/non-code-contributions.md
index 9143fb30..11813bac 100644
--- a/contributors/guide/non-code-contributions.md
+++ b/contributors/guide/non-code-contributions.md
@@ -3,7 +3,7 @@ title: "Non-code Contributions"
weight: 11
description: |
Looking for a good entrance into the project? or to do something different?
- There are many ways to contribute to the the Kubernetes project without having
+ There are many ways to contribute to the Kubernetes project without having
to have coding experience: issue triage, writing documentation, joining the
release team and much more.
---