@@ -102,7 +102,7 @@ After submitting at least 5 substantial pull requests and meeting the other
102
102
## Reviewers
103
103
104
104
Reviewers are responsible for reviewing open pull requests. Unlike member
105
- feedback, you must address reviewer feedback. Reviewers are members of the
105
+ feedback, the PR author must address reviewer feedback. Reviewers are members of the
106
106
[ @kubernetes/sig-docs- {language}-reviews] ( https://github.com/orgs/kubernetes/teams?query=sig-docs )
107
107
GitHub team.
108
108
@@ -146,15 +146,15 @@ separately for reviewer status in SIG Docs.
146
146
147
147
To apply:
148
148
149
- 1 . Open a pull request that adds your GitHub user name to a section of the
149
+ 1 . Open a pull request that adds your GitHub username to a section of the
150
150
[ OWNERS_ALIASES] ( https://github.com/kubernetes/website/blob/main/OWNERS_ALIASES ) file
151
151
in the ` kubernetes/website ` repository.
152
152
153
153
{{< note >}}
154
154
If you aren't sure where to add yourself, add yourself to ` sig-docs-en-reviews ` .
155
155
{{< /note >}}
156
156
157
- 1 . Assign the PR to one or more SIG-Docs approvers (user names listed under
157
+ 1 . Assign the PR to one or more SIG-Docs approvers (usernames listed under
158
158
` sig-docs-{language}-owners ` ).
159
159
160
160
If approved, a SIG Docs lead adds you to the appropriate GitHub team. Once added,
@@ -192,7 +192,7 @@ into the website repository. This comes with certain responsibilities.
192
192
{{< /warning >}}
193
193
194
194
- Make sure that proposed changes meet the
195
- [ contribution guidelines ] ( /docs/contribute/style/content-guide/#contributing-content ) .
195
+ [ documentation content guide ] ( /docs/contribute/style/content-guide/ ) .
196
196
197
197
If you ever have a question, or you're not sure about something, feel free
198
198
to call for additional review.
0 commit comments