diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-12-03 18:36:57 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-12-03 18:36:57 -0800 |
| commit | d39b2b35b72d5ff4646a0a2cc7f0d4ae6aac688d (patch) | |
| tree | aae82315ead6b8ed939864bf89e417632fb2e0a6 | |
| parent | 06d4e1945e70fabe3fd3fa805dd1126f6445c545 (diff) | |
| parent | fe22ecd60589fefda44258a3172a727428859c0a (diff) | |
Merge pull request #4283 from abhiraut/typo
Fix some typos in issue-triage guide
| -rw-r--r-- | contributors/guide/issue-triage.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contributors/guide/issue-triage.md b/contributors/guide/issue-triage.md index c9c32f80..94416d24 100644 --- a/contributors/guide/issue-triage.md +++ b/contributors/guide/issue-triage.md @@ -183,8 +183,8 @@ Ideally the SIG lead should have a SIG member that is a first point of contact for SIG new issues. If an issue has a SIG label assigned and no action is taken by SIG in 30 days (e.g. no comment was added by SIG or no discussion was initiated) then gently poke SIG about this pending issue. -Also consider attending one of the SIG meetings and brig up issue, if you feel -this is appropriate. +Also, consider attending one of the SIG meetings and bringing up the issue, if +you feel this is appropriate. ## Milestones @@ -251,6 +251,6 @@ and the `good first issue` label with the `/good-first-issue` command. Please note that adding the `good first issue` label will also automatically add the `help wanted` label. -If an issue has these labels but does not satisify the guidelines, please +If an issue has these labels but does not satisfy the guidelines, please ask for more details to be added to the issue or remove the labels using `/remove-help` or `/remove-good-first-issue` commands. |