diff --git a/committee-code-of-conduct/incident-process.md b/committee-code-of-conduct/incident-process.md index c68d1bed1..007f46521 100644 --- a/committee-code-of-conduct/incident-process.md +++ b/committee-code-of-conduct/incident-process.md @@ -3,7 +3,7 @@ title: "Code of Conduct Committee Incident Reporting and Response Process" weight: 550 aliases: [ "/coc-process" ] description: | - Overview of the the Code of Conduct Committee's workflow when receiving and + Overview of the Code of Conduct Committee's workflow when receiving and responding to an incident report. --- diff --git a/communication/discuss-guidelines.md b/communication/discuss-guidelines.md index dded2ff6d..11b5d992c 100644 --- a/communication/discuss-guidelines.md +++ b/communication/discuss-guidelines.md @@ -47,7 +47,7 @@ throughout the project, and includes all communication mediums. ## Privacy Policy -Discuss adheres to the the [Linux Foundation Privacy Policy]. +Discuss adheres to the [Linux Foundation Privacy Policy]. ## Admins diff --git a/communication/mailing-list-guidelines.md b/communication/mailing-list-guidelines.md index 50c3713a8..f6a945004 100644 --- a/communication/mailing-list-guidelines.md +++ b/communication/mailing-list-guidelines.md @@ -136,7 +136,7 @@ list, and again for the members mailing list. Click **Next**. -2. Fill out the the **Choose privacy settings** with these options: +2. Fill out the **Choose privacy settings** with these options: | Field | Leads ML value | Members ML value | | --- | --- | --- | diff --git a/communication/meeting-notes-archive/201902-201911_Community_Meeting_Notes.md b/communication/meeting-notes-archive/201902-201911_Community_Meeting_Notes.md index 29247086b..df46b73ce 100644 --- a/communication/meeting-notes-archive/201902-201911_Community_Meeting_Notes.md +++ b/communication/meeting-notes-archive/201902-201911_Community_Meeting_Notes.md @@ -2320,7 +2320,7 @@ Twitter | [Sep 19th](https://twitter.com/stephenaugustus/status/1174797710043430 * APAC and EU moderators needed the most * Shoutouts * Akutz - Major #shoutout to Katharine Berry (@Katharine) for fixing a UX bug within just a few hours of me mentioning it - [https://kubernetes.slack.com/archives/C09QZ4DQB/p1550863111161400](https://kubernetes.slack.com/archives/C09QZ4DQB/p1550863111161400). Ain’t no service like SIG-Testing service, cause SIG-Testing service don’t stop! - * spiffxp - shoutout to Thomas Runyon (@runyontr) for [https://github.com/kubernetes/kubernetes/pull/72939](https://github.com/kubernetes/kubernetes/pull/72939) allowing us to run eg: `make test-cmd WHAT=deployment` to run just the the deployment cli tests, same sort of thing you can do with `make test` and `make test-integration` + * spiffxp - shoutout to Thomas Runyon (@runyontr) for [https://github.com/kubernetes/kubernetes/pull/72939](https://github.com/kubernetes/kubernetes/pull/72939) allowing us to run eg: `make test-cmd WHAT=deployment` to run just the deployment cli tests, same sort of thing you can do with `make test` and `make test-integration` * bentheelder - shoutout to @gsaenger for writing a wonderful new message for the welcome bot! looking forward to seeing this in more places - ([https://github.com/kubernetes-sigs/contributor-playground/pull/229#issuecomment-466711312](https://github.com/kubernetes-sigs/contributor-playground/pull/229#issuecomment-466711312)) * bentheelder - Shoutout to @jeefy for the really shiny and useful looking structured Kubernetes release notes viewer demo in today's #sig-release meeting, looking forward to seeing more about this! * Maria - shoutout to Silvia Moura Pina (@smourapina) for putting together a workflow to enable the CI signal subteam of the release team keep on top of flagging issues from e2e tests and coordinate follow-ups and to Jorge Alarcon (@Jorge) for spotting an opportunity to offer broader transparency to what the CI signal team is working on, suggesting a structure and kicking off implementation (find current version at [https://github.com/orgs/kubernetes/projects/11](https://github.com/orgs/kubernetes/projects/11)) diff --git a/contributors/devel/sig-node/e2e-node-tests.md b/contributors/devel/sig-node/e2e-node-tests.md index f212957cd..bbfbdee7c 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 dbddf4b03..6830b660e 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 9143fb307..11813baca 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. --- diff --git a/mentoring/programs/outreachy.md b/mentoring/programs/outreachy.md index 7f835b083..24cb8a2f8 100644 --- a/mentoring/programs/outreachy.md +++ b/mentoring/programs/outreachy.md @@ -20,7 +20,7 @@ This [slide deck](https://docs.google.com/presentation/d/1JqcALpsg07eH665ZXQrIvO ## Communication - Mailing List: development announcements and discussions appear on the [`kubernetes-dev`](https://groups.google.com/forum/#!forum/kubernetes-dev) Google Group. -- Slack: Please [sign up](http://slack.k8s.io/) for an invite and join the the [#outreachy-apps](https://kubernetes.slack.com/messages/outreachy-apps) channel. +- Slack: Please [sign up](http://slack.k8s.io/) for an invite and join the [#outreachy-apps](https://kubernetes.slack.com/messages/outreachy-apps) channel. ## Contribute diff --git a/sig-node/archive/meeting-notes-2020.md b/sig-node/archive/meeting-notes-2020.md index e753d9e65..915805af8 100644 --- a/sig-node/archive/meeting-notes-2020.md +++ b/sig-node/archive/meeting-notes-2020.md @@ -1050,7 +1050,7 @@ Meeting is [canceled](https://groups.google.com/forum/?utm_medium=email&utm_sour * [bart0sh] 2 hugepages PRs need review/approval: * [Implement support for multiple sizes huge pages](https://github.com/kubernetes/kubernetes/pull/84051) was already reviewed and passed API review. Last signode review is required. This PR is covered by [granted sig-release exception](https://github.com/kubernetes/enhancements/pull/1540#issuecomment-583072382) and is going to be included into 1.18 if merged. * [kubelet: sync node allocatable cgroups upon status update](https://github.com/kubernetes/kubernetes/pull/81774) bugfix got lgtm in Oct 2019. It would be great to have it in 1.18. -* [cynepco3hahue] The KEP [Propose Memory Manager for NUMA awareness](https://github.com/kubernetes/enhancements/pull/1203) needs review, it can be great to get feedback from someone under the the sig-node group. +* [cynepco3hahue] The KEP [Propose Memory Manager for NUMA awareness](https://github.com/kubernetes/enhancements/pull/1203) needs review, it can be great to get feedback from someone under the sig-node group. * [vpickard] ~~Topology Manager CI job PR needs /approve from sig-node owner [https://github.com/kubernetes/test-infra/pull/16062](https://github.com/kubernetes/test-infra/pull/16062)~~ * [fromani] Topology Manager Upgrade test PR [https://github.com/kubernetes/kubernetes/pull/88107](https://github.com/kubernetes/kubernetes/pull/88107) * [dashpole] Distributed Tracing in Kubernete